On This Page

Okta Angular Quickstart

This guide will walk you through integrating authentication into an Angular app with Okta by performing these steps:

  1. Add an OpenID Connect Client in Okta
  2. Install the Okta Angular SDK
  3. Attach Components to Routes
  4. Use the Access Token

At the end of the Angular instructions you can choose your server type to learn more about post-authentication workflows, such as verifying tokens that your Angular application can send to your server.

If you would prefer to download a complete sample application instead, please visit Angular Sample Applications for Okta and follow those instructions.


If you don't have an Angular app, or are new to Angular, please start with Angular's documentation. It will walk you through the creation of an Angular app, creating routes, and other application development essentials.

Add an OpenID Connect Client in Okta

In Okta, applications are OpenID Connect clients that can use Okta Authorization servers to authenticate users. Your Okta org already has a default authorization server, so you just need to create an OIDC client that will use it.

  • Log into the Okta Developer Dashboard, click Applications then Add Application.
  • Choose Single Page App (SPA) as the platform, then populate your new OpenID Connect application with values suitable for your app. If you are running this locally and using the defaults from Angular's documentation, your port will be 4200:
Setting Value
App Name My SPA App
Base URIs http://localhost:
Login redirect URIs http://localhost:{port}/implicit/callback
Grant Types Allowed Authorization Code

After you have created the application there are two more values you will need to gather:

Setting Where to Find
Client ID In the applications list, or on the "General" tab of a specific application.
Org URL https://${yourOktaDomain}
On the home screen of the developer dashboard, in the upper right.

These values will be used in your Angular application to setup the OpenID Connect flow with Okta.

Install the Okta Angular SDK

You will need to use the Okta Angular SDK library to sign in the user by redirecting to the authorization endpoint on your Okta org. You can install it via npm:

npm install @okta/okta-angular --save


You will need the values from the OIDC client that you created in the previous step to instantiate the middleware. You will also need to know your Okta org URL, which you can see on the home page of the Okta Developer console.

In your application's module.ts file, import the following objects and create a configuration object:

Note: https://{yourOktaDomain} is different from your admin URL. Don’t include -admin in the value. When you copy your Okta domain from the Developer Console, you can find the correct value in the upper-right corner of the dashboard.

// myApp.module.ts

import {
} from '@okta/okta-angular';

const config = {
  issuer: 'https://${yourOktaDomain}/oauth2/default',
  redirectUri: 'http://localhost:{port}/implicit/callback',
  clientId: '{clientId}',
  pkce: true

Attach Components to Routes

You'll need to provide these routes in your sample application, so that we can sign the user in and handle the callback from Okta. We will show you how to set these up below using Angular Router:

  • /: A default home page to handle basic control of the app.
  • /implicit/callback: Handle the response from Okta and store the returned tokens.

Provide the Login and Logout Buttons

In the relevant location in your application, you will want to provide Login and Logout buttons for the user. You can show/hide the correct button by using the oktaAuth.isAuthenticated() method. For example:

import { Component } from '@angular/core';
import { OktaAuthService } from '@okta/okta-angular';

  selector: 'app-root',
  template: `
    <button *ngIf="!isAuthenticated" (click)="login()"> Login </button>
    <button *ngIf="isAuthenticated" (click)="logout()"> Logout </button>
export class AppComponent {
  isAuthenticated: boolean;

  constructor(public oktaAuth: OktaAuthService) {
    // Subscribe to authentication state changes
      (isAuthenticated: boolean)  => this.isAuthenticated = isAuthenticated

  async ngOnInit() {
    // Get the authentication state for immediate use
    this.isAuthenticated = await this.oktaAuth.isAuthenticated();

  login() {

  logout() {

Create the Callback Handler

In order to handle the redirect back from Okta, you need to capture the token values from the URL. You'll use /implicit/callback as the callback URL, and specify the default OktaCallbackComponent and declare it in your NgModule.

import { Routes, RouterModule } from '@angular/router';

const appRoutes: Routes = [
    path: 'implicit/callback',
    component: OktaCallbackComponent

Update your NgModule

Finally, import the OktaAuthModule into your NgModule, and instantiate it by passing in your configuration object:

  imports: [
export class MyAppModule { }

Use the Access Token

Your Angular application now has an access token in local storage that was issued by your Okta Authorization server. You can use this token to authenticate requests for resources on your server or API. As a hypothetical example, let's say that you have an API that gives us messages for our user. You could create a MessageList component that gets the access token from local storage, and use it to make an authenticated request to your server.

Here is what the Angular component could look like for this hypothetical example:

// messagelist.component.ts

import { Component, OnInit } from '@angular/core';
import { Http, Headers, RequestOptions } from '@angular/http';
import { OktaAuthService } from '@okta/okta-angular';
import 'rxjs/Rx';

interface Message {
   date: String,
   text: String

  template: `
    <div *ngIf="messages.length">
      <li *ngFor="let message of messages">{{message.message}}</li>
export class MessageListComponent implements OnInit{
  messages: Array<Message> [];

  constructor(private oktaAuth: OktaAuthService, private http: Http) {
    this.messages = [];

  async ngOnInit() {
    const accessToken = await this.oktaAuth.getAccessToken();
    const headers = new Headers({
      Authorization: 'Bearer ' + accessToken
    // Make request
      new RequestOptions({ headers: headers })
    .map(res => res.json())
    .subscribe((messages: Array<Message>) => messages.forEach(message => this.messages.push(message)));

In the next section you can select your server technology to see how your server can read this incoming token and validate it.