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

@christianacca/angular-swa-auth

Package Overview
Dependencies
Maintainers
1
Versions
11
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@christianacca/angular-swa-auth

Programmatically work with Azure Static Web Apps authentication in an angular app

  • 2.0.0-beta.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
12
Maintainers
1
Weekly downloads
 
Created
Source

@christianacca/angular-swa-auth

Programmatically work with Azure Static Web Apps authentication in an angular app

Features

When to use this library?

Depending on your use case you might not need this library at all. You likely do NOT need this library if your requirements are simple:

  • Your angular app is ONLY served up to authenticated users
  • It's not a problem that authentication does not work for deep linking (see issue 502)
  • The same authorization rules apply to all client-side routes
  • You don't need to inform your functions app when a user has signed in / out

If this is your app, then have a look at angular-swa-auth-nolib: a sample app that does not use this library to implement authentication

For all other use cases, this library will likely add value.

Usage

1. Install library

npm install @christianacca/angular-swa-auth

2. Configure and use library

  1. Import library in app module:

    import { NgModule } from '@angular/core';
    import { BrowserModule } from '@angular/platform-browser';
    import { SwaAuthModule } from '@christianacca/angular-swa-auth';
    
    import { AppComponent } from './app.component';
    
    @NgModule({
      declarations: [AppComponent],
      imports: [
        BrowserModule,
        SwaAuthModule.forRoot({
          // overrides to the default configuration here
        })
      ],
      bootstrap: [AppComponent]
    })
    export class AppModule {}
    
  2. Implement login/logout/purge

    The following is guidance only. For an alternative, where the user is prompted with a modal to select the identity provider to sign in with see IdentityProviderInteractiveSelectorService

    import { Component } from '@angular/core';
    import { AuthService, ClientPrincipal } from '@christianacca/angular-swa-auth';
    import { Observable } from 'rxjs';
    
    @Component({
      selector: 'app-auth',
      template: `
        <nav class="menu auth">
          <p class="menu-label">Auth</p>
          <div class="menu-list auth">
            <ng-container *ngIf="userInfo$ | async as user; else loginTpl">
              <a (click)="logout()">Logout</a>
              <a (click)="purge()">Forget me</a>
            </ng-container>
            <ng-template #loginTpl>
              <a *ngFor="let provider of providers" (click)="login(provider.id)">{{ provider.name }}</a>
            </ng-template>
          </div>
        </nav>
      `
    })
    export class AuthComponent {
      userInfo$: Observable<ClientPrincipal | null>;
      providers = this.authService.identityProviders;
    
      constructor(private authService: AuthService) {
        this.userInfo$ = this.authService.userLoaded$;
      }
    
      login(identityProvider: string) {
        this.authService.login({ identityProvider });
      }
    
      logout() {
        this.authService.logout();
      }
    
      purge() {
        this.authService.purge();
      }
    }
    
  3. Optionally add AuthGuard to your route(s)

    If your app can only be accessed by authenticated users then add the guard to the top level route. EG:

    import { AuthGuard } from '@christianacca/angular-swa-auth';
    
    const routes: Route[] = [
      {
        path: '',
        canActivate: [AuthGuard],
        children: [
          {
            path: 'home',
            component: ShellComponent,
            children: [
              // routes to your "content" pages in your app
            ]
          },
          { path: '', pathMatch: 'full', redirectTo: '/home' }
        ]
      }
    ];
    
  4. Optionally add SwaRoleGuard to your route(s)

    import { AuthGuard } from '@christianacca/angular-swa-auth';
    
    const routes: Route[] = [
      {
        path: 'product-admin',
        data: {
          allowedRoles: 'admin' // other ex: ['admin', 'owner']  ['admin', ['product-reader', 'owner']]
        },
        canActivate: [SwaRoleGuard],
        component: AdminComponent
      },
      {
        path: 'user-admin',
        data: {
          allowedRoles: 'owner'
        },
        canLoad: [SwaRoleGuard],
        loadChildren: () => import('@christianacca/demo-app/user-admin').then(m => m.UserAdminModule)
      }
    ];
    
  5. Optionally send authentication session events to your function app api

      imports: [
        BrowserModule,
        SwaAuthModule.forRoot({
          sendSessionEventsToApi: true,
          sessionEventsApiUrl: '/api/authevents' // this is the default if not supplied
        })
      ]
    

    IMPORTANT: you will need to add a function to your functions app api that receives via a POST an instance of AuthEventPayload

More resources

Keywords

FAQs

Package last updated on 14 Sep 2021

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