Angular library for secure access to RESTful web APIs

bower install secure-ng-resource



Build Status

A wrapper around ngResource that adds authentication to requests, automatically asking the user for credentials when needed. Currently supports OAuth password flow, and OpenID verification with an Authorization header to pass the key.

The ArrayBuffer javascript type is required; for IE versions 9 and below, you will need to provide a polyfill for it.


After you've downloaded the secure-ng-resource component with bower, add the usual lines in app.js (to secureNgResource) and index.html (to components/secure-ng-resource/build/secure-ng-resource.js).

Using OAuth password flow

Suppose you are writing an Angular app that is backed by a RESTful web service available at Its authentication is based on the OAuth Resource Owner Password Flow. Configure your app to use this auth system in a session service for your application:

// app/scripts/services/appSession.js

angular.module('myApp').factory('appSession', [
'authSession', 'passwordOAuth', // These are from secureNgResource
function(authSession, passwordOAuth) {
    return authSession(passwordOAuth(
        "", // Host which provides the OAuth tokens
        "1_myappmyappmyapp", // OAuth Client ID
        "shhhhhhhhhhhhhhhh" // OAuth Client Secret

Then you can use this session with secureResource, which is just a wrapper around ngResource:

// app/scripts/controllers/things.js

angular.module('myApp').controller('ThingsCtrl', [
'$scope', 'secureResource', 'appSession',
function($scope, secureResource, appSession) {
    var Thing = secureResource(

    $scope.things = Thing.query();

When Thing.query() executes, SecureResource will add the appropriate authorization to the request. If the request is refused (if the user hasn't logged in yet, or if they logged in a long while ago and their access token expired), then the user is redirected to your login page (by default at /login) within your angular app's internal routing system.

Your login controller can interact with the session like so:

// app/scripts/controllers/login.js

angular.module('myApp').controller('LoginCtrl', [
'$scope', 'appSession',
function($scope, appSession) {
    $scope.credentials = {
        user: null, // Attach your login username element to this
        pass: null  // And your password element to this

    // Have your "Log In" button call this
    $scope.login = function () {
        if (!$scope.loginForm.$valid) { return; }
        .then(null, function(result) {
            if (result.status == 'denied') {
                alert("Login failed: " + result.msg);
            } else {
                alert("Something went wrong: " + result.msg);

You don't have to worry about redirecting the user after they successfully log in, the appSession.login function will take care of that. If the user was at another internal route and got kicked over to the login page by an auth failure, then they will be sent back there. Otherwise they will be sent to the / internal route by default.

Using OpenID

The OpenID system requires more specific behavior from the back-end server than the OAuth system. When creating the OpenID auth instance, you supply a host which is typically your server, and a beginPath at that host.

The login process goes like so:

  1. The user supplies an OpenID identifier as their credentials. You should pass this identifier URL to AuthSession.login() in an object under the key 'openid_identifier'.

  2. Secure-ng-resource redirects user to beginPath via a POST, submitting the usual OpenID form data plus these additional fields:

    • key: A random byte string, base64 encoded.
    • target_url: A URL to go to after authentication completes, generally this is the URL for the angular app's login page.
  3. The server responds with a redirect to the identity provider login page.

  4. When authentication completes, the server redirects to the target URL from step #2, with the following JSON structure base64 encoded as the GET argument auth_resp:

    • approved: A boolean indicating whether authentication was accepted
    • sessionId: (If approved) An authentication token, XOR'd against the key and then itself base64 encoded
    • user: (If approved) The username that the user logged in as
    • userId: (Optional) The id of the user that logged in (usable in app API requests)
    • message: (Optional) An explanation of what happened during authentication
  5. Assuming access was allowed, then from that point forward any requests that go through secureNgResource using this authentication session will include an Authorization header of the form SesID 123ABC where 123ABC is the sessionId from the response object. Note that cookies are not used in these requests; this helps to prevent XSS attacks.

In order to support step #4 of this process, your login controller should check for the auth_resp value and pass it to the login method if it's present:

if ($ {
    appSession.login({auth_resp: $});
    $'auth_resp', null);


Project directory structure and build/test configs based on those found in ng-grid.