I am in the process of setting up a site using Angular, Express, Node, and Passport. Currently, I am configuring Angular to monitor the $rootScope.currentUser variable with the following code:
app.run(function ($rootScope, $location, Auth) {
// Watching the value of the currentUser variable.
$rootScope.$watch('currentUser', function(currentUser) {
// If there is no currentUser and the page requires authorization, attempt to update it
// This may trigger 401 errors if the user's session is invalid
if (!currentUser && (['/', '/login', '/logout', '/signup'].indexOf($location.path()) == -1 )) {
Auth.currentUser();
}
});
// When receiving a 401 error, redirect to the login page.
$rootScope.$on('event:auth-loginRequired', function() {
//console.log(currentUser);
$location.path('/login');
return false;
});
});
Based on my console observations, I have noticed that the $rootScope.currentUser becomes unavailable when transitioning from the profile page to the settings page, as the Auth.currentUser() function fails due to a null value in $rootScope.currentUser.
Below is some more relevant code:
Auth.js (where the Auth.currentUser() function resides)
'use strict';
angular.module('groundup')
.factory('Auth', function Auth($location, $rootScope, Session, User, $cookieStore) {
$rootScope.currentUser = $cookieStore.get('user') || null;
$cookieStore.remove('user');
$rootScope.currentUserSignedIn;
return {
// various functions such as login, logout, createUser, currentUser, changePassword, and removeUser are defined here
};
})
After calling Auth.currentUser(), a GET request triggers the following function on the Express side:
exports.session = function (req, res) {
console.log(req.user.user_info + " in session function");
res.json(req.user.user_info);
};
The issue arises during the redirect to the /settings page, where $rootScope.currentUser is being monitored causing an automatic redirection to /login due to a failed call to Auth.currentUser(). Any assistance or insights would be highly appreciated. Thank you.