Skip to content
This repository
branch: master

Merge pull request #63 from VRMink/patch-1

Updated README with configUpdater description
latest commit 3c024544a9
Witold Szczerba authored
Octocat-spinner-32 src format December 02, 2013
Octocat-spinner-32 .gitignore feat(bower.json): add bower.json May 02, 2013
Octocat-spinner-32 LICENSE Add MIT License September 03, 2013
Octocat-spinner-32 Fixed typo April 07, 2014
Octocat-spinner-32 bower.json adjusting bower.json December 12, 2013

HTTP Auth Interceptor Module

for AngularJS

This is the implementation of the concept described in Authentication in AngularJS (or similar) based application.

There are releases for both AngularJS 1.0.x and 1.2.x, see releases.

Launch demo here or switch to gh-pages branch for source code of the demo.


This module installs $http interceptor and provides the authService.

The $http interceptor does the following: the configuration object (this is the requested URL, payload and parameters) of every HTTP 401 response is buffered and everytime it happens, the event:auth-loginRequired message is broadcasted from $rootScope.

The authService has only one method: #loginConfirmed(). You are responsible to invoke this method after user logged in. You may optionally pass in a data argument to the loginConfirmed method which will be passed on to the loginConfirmed $broadcast. This may be useful, for example if you need to pass through details of the user that was logged in. The authService will then retry all the requests previously failed due to HTTP 401 response.

Typical use case:

  • somewhere (some service or controller) the: $http(...).then(function(response) { do-something-with-response }) is invoked,
  • the response of that requests is a HTTP 401,
  • http-auth-interceptor captures the initial request and broadcasts event:auth-loginRequired,
  • your application intercepts this to e.g. show a login dialog:
    • DO NOT REDIRECT anywhere (you can hide your forms), just show login dialog
  • once your application figures out the authentication is OK, call: authService.loginConfirmed(),
  • your initial failed request will now be retried and when proper response is finally received, the function(response) {do-something-with-response} will fire,
  • your application will continue as nothing had happened.

Advanced use case:

Same beginning as before but,

  • once your application figures out the authentication is OK, call: authService.loginConfirmed([data], [updateConfigFunc]),
  • your initial failed request will now be retried but you can supply additional data to observers who are listening for event:auth-loginConfirmed, and all your queued http requests will be recalculated by your updateConfigFunc(httpConfig) function. This is very usefull if you need to update the headers with new credentials and/or tokens from your successful login.
Something went wrong with that request. Please try again.