這是另一種可能的解決方案，使用$stateProvider或$routeProvider的resolve屬性。例如用$stateProvider：
.config(["$stateProvider", function ($stateProvider) {
$stateProvider
.state("forbidden", {
/* ... */
})
.state("signIn", {
/* ... */
resolve: {
access: ["Access", function (Access) { return Access.isAnonymous(); }],
}
})
.state("home", {
/* ... */
resolve: {
access: ["Access", function (Access) { return Access.isAuthenticated(); }],
}
})
.state("admin", {
/* ... */
resolve: {
access: ["Access", function (Access) { return Access.hasRole("ROLE_ADMIN"); }],
}
});
}])
Access做出決議或拒絕根據當前用戶權限的承諾：
.factory("Access", ["$q", "UserProfile", function ($q, UserProfile) {
var Access = {
OK: 200,
// "we don't know who you are, so we can't say if you're authorized to access
// this resource or not yet, please sign in first"
UNAUTHORIZED: 401,
// "we know who you are, and your profile does not allow you to access this resource"
FORBIDDEN: 403,
hasRole: function (role) {
return UserProfile.then(function (userProfile) {
if (userProfile.$hasRole(role)) {
return Access.OK;
} else if (userProfile.$isAnonymous()) {
return $q.reject(Access.UNAUTHORIZED);
} else {
return $q.reject(Access.FORBIDDEN);
}
});
},
hasAnyRole: function (roles) {
return UserProfile.then(function (userProfile) {
if (userProfile.$hasAnyRole(roles)) {
return Access.OK;
} else if (userProfile.$isAnonymous()) {
return $q.reject(Access.UNAUTHORIZED);
} else {
return $q.reject(Access.FORBIDDEN);
}
});
},
isAnonymous: function() {
return UserProfile.then(function (userProfile) {
if (userProfile.$isAnonymous()) {
return Access.OK;
} else {
return $q.reject(Access.FORBIDDEN);
}
});
},
isAuthenticated: function() {
return UserProfile.then(function (userProfile) {
if (userProfile.$isAuthenticated()) {
return Access.OK;
} else {
return $q.reject(Access.UNAUTHORIZED);
}
});
}
};
return Access;
}])
UserProfile複製當前用戶的屬性，並執行$hasRole，$hasAnyRole，$isAnonymous和$isAuthenticated方法邏輯（加上$refresh方法，稍後解釋）：
.factory("UserProfile", ["Auth", function (Auth) {
var userProfile = {};
var clearUserProfile = function() {
for (var prop in userProfile) {
if (userProfile.hasOwnProperty(prop)) {
delete userProfile[prop];
}
}
};
var fetchUserProfile = function() {
return Auth.getProfile().then(function (response) {
clearUserProfile();
return angular.extend(userProfile, response.data, {
$refresh: fetchUserProfile,
$hasRole: function (role) {
return userProfile.roles.indexOf(role) >= 0;
},
$hasAnyRole: function (roles) {
return !!userProfile.roles.filter(function (role) {
return roles.indexOf(role) >= 0;
}).length;
},
$isAnonymous: function() {
return userProfile.anonymous;
},
$isAuthenticated: function() {
return !userProfile.anonymous;
}
});
});
};
return fetchUserProfile();
}])
Auth負責請求服務器，知道用戶簡檔（與連接到例如該請求接入令牌）的：
.service("Auth", ["$http", function ($http) {
this.getProfile = function() {
return $http.get("api/auth");
};
}])
服務器預期返回這樣一個JSON對象請求時GET api/auth：
{
"name": "John Doe", // plus any other user information
"roles": ["ROLE_ADMIN", "ROLE_USER"], // or any other role (or no role at all, i.e. an empty array)
"anonymous": false // or true
}
最後，當Access拒絕一個承諾，如果使用ui.router，該$stateChangeError事件將被解僱：
.run(["$rootScope", "Access", "$state", "$log", function ($rootScope, Access, $state, $log) {
$rootScope.$on("$stateChangeError", function (event, toState, toParams, fromState, fromParams, error) {
switch (error) {
case Access.UNAUTHORIZED:
$state.go("signIn");
break;
case Access.FORBIDDEN:
$state.go("forbidden");
break;
default:
$log.warn("$stateChangeError event catched");
break;
}
});
}])
如果使用ngRoute，所述$routeChangeError事件將被觸發：
.run(["$rootScope", "Access", "$location", "$log", function ($rootScope, Access, $location, $log) {
$rootScope.$on("$routeChangeError", function (event, current, previous, rejection) {
switch (rejection) {
case Access.UNAUTHORIZED:
$location.path("/signin");
break;
case Access.FORBIDDEN:
$location.path("/forbidden");
break;
default:
$log.warn("$stateChangeError event catched");
break;
}
});
}])
用戶簡檔還可以在控制器訪問：
.state("home", {
/* ... */
controller: "HomeController",
resolve: {
userProfile: "UserProfile"
}
})
UserProfile於是包含返回的屬性由服務器在請求時提供GET api/auth：
要刷新種
.controller("HomeController", ["$scope", "userProfile", function ($scope, userProfile) {
$scope.title = "Hello " + userProfile.name; // "Hello John Doe" in the example
}])
UserProfile需求，當用戶跡象或縮小，從而使Access可以處理與新的用戶配置文件的路徑。您可以重新加載整個頁面，或致電UserProfile.$refresh()。
.service("Auth", ["$http", function ($http) {
/* ... */
this.signIn = function (credentials) {
return $http.post("api/auth", credentials).then(function (response) {
// authentication succeeded, store the response access token somewhere (if any)
});
};
}])
.state("signIn", {
/* ... */
controller: "SignInController",
resolve: {
/* ... */
userProfile: "UserProfile"
}
})
.controller("SignInController", ["$scope", "$state", "Auth", "userProfile", function ($scope, $state, Auth, userProfile) {
$scope.signIn = function() {
Auth.signIn($scope.credentials).then(function() {
// user successfully authenticated, refresh UserProfile
return userProfile.$refresh();
}).then(function() {
// UserProfile is refreshed, redirect user somewhere
$state.go("home");
});
};
}])
好的。什麼應該在我的loginController？我的意思是我應該設置什麼？ – iCode
loginController將允許用戶從登錄頁面登錄。它將處理登錄表單。表單必須調用一個submit方法，它是loginController的一部分。此方法將更新（如果表單正確且用戶必須登錄）使用我描述的Auth服務的用戶的狀態。 – gab
對不起，您可以展示如何編寫該服務以及如何在LoginController中設置該服務？ – iCode