-
Notifications
You must be signed in to change notification settings - Fork 5
Routing and KeycloakGuard
Stan Silvert edited this page Feb 5, 2018
·
4 revisions
By default, keycloak-schematic will secure your entire application and force the user to log in before visiting any pages/routes. But if you only wish to secure certain routes, you can do that too. keycloak-schematic installs a KeycloakGuard that you can use for this purpose.
KeycloakService.init(configOptions, {onLoad: 'check-sso'})import { NgModule } from '@angular/core';
import { Routes, RouterModule } from '@angular/router';
import { PrivateComponent } from './private/private.component';
import { PublicComponent } from './public/public.component';
import {KeycloakGuard} from './keycloak-service/keycloak.guard';
const routes: Routes = [
{ path: 'public', component: PublicComponent },
{ path: 'private', component: PrivateComponent, canActivate: [KeycloakGuard] }
];
@NgModule({
imports: [RouterModule.forRoot(routes)],
exports: [RouterModule],
providers: [KeycloakGuard]
})
export class AppRoutingModule { }