Securing Your Angular App: A Comprehensive Guide to Keycloak Integration

One of the repetitive, complex, and important parts of an application is user authorization and authentication. There are many tools for this, like Firebase, Auth0, and Okta, or you can let users log in with third-party providers like Gmail, Microsoft, or social networks.

I have used Keycloak in web applications before and like the idea of centralizing authentication and authorization. This lets us focus on developing our application. In this guide, I will show you how to set up Keycloak with a simple Angular application to manage users.

But, what can Keycloak do for me?

Keycloak is an open-source tool that makes authentication and authorization easier in apps and services. It helps manage users and includes features like single sign-on (SSO), identity federation, and role and permission management.

In simple terms, Keycloak helps you:

Authenticate Users: Let users log in to your application securely.

Authorization: Controls which parts of your application users can access based on their roles and permissions.

Identity Federation: Connects with multiple identity providers (like Google, Facebook, etc.) so users can log in with their existing accounts.

Session Management: Handles user sessions, including global logout and session expiration.

Project running

This is the final result of the following guide.

Part 1. Make run Keycloak with Docker Compose

First, let’s set up Keycloak using Docker Compose. Create a docker-compose.yml file with the following content:

// docker-compose.yml
version: '3.8'

    container_name: keycloak
      - "8080:8080"
      - KC_DB=${KC_DB}
      - KC_DB_URL=${KC_DB_URL}
    command: [ "start-dev", "--import-realm" ]

    image: postgres:latest
    container_name: postgres
      - "5432:5432"
      - postgres_data:/var/lib/postgresql/data


And, a .env file at the same level as the docker-compose.yml:



Now, you can go to your terminal and do docker compose up and now you have a Keycloak up and running.

Now, we can access to our Keycloak using http://localhost:8080 and configure our new client for our Angular app.

Clicking at Administration Console using the password added in the .env file (in our case is user: admin, password: admin)

Keycloak configuration

Create a realm: In Keycloak, a realm is an isolated space that contains everything needed to manage authentication and authorization for a set of applications or services. You can define users, roles, clients, identities, and security settings within a realm.

Create a client: A client represents an application or service that uses Keycloak to manage authentication and authorization. Clients can be web apps, mobile apps, backend services, or any other entity that needs to authenticate users and manage their permissions. Our angular app will be a client of Keycloak.

Step 1: General settings:

Step 2: Capability config: We left it as is, in our basic demo, we don't need to change/add anything.

Step 3: Login settings: This one is important, lets to explain each input:

  • Root URL: The root URL of our application, Keycloak uses this URL as the base for redirection after authentication.

  • Home URL: It can be used by Keycloak to redirect users to the main page of your application after authentication, e.g., http://localhost:8080/dashboard

  • Valid redirect URIs: Specify the URLs to which Keycloak is allowed to redirect after successful authentication. This is crucial to prevent malicious redirection attacks.

  • Valid post-logout redirect URIs: Define the URLs to which Keycloak can redirect after logging out. This ensures that users are redirected to a safe and expected place after leaving the application.

  • Web origins: Define which origins are allowed to make cross-origin requests to Keycloak. This is essential for your Angular application to communicate with Keycloak without being blocked due to CORS policies.

Create a test user for login

For our Demo Angular App, we need to create a user. Go to Users and add a new user inside the realm we created.

After creating it, we can add a password:

And that's it. We are now ready to focus on our Angular app.

Part 2. Integrate Keycloak with Angular

Assuming we already have an Angular application (Angular 18), we need to install these 2 libraries: keycloak-js and keycloak-angular:

npm install keycloak-js keycloak-angular 
// OR
yarn add keycloak-js keycloak-angular

What we will add to our Angular app

  • Add the Keycloak config to our environment.ts file to use from there.
