Listening on Route Changes to Implement a Login Mechanism


You wish to ensure that a user has to login before navigating to protected pages.


Implement a listener on the $routeChangeStart event to track the next route navigation. Redirect to a login page if the user is not yet logged in.

The most interesting part is the implementation of the route change listener:

var app = angular.module("MyApp", []).
  config(function($routeProvider, $locationProvider) {
        { templateUrl: "partials/index.html" }).
        { templateUrl: "partials/login.html", controller: "LoginCtrl" }).
      // event more routes here ...
      otherwise( { redirectTo: "/persons" });
  run(function($rootScope, $location) {
    $rootScope.$on( "$routeChangeStart", function(event, next, current) {
      if ($rootScope.loggedInUser == null) {
        // no logged user, redirect to /login
        if ( next.templateUrl === "partials/login.html") {
        } else {

Next we will define a login form to enter the username, skipping the password for the sake of simplicity:

<form ng-submit="login()">
  <input type="text" ng-model="username">

and finally the login controller, which sets the logged in user and redirects to the persons URL:

app.controller("LoginCtrl", function($scope, $location, $rootScope) {
  $scope.login = function() {
    $rootScope.loggedInUser = $scope.username;

You can find the complete example on github.


This is of course not a fully fledged login system so please don’t use it in any production system. But, it exemplifies how to generally handle access to specific areas of your web app. When you open the app in your browser you will be redirected to the login app in all cases. Only after you have entered a username can you access the other areas.

The run method is defined in Module and is a good place for such a route change listener since it runs only once on initialization after the injector is finished loading all the modules. We check the loggedInUser in the $rootScope and if it is not set we redirect the user to the login page. Note that in order to skip this behavior when already navigating to the login page, we have to explicitly check the next templateUrl.

The login controller sets the $rootScope to the username and redirects to /persons. Generally, I try to avoid using the $rootScope since it basically is a kind of global state but in our case it fits nicely since there should be a current user globally available.