Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

co-auther

Package Overview
Dependencies
Maintainers
1
Versions
32
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

co-auther

Authentication related routing logics for an Angular 2 app like this:

  • 0.0.10
  • npm
  • Socket score

Version published
Weekly downloads
8
increased by300%
Maintainers
1
Weekly downloads
 
Created
Source

co-auther

Authentication related routing logics for an Angular 2 app like this:

  • You are using JWT authentication
  • You have one route for authentication with username and password field
  • You need to load some data before actually being logged in properly (user roles / updates / news)

This module helps managing the routing based on if the authentication token is available, if the user data has been loaded, and if any of these requests fail. The authentication token is stored in a configurable localStorage variable.

Running example

  • npm install
  • npm start
  • open browser and navigate to page

Running tests

npm test

Using module

There are 3 base routes of you application

  • Authenticate: login screen
  • Initialize: loading screen for first request
  • Logged in: all pages that require authentication are children of this route

You have an "API service" with 3 methods (called login/logout/initialRequest) that return promises

  • login: should resolve with authentication token string
  • logout: makes logout request, nothing else
  • initialRequest: the initial request for the app

In your root component, load your API service and the CoAuther module. Then configure routes and initialize the CoAuther in the constructor of the component. Also expose the logout function from the CoAuther where you will use that:

import apiService from './apiService'
import * as CoAuther from 'co-auther'
...
// The 3 basic routes
@RouteConfig([
  {path: '/authenticate',    as: 'Authenticate',     component: AuthenticateCmp,   useAsDefault: true},
  {path: '/loggedIn',        as: 'LoggedIn',         component: LoggedInCmp},
  {path: '/initialRequest',  as: 'InitialRequest',   component: InitialRequestCmp}
])
...
constructor () {
  CoAuther.initialize(apiService, {
    routes: {
      loggedIn: 'LoggedIn',
      authenticate: 'Authenticate',
      initialRequest: 'InitialRequest'
    },
    authData: 'authData'
  }, (routePath) => { // Register a routing function
    this.router.navigate(['/' + routePath])
  })
}
logout () {
  CoAuther.getCoAuther().logoutWrap()
}

Use the authentication features in your authentication component:

import { activationHelper, getCoAuther } from 'co-auther'
...
@CanActivate(() => activationHelper('Authenticate'))
export class AuthenticateCmp {
  login (username, login) {
    getCoAuther().loginWrap(username, login)
  }
}

Use the activationHelper in the initialRequest route:

import { activationHelper } from 'co-auther'
...
@CanActivate(() => activationHelper('InitialRequest'))

And finally use activationHelper in loggedIn route:

import { activationHelper } from 'co-auther'
...
@CanActivate(() => activationHelper('LoggedIn'))

In order to remember which terminal route you were aiming for when accessing the GUI, you need this 'hack' in the terminal routes:

import {setTerminal} from 'co-auther'
...
@CanActivate(setTerminal)
...

NOTE: Error handling in apiService

When writing the error handling in the apiService you will want to use the .catch() of the promises. The problem is that once you've caught a rejected promise, it will bubble up as a resolved promise, so the parent will get a .then(). You can fix it by creating a new promise in your apiService and "rethrow" the error. In the file "example-common/api-service.ts" there is an example of this for the "initialRequest" function.

let apiService = {
  login () {
    return new Promise((resolve, reject) => {
      return myRequest
        .then((data) => {
          resolve(data)
        })
        .catch((err) => {
          myCustomErrorHandler(err)
          reject(err)
        })
    })
  }
}

FAQs

Package last updated on 16 Feb 2016

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc