angularjs-authentication

My app has 2 pages: main.html and login.html . When not authenticated users go to /main they should be redirected to /login . The problem is that main.html is rendered first, and after a second or so, when user authentication fails, login.html is rendered. How could I prevent from main.html to be rendered until authentication succeeds? Here is the relevant code (CoffeeScript): angular.module('myApp', [...]) .config(['$routeProvider', ($routeProvider) -> $routeProvider.when '/login', templateUrl: 'html/login.html' controller: LoginController $routeProvider.otherwise templateUrl: 'html/main.html

I'm pretty new to Angular, and right now I'm just trying to get all my routes set up and working as I'd like. Setup: When a user navigates to certain pages ( /settings for this example) the app should check if there is a user already logged in. If there is continue as usual. Otherwise the user should go to the login page ( /login ). What I'd like: After the user has successfully logged in they should go to the page they were originally trying to get to ( /settings ) My question: Is there an "Angular way" to remember where the user was trying to go to? Relevant code: app.js .when('/settings', {

I wish to create a simple authentication check for my routes by external service. I define the access requirements on the route object: $routeProvider .when('/', { templateUrl: 'src/app/views/index.html', controller: 'indexCtrl', authenticated: true }) .when('/login', { templateUrl: 'src/app/views/login.html', controller: 'loginCtrl', anonymous: true }) .otherwise({ redirectTo: '/' }) ; Then, I check if I have permission within the $routeChangeStart event. $rootScope.$on('$routeChangeStart', function (event, next) { if(next.authenticated && !$myService.isLoggedin()) $location.path("/login");

I started developing a web-app with angularJS and I'm not sure that everything is right secured (client and server side). Security is based on a single login page, if credentials are checked ok, my server sends back an unique token with custom time-validity. All other REST api are accessible through this token. The application (client) browse to my entry-point ex: https://www.example.com/home.html user insert credentials and receive back a unique token. This unique token is stored in the server database with AES or other secure techniques, it is not stored in clear format. From now on, my