Token based authentication service for Angular2 with multiple user support. Angular2-Token works best with the devise token auth gem for Rails.
Angular2-Token is currently in Alpha. Any contribution is much appreciated.
You can try out Angular2-Token here.
The repository can be found here.
- Installation
 - Configuration
 - Service Methods
 - HTTP Service Wrapper
 - Multiple User Types
 - Route Guards
 - Testing
 - Credits
 - License
 
- 
Install Angular2-Token via NPM with
npm install angular2-token --save
 - 
Import and add
Angular2TokenServiceto your main module.Angular2TokenServicedepends onHttpModuleandRouterModule, so make sure you imported them too.import { HttpModule } from '@angular/http'; import { RouterModule } from '@angular/router'; import { Angular2TokenService } from 'angular2-token'; @NgModule({ imports: [ BrowserModule, HttpModule, RouterModule ], declarations: [ AppComponent ], providers: [ Angular2TokenService ], bootstrap: [ AppComponent ] })
 - 
Inject
Angular2TokenServiceinto your main component and call.init().constructor(private _tokenService: Angular2TokenService) { this._tokenService.init(); }
 - 
If you are using CORS in your Rails API make sure that
Access-Control-Expose-Headersincludesaccess-token,expiry,token-type,uid, andclient. For the rack-cors gem this can be done by adding the following to its config. More information can be found here:expose => ['access-token', 'expiry', 'token-type', 'uid', 'client']
 
Configuration options can be passed as Angular2TokenOptions via .init().
constructor(private _tokenService: Angular2TokenService) {
    this._tokenService.init({
        apiPath:                    null,
        signInPath:                 'auth/sign_in',
        signOutPath:                'auth/sign_out',
        validateTokenPath:          'auth/validate_token',
        registerAccountPath:        'auth',
        deleteAccountPath:          'auth',
        registerAccountCallback:    window.location.href,
        updatePasswordPath:         'auth',
        resetPasswordPath:          'auth/password',
        resetPasswordCallback:      window.location.href,
        userTypes:                  null
    });
}apiPath?: string- Sets base path all operations are based onsignInPath?: string- Sets path for sign insignOutPath?: string- Sets path for sign outvalidateTokenPath?: string- Sets path for token validationregisterAccountPath?: string- Sets path for account registrationdeleteAccountPath?: string- Sets path for account deletionregisterAccountCallback?: string- Sets the path user are redirected to after email confirmation for registrationupdatePasswordPath?: string- Sets path for password updateresetPasswordPath?: string- Sets path for password resetresetPasswordCallback?: string- Sets the path user are redirected to after email confirmation for password resetuserTypes?: UserTypes[]- Allows the configuration of multiple user types (see Multiple User Types)
Further information on paths/routes can be found at devise token auth
Once initialized Angular2TokenService offers methods for session management.
The signIn method is used to sign in the user with email address and password.
The optional parameter type specifies the name of UserType used for this session.
signIn(email: string, password: string, userType?: string): Observable<Response>
this._tokenService.signIn(
    'example@example.org',
    'secretPassword'
).subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);The signOut method destroys session and session storage.
signOut(): Observable<Response>
this._tokenService.signOut().subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);Sends a new user registration request to the Server.
registerAccount(email: string, password: string, passwordConfirmation: string, userType?: string): Observable<Response>
this._tokenService.registerAccount(
    'example@example.org',
    'secretPassword',
    'secretPassword'
).subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);Deletes the account for the signed in user.
deleteAccount(): Observable<Response>
this._tokenService.deleteAccount().subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);Validates the current token with the server.
validateToken(): Observable<Response>
this._tokenService.validateToken().subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);Updates the password for the logged in user.
updatePassword(password: string, passwordConfirmation: string, currentPassword?: string, userType?: string): Observable<Response>
this._tokenService.updatePassword(
    'newPassword',
    'newPassword',
    'oldPassword'
).subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);Request a password reset from the server.
resetPassword(email: string, userType?: string): Observable<Response>
this._tokenService.updatePassword(
    'example@example.org',
).subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);Angular2TokenService wraps all standard Angular2 Http Service calls for authentication and token processing.
get(path: string, requestOptions?: RequestOptions): Observable<Response>post(path: string, data: any, requestOptions?: RequestOptions): Observable<Response>put(path: string, data: any, requestOptions?: RequestOptions): Observable<Response>delete(path: string, requestOptions?: RequestOptions): Observable<Response>patch(path: string, data: any, requestOptions?: RequestOptions): Observable<Response>
this._tokenService.get('my-resource/1').map(res => res.json()).subscribe(
    res =>      console.log(res),
    error =>    console.log(error)
);An array of UserType can be passed in Angular2TokenOptions during init().
The user type is selected during sign in and persists until sign out.
.currentUser returns the currently logged in user.
this._tokenService.init({
    userTypes: [
        { name: 'ADMIN', path: 'admin' },
        { name: 'USER', path: 'user' }
    ]
});
this._tokenService.signIn(
    'example@example.com',
    'secretPassword',
    'ADMIN'
)
this._tokenService.currentUser; // ADMINAngular2-Token implements the CanActivate interface, so it can directly be used
as a route guard. It currently does not distinguish between user types.
const routerConfig: Routes = [
    { 
        path: '', 
        component: PublicComponent 
    }, {
        path: 'restricted', 
        component: RestrictedComponent, 
        canActivate: [Angular2TokenService] 
    }
];npm testTest config files based on Angular2 Webpack Starter by AngularClass
The MIT License (see the LICENSE file for the full text)