// environment.development.ts
export const environment = {
  production: false,
  keycloak: {
    authority: 'http://localhost:8080', // Keycloak server
    redirectUri: 'http://localhost:4200', // redirect
    postLogoutRedirectUri: 'http://localhost:4200/logout', // post logout url
    realm: 'my-app',
    clientId: 'angular-app',
  • Initialize the Keycloak client and register it in APP_INITIALIZER
// keycloak.factory.ts

import { KeycloakService } from 'keycloak-angular';
import { environment } from '../../environments/environment';

 * Initializes Keycloak service.
 * @param {KeycloakService} keycloak - The Keycloak service instance.
export function initializeKeycloak(keycloak: KeycloakService) {
  return async () => keycloak.init({
    config: {
      url: environment.keycloak.authority,
      realm: environment.keycloak.realm,
      clientId: environment.keycloak.clientId,
    loadUserProfileAtStartUp: true,
    initOptions: {
      onLoad: 'check-sso',
        window.location.origin + '/silent-check-sso.html',
      checkLoginIframe: false,
      redirectUri: environment.keycloak.redirectUri,

And register as a factory in appConfig with the APP_INITIALIZER token

// app.config.ts
export const appConfig: ApplicationConfig = {
  providers: [
    provideZoneChangeDetection({ eventCoalescing: true }),
      provide: APP_INITIALIZER,
      useFactory: initializeKeycloak, // Our factory
      multi: true,
      deps: [KeycloakService],
  • Create the HTML file (silent-check-sso.html) for silent SSO verification
  parent.postMessage(location.href, location.origin);

This file is important to ensure everything works correctly. Make sure it is reachable. In my case, I placed it inside /public/. Check where your asset folder is located in angular.json or project.json (if you are using Nx). To double check if it is reachable http://localhost:4200/silent-check-sso.html in my case.

  • Auth service to use KeycloakService
// auth.service.ts

 * Provides authentication services using Keycloak.
  providedIn: 'root'
export class AuthService {
  readonly #keycloakService = inject(KeycloakService);

   * Redirects the user to the login page.
   * @returns {Promise<void>} A promise that resolves when the user is redirected to the login page.
  redirectToLoginPage(): Promise<void> {
    return this.#keycloakService.login();

   * Retrieves the username of the currently authenticated user.
   * @return {string} The username of the authenticated user.
  get userName(): string {
    return this.#keycloakService.getUsername();

   * Checks if the user is currently logged in.
   * @return {boolean} - Returns true if the user is logged in, otherwise returns false.
  isLoggedIn(): boolean {
    return this.#keycloakService.isLoggedIn();

   * Logs out the user from the Keycloak service.
   * @return {void} This method does not return any value.
  logout(): void {
  • Create an auth guard to prevent users from visiting protected routes
// auth.guard.ts
export const authGuard: CanActivateFn = () => {
  const authService = inject(AuthService);
  // Checks if the user is currently logged in.
  if (authService.isLoggedIn()) {
    // Allow go to the URL
    return true;
  // Redirects the user to the login page.
  return false;
  • Use the authGuard in our appRoutes file:
export const appRoutes: Route[] = [
    path: '',
    pathMatch: 'full',
    component: MainPageComponent,
    path: 'public',
    component: PublicPageComponent,
    path: 'private',
    canActivate: [authGuard], // <-- only logged users
    component: PrivatePageComponent,
    path: 'logout',
    component: LogoutComponent,
    path: '404',
    component: NotFoundComponent,
    path: '**',
    redirectTo: '404',
  • Pages to verify the application flow

    • MainPageComponent: With a welcome page, which will show the available routes to access and a Login button that redirects us to Keycloak for authentication. [github]

    • PrivatePageComponent: This is protected by the authGuard we created. If you are not logged in, it sends you to the login page. [github]

    • PublicPageComponent: This is accessible to anyone, whether logged in or not. [github]

    • LogoutComponent: This informs the user they have logged out. [github]

This is the URL of the repo of the project up and running if you want to download and run all together.


Integrating Keycloak with your Angular app gives you a strong way to handle authentication and authorization. Keycloak takes care of security, so you can focus on building your app. It offers features like single sign-on, identity federation, and role-based access control, making the user experience secure and smooth.

Did you find this article valuable?

Support Arcadio Quintero by becoming a sponsor. Any amount is appreciated!