Asgardeo Auth SPA SDK

Table of Content

• Introduction
• Install
• Getting Started
  • Using an Embedded Script
  • Using a Module
  • Configuring Single Logout
• Try Out the Sample Apps
• Browser Compatibility
• APIs
  • getInstance
  • initialize
  • getBasicUserInfo
  • signIn
  • trySignInSilently
  • signOut
  • httpRequest
  • httpRequestAll
  • requestCustomGrant
  • revokeAccessToken
  • getOIDCServiceEndpoints
  • getDecodedIDToken
  • getIDToken
  • getCryptoHelper
  • getAccessToken
  • getIDPAccessToken
  • refreshAccessToken
  • on
  • isAuthenticated
  • enableHttpHandler
  • disableHttpHandler
  • updateConfig
  • getHttpClient
• Utils
• Using the form_post Response Mode
• Storage
• Models
  • AuthClientConfig<Config>
  • BasicUserInfo
  • SignInConfig
  • OIDCEndpoints
  • CustomGrantConfig
  • Custom Grant Template Tags
  • DecodedIDTokenPayload
  • HttpRequestConfig
• Develop
  • Prerequisites
  • Installing Dependencies
• Error Codes
• Contribute
• License

Introduction

Asgardeo Auth SPA SDK for JavaScript allows Single Page Applications to use OIDC or OAuth2 authentication in a simple and secure way. By using Asgardeo and the JavaScript SPA SDK, developers will be able to add identity management to their Single Page Applications in a jiffy.

Prerequisite

Create an organization in Asgardeo if you don't already have one. The organization name you choose will be referred to as <org_name> throughout this document.

Install

Install the JavaScript library from the npm registry.

npm install --save @asgardeo/auth-spa

Or simply load the SDK by importing the script into the header of your HTML file.

<script src="https://unpkg.com/@asgardeo/auth-spa@latest/dist/asgardeo-spa.production.min.js"></script>

<script>
    var auth = AsgardeoAuth.AsgardeoSPAClient.getInstance();
</script>

Getting Started

Using an Embedded Script

// This client is a class and can be instantiated as follows.
var auth = AsgardeoAuth.AsgardeoSPAClient.getInstance();

// Once instantiated, the  client can be initialized by passing the relevant parameters such as the baseUrl, redirect URL, client ID, etc.
auth.initialize({
     signInRedirectURL: "http://localhost:3000/sign-in",
     signOutRedirectURL: "http://localhost:3000/dashboard",
     clientID: "client ID",
     baseUrl: "https://api.asgardeo.io/t/<org_name>"
});

// To sign in, simply call the `signIn()` method.
auth.signIn();

// The `sign-in` hook is used to fire a callback function after signing in is successful.
auth.on("sign-in", (response) => {
    alert("You have successfully signed in!");
});

Using a Module

// The SDK provides a client that can be used to carry out the authentication.
import { AsgardeoSPAClient } from "@asgardeo/auth-spa";

// This client is a class and can be instantiated as follows.
const auth = AsgardeoSPAClient.getInstance();

// Once instantiated, the  client can be initialized by passing the relevant parameters such as the server origin, redirect URL, client ID, etc.
auth.initialize({
     signInRedirectURL: "http://localhost:3000/sign-in",
     signOutRedirectURL: "http://localhost:3000/dashboard",
     clientID: "client ID",
     baseUrl: "https://api.asgardeo.io/t/<org_name>"
});

// To sign in, simply call the `signIn()` method.
auth.signIn();

// The `sign-in` hook is used to fire a callback function after signing in is successful.
auth.on("sign-in", (response) => {
    alert("You have successfully signed in!");
});

Learn more.

Configuring Single Logout

Asgardeo allows the developers to add single logout capabilities to their applications. To configure single logout:

1. Include following configs when initializing the AsgardeoSPAClient instance.
   1. Set enableOIDCSessionManagement flag to true in order to enable single logout.
   2. Adjust the checkSessionInterval value as needed to override the default interval. See AuthClientConfig for more details.
2. Ensure signIn( ) method is called with {callOnlyOnRedirect: true} when signInRedirectURL is loaded.

    auth.signIn({callOnlyOnRedirect: true});

Try Out the Sample Apps

1. Create an Application in Asgardeo

Before trying out the sample apps, you need to create an application in Asgardeo.

1. Navigate to Asgardeo Console and click on Applications under Develop tab

2. Click on New Application and then Single Page Application.

3. Enter Sample as the name of the app and add the redirect URL(s). You can find the relevant redirect URL(s) of each sample app in the Running the sample apps section.

4. Click on Register. You will be navigated to management page of the sample application.

5. Add https://localhost:3000 to Allowed Origins under Access tab and check Public client option.

6. Click on Update at the bottom.

2. Running the sample apps

Build the apps by running the following command at the root directory.

npm run build

1. HTML JavaScript Sample

The Callback URL of this app is http://localhost:3000.

You can try out the HTML JavaScript Sample App from the samples/asgardeo-html-js-app. The instructions to run the app can be found here

2. React JavaScript Sample

The Callback URL of this app is http://localhost:3000.

You can try out the React JS Sample App from the samples/asgardeo-react-js-app. The instructions to run the app can be found here

3. React Typescript Sample

The Callback URL of this app is http://localhost:3000.

You can try out the React Typescript Sample App from the samples/asgardeo-react-ts-app. The instructions to run the app can be found here

4. Java Webapp Sample

The Callback URL of this app is the URL of this app on the server. For instance, if your Tomcat server is running on http://localhost:8080, then the callback URL will be http://localhost:8080/java-webapp.

You can try out the Java Webapp Sample App from the samples/asgardeo-java-webapp. The instructions to run the app can be found here

Browser Compatibility

The SDK supports all major browsers and provides polyfills to support incompatible browsers. If you want the SDK to run on Internet Explorer or any other old browser, you can use the polyfilled script instead of the default one.

To embed a polyfilled script in an HTML page:

<script src="https://unpkg.com/@asgardeo/auth-spa@latest/dist/asgardeo-spa.production.min.js"></script>

You can also import a polyfilled module into your modular app. Asgardeo provides two different modules each supporting UMD and ESM. You can specify the preferred module type by appending the type to the module name as follows.

To import a polyfilled ESM module:

import { AsgardeoSPAClient } from "@asgardeo/auth-spa/polyfilled/esm";

To import a polyfilled UMD module:

import { AsgardeoSPAClient } from "@asgardeo/auth-spa/polyfilled/umd";

Note that using a polyfilled modules comes at the cost of the bundle size being twice as big as the default, non-polyfilled bundle.

A Web Worker cannot be used as a storage option in Internet Explorer as the browser doesn't fully support some of the modern features of web workers.

APIs

getInstance

getInstance(id?: string): AsgardeoSPAClient;

Arguments

1. id: string The id of the instance. If you need to create only one instance, then this is optional.

Returns

An instance of the AsgardeoSPAClient.

Description

This returns a static instance of the AsgardeoSPAClient. The SDK allows you to create multiple instances of the AsgardeoSPAClient. To do so, you can pass an id into the getInstance method. If no instance has been created for the provided id, a new instance will be created and returned by this method. If an instance exists, then that instance will be returned. If no id is provided, the default instance will be returned. This allows the SDK to talk to multiple identity providers through the same app.

Creating a static instance affords the developers the flexibility of using multiple files to implement the authentication logic. That is, you can have the sign in logic implemented on one page and the sign-out logic on another.

Example

const auth = AsgardeoSPAClient.getInstance();

To create another instance,

const auth2 = AsgardeoSPAClient.getInstance("primary");

initialize

initialize(config?: `AuthClientConfig<Config>`): Promise<void>;

Arguments

1. config: AuthClientConfig<Config> This contains the configurations required to implement authentication such as the client ID, server origin, etc. Refer to the AuthClientConfig<Config> section to learn about the available attributes.

Description

The initialize method is used to initialize the client. This MUST be called soon after instantiating the AsgardeoSPAClient and before calling another methods.

This method takes a config object as the only argument. The attributes of the config object is as follows.

The initialize hook is used to fire a callback function after initializing is successful. Check the on() section for more information.

Example

const config = {
    signInRedirectURL: "http://localhost:3000/sign-in",
    signOutRedirectURL: "http://localhost:3000/dashboard",
    clientID: "client ID",
    baseUrl: "https://api.asgardeo.io/t/<org_name>"
}

auth.initialize(config);

getBasicUserInfo

getBasicUserInfo(): Promise<BasicUserInfo>;

Returns

A Promise that resolves with BasicUserInfo.

Description

This method returns a promise that resolves with the information about the authenticated user obtained from the id token as an object. To learn more what information this object contains, refer to the BasicUserInfo section.

Example

auth.getBasicUserInfo().then((response) => {
    // console.log(response);
}).catch((error) => {
    // console.error(error);
});

signIn

signIn(config?: SignInConfig, authorizationCode?: string, sessionState?: string, tokenRequestConfig?: { params: Record<string, unknown> });

Arguments

1. config?: SignInConfig (optional) An object that contains attributes that allows you to configure sign in. The forceInit attribute of this object, allows you to force a request to the .well-known endpoint even if a request has previously been sent. You can also pass key-value pairs that you want to be appended as path parameters to the authorization URL to this object. To learn more, refer to SignInConfig. This object is needed only during the authorization-url-generation phase.

2. authorizationCode?: string (optional) The signIn method can be passed the authorization code as an argument, which will be used to obtain the token during the token-request phase of the method. This allows developers to use different response modes such as form_post. To learn more about the form_post method refer to the Using the form_post response mode section. If you're using the query method, then the signIn method automatically obtains the authorization code from the URL.

3. sessionState?: string (optional) The signIn method can be passed the session state as an argument, which will be used to obtain the token during the token-request phase of the method. This allows developers to use different response modes such as form_post. To learn more about the form_post method refer to the Using the form_post response mode section. If you're using the query method, then the signIn method automatically obtains the session state from the URL.

4. tokenRequestConfig?: object (optional) An optional configuration object that allows you to augment the token request.

   • params (Mandatory): Key-value pairs to be sent as additional parameters in the token request payload.

     tokenRequestConfig: {
         params: Record<string, unknown>
     }

Description

As the name implies, this method is used to sign-in users. This method will have to be called twice to implement the two phases of the authentication process. The first phase generates the authorization URl and takes the user to the single-sign-on page of the Asgardeo, while second phase triggers the token request to complete the authentication process. So, this method should be called when initiating authentication and when the user is redirected back to the app after authentication themselves with the server.

The sign-in hook is used to fire a callback function after signing in is successful. Check the on() section for more information.

Example

auth.signIn();

trySignInSilently

trySignInSilently();

Description

This method attempts to sign a user in silently by sending an authorization request with the prompt query parameter set to none. This will be useful when you want to sign a user in automatically while avoiding the browser redirects.

This uses an iFrame to check if there is an active user session in the Asgardeo by sending an authorization request. If the request returns an authorization code, then the token request is dispatched and the returned token is stored effectively signing the user in.

To dispatch a token request, the [signIn()](#signIn) or this trySignInSilently() method should be called by the page/component rendered by the redirect URL.

This returns a promise that resolves with a [BasicUserInfo](#BasicUserInfo) object following a successful sign in. If the user is not signed into the Asgardeo, then the promise resolves with the boolean value of false.

The sign-in hook is used to fire a callback function after signing in is successful. Check the on() section for more information.

:warning: Since this method uses an iFrame, this method will not work if third-party cookies are blocked in the browser.

Example

auth.trySignInSilently().then((response) => {
    if (response) {
        // The user is signed in.
        // handle basic user info
    }

    // The user is not signed in.
});

signOut

signOut();

Description

This method ends the user session at the Asgardeo and logs the user out.

The sign-out hook is used to fire a callback function after signing out is successful. Check the on() section for more information.

Example

auth.signOut();

The locally stored user session is cleared when a sign-out hook is registered after the user gets redirected back to the signOutRedirectURL. Therefore, the developer should ensure that a sign-out hook is registered when signOutRedirectURL is loaded. Refer the example for further details.

Example

// Register a sign-out hook with any callback function when signOutRedirectURL is loaded 
// to clear locally stored user session
auth.on("sign-out", () => {});

httpRequest

httpRequest(config: HttpRequestConfig): Promise<HttpResponse>;

Arguments

1. config: [HttpRequestConfig](#httpRequestConfig) A config object with the settings necessary to send http requests. This object is similar to the AxiosRequestConfig but provides these additional attributes:

   | Attribute | Type | Default | Description | |--------------------------|-----------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------| | attachToken | boolean | true | If set to true, the token will be attached to the request header. | | shouldEncodeToFormData | boolean | false | If set to true, the request body will be encoded to FormData. The body (specified by the data attribute) should be a Javascript object. | | shouldAttachIDPAccessToken | boolean | false | If set to true, the IDP access token will be attached to the the request Authorization header. |

Returns

A Promise that resolves with the response.

Description

This method is used to send http requests to the Asgardeo authenticated endpoints. The developer doesn't need to manually attach the access token since this method does it automatically.

If the storage type is set to sessionStorage or localStorage, the developer may choose to implement their own ways of sending http requests by obtaining the access token from the relevant storage medium and attaching it to the header. However, if the storage is set to webWorker, this is the ONLY way http requests can be sent.

This method accepts a config object which is of type AxiosRequestConfig. If you have used axios before, you can use the httpRequest in the exact same way.

For example, to get the user profile details after signing in, you can query the me endpoint as follows:

Example

const auth = AsgardeoSPAClient.getInstance();

const requestConfig = {
    headers: {
        "Accept": "application/json",
        "Content-Type": "application/scim+json"
    },
    method: "GET",
    url: "https://api.asgardeo.io/scim2/me"
};

return auth.httpRequest(requestConfig)
    .then((response) => {
        // console.log(response);
    })
    .catch((error) => {
        // console.error(error);
    });

httpRequestAll

httpRequestAll(config[]: HttpRequestConfig[]): Promise<[]>;

Arguments

1. config[]: [HttpRequestConfig](#httpRequestConfig)[] An array of config objects with the settings necessary to send http requests. This object is similar to the AxiosRequestConfig but provides an additional attribute called attachToken to allow you to specify if the access token should be attached to the request.

Returns

A Promise that resolves with the responses.

Description

This method is used to send multiple http requests at the same time. This works similar to axios.all(). An array of config objects need to be passed as the argument and an array of responses will be returned in a Promise in the order in which the configs were passed.

Example

auth.httpRequestAll(configs).then((responses) => {
    response.forEach((response) => {
        // console.log(response);
    });
}).catch((error) => {
    // console.error(error);
});

requestCustomGrant

requestCustomGrant(config: CustomGranConfig): Promise<HttpResponse | BasicUserInfo>;

Arguments

1. config: CustomGrantConfig A config object to configure the custom-grant request. To learn more about the different attributes that can be used with config object, see the CustomGrantConfig section.

Returns

A Promise that resolves either with the response or the BasicUserInfo.

Description

This method allows developers to use custom grants provided by their Identity Providers. This method accepts an object that has the following attributes as the argument.

The custom-grant hook is used to fire a callback function after a custom grant request is successful. Check the on() section for more information.

    const config = {
      attachToken: false,
      data: {
          client_id: "{{clientID}}",
          grant_type: "account_switch",
          scope: "{{scope}}",
          token: "{{token}}",
      },
      id: "account-switch",
      returnResponse: true,
      returnsSession: true,
      signInRequired: true
    }

    auth.requestCustomGrant(config).then((response)=>{
        console.log(response);
    }).catch((error)=>{
        console.error(error);
    });

revokeAccessToken

revokeAccessToken();

Description

This method revokes the access token and clears the session information from the storage.

The end-user-session hook is used to fire a callback function after end user session is successful. Check the on() section for more information.

Example

auth.revokeAccessToken();

getOIDCServiceEndpoints

getOIDCServiceEndpoints(): Promise<OIDCEndpoints>

Returns

A Promise that resolves with an object containing the endpoints. To learn more about what endpoints are returned, refer to the OIDCEndpoints section.

Description

This method returns a promise that resolves with an object containing the OIDC endpoints obtained from the .well-known endpoint. The object contains the following attributes.

| Attribute | Description | |-----------------------|------------------------------------------------------------------------------------| | "authorize" | The endpoint to which the authorization request should be sent. | | "jwks" | The endpoint from which JSON Web Key Set can be obtained. | | "oidcSessionIFrame" | The URL of the page that should be loaded in an IFrame to get session information. | | "revoke" | The endpoint to which the revoke-token request should be sent. | | "token" | The endpoint to which the token request should be sent. | | "wellKnown" | The well-known endpoint from which OpenID endpoints of the server can be obtained. |

Example

auth.getOIDCServiceEndpoints().then((endpoints) => {
    // console.log(endpoints);
}).error((error) => {
    // console.error(error);
});

getDecodedIDToken

getDecodedIDToken(): Promise<DecodedIDTokenPayload>

Returns

A promise that returns with the DecodedIDTokenPayload object.

Description

This method returns a promise that resolves with the decoded payload of the JWT ID token.

Example

auth.getDecodedIDToken().then((idToken) => {
    // console.log(idToken);
}).error((error) => {
    // console.error(error);
});

getIDToken

getIDToken(): Promise<string>

Returns

idToken: Promise<string> The id token.

Description

This method returns the id token.

Example

const idToken = await auth.getIDToken();

getAccessToken

getAccessToken(): Promise<string>;

Returns

A Promise that resolves with the access token.

Description

This returns a promise that resolves with the access token. The promise resolves successfully only if the storage type is set to a type other than webWorker. Otherwise, an error is thrown.

Example

auth.getAccessToken().then((token) => {
    // console.log(token);
}).error((error) => {
    // console.error(error);
});

getIDPAccessToken

getIDPAccessToken(): Promise<string>;

Returns

A Promise that resolves with the idp access token.

Description

This returns a promise that resolves with the idp access token. The promise resolves successfully only if the storage type is set to a type other than webWorker. Otherwise, an error is thrown.

Example

auth.getIDPAccessToken().then((token) => {
    // console.log(token);
}).error((error) => {
    // console.error(error);
});

getDataLayer

getDataLayer(): Promise<DataLayer<MainThreadClientConfig>>;

Returns

A Promise that resolves with the data layer object.

Description

This returns a promise that resolves with the data layer object. The promise resolves successfully only if the storage type is set to a type other than webWorker. Otherwise, an error is thrown.

Example

auth.getDataLayer().then((dataLayer) => {
    // console.log(dataLayer);
}).error((error) => {
    // console.error(error);
});

getCryptoHelper

getCryptoHelper(): Promise<CryptoHelper>

Returns

cryptoHelper : CryptoHelper

CryptoHelper provides support for performing a cryptographic operation such as producing a PKCE code and verifying ID tokens.

Description

This method returns the CryptoHelper object used by the SDK to perform cryptographic operations.

Example

auth.getCryptoHelper().then((cryptoHelper) => {
    // console.log(cryptoHelper);
}).error((error) => {
    // console.error(error);
});

refreshAccessToken

refreshAccessToken(): Promise<BasicUserInfo>;

Returns

A Promise that resolves with the BasicUserInfo object.

Description

This refreshes the access token and stores the refreshed session information in either the session or local storage as per your configuration. Note that this method is not required to be used when the storage type is set to webWorker since the web worker automatically refreshes the token, and there is no need for the developer to do it.

Example

auth.refreshAccessToken().then((response)=>{
      // console.log(response);
 }).catch((error)=>{
      // console.error(error);
});

on

on(hook: string, callback: () => void, id?: string): Promise<void>

Arguments

1. hook: string The name of the hook.
2. callback: () => void The callback function that should be fired.
3. id?: string An id for the method. This is required only when the hook type is custom-grant.

Description

The on method is used to hook callback functions to authentication methods. The method accepts a hook name and a callback function as the only arguments except when the hook name is "custom-grant", in which case the id of the custom grant should be passed as the third argument. The following hooks are available.

If you are using TypeScript, you may want to use the Hooks enum that consists of the following string literals instead of directly inputting the string value.

| Hook | Method to which the callback function is attached | Returned Response | |:-------------------------|:---------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------| | "sign-in" | signIn() | The user information. See getUserInfo()'s return type for more details. | | "sign-out" | signOut() | | | "initialize" | initialize() | A boolean value indicating if the initialization was successful or not. | | "http-request-start" | httpRequest() (Called before an http request is sent) | | | "http-request-finish" | httpRequest() (Called after an http request is sent and response is received.) | | | "http-request-error" | httpRequest() (Called when an http request returns an error) | | | "http-request-success" | httpRequest() (Called when an http requests returns a response successfully) | | | "revoke-access-token" | revokeAccessToken() | A boolean value indicating if the process was successful or not | | "custom-grant" | customGrant() | Returns the response from the custom grant request. | | sign-out-failed | signOut() (Called when sign out fails) | An object of type SignOutError. |

When the user signs out, the user is taken to the Asgardeo's logout page and then redirected back to the SPA on successful log out. Hence, developers should ensure that the "sign-out" hook is called when the page the user is redirected to loads.

Example

auth.on("sign-in", () => {
    // console.log(response);
});

isAuthenticated

isAuthenticated(): boolean

Returns

isAuth: boolean A boolean value that indicates of the user is authenticated or not.

Description

This method returns a boolean value indicating if the user is authenticated or not.

Example

const isAuth = auth.isAuthenticated();

enableHttpHandler

enableHttpHandler(): Promise<Boolean>

Returns

A Promise that resolves with a boolean value indicating if the call was successful.

Description

This enables the callback functions attached to the http client. The callback functions are enabled by default. This needs to be called only if the disableHttpHandler method was called previously.

Example

auth.enableHttpHandler();

disableHttpHandler

disableHttpHandler(): Promise<boolean>

Returns

A Promise that resolves with a boolean value indicating if the call was successful.

Description

This disables the callback functions attached to the http client.

Example

auth.disableHttpHandler();

updateConfig

updateConfig(config: Partial<AuthClientConfig<T>>): void

Arguments

1. config: AuthClientConfig<T>

The config object containing the attributes that can be used to configure the SDK. To learn more about the available attributes, refer to the AuthClientConfig>T> model.

Description

This method can be used to update the configurations passed into the constructor of the AsgardeoAuthClient. Please note that every attribute in the config object passed as the argument here is optional. Use this method if you want to update certain attributes after instantiating the class.

Example

auth.updateConfig({
    signOutRedirectURL: "http://localhost:3000/sign-out"
});

getHttpClient

auth.getHttpClient(): `HttpClientInstance`

Returns

An HttpClientInstance

Description

This method returns the HttpClientInstance. This is the client that is used to send http requests internally.

Example

const httpClient = auth.getHttpClient();

Utils

SPAUtils

Collection of utils that could be used by consuming framework SDKs.

hasAuthSearchParamsInURL

SPAUtils.hasAuthSearchParamsInURL(): boolean

Returns

An boolean

Description

Util function to test if code and session_state are available in the URL as search params.

Example

const hasParams: boolean = SPAUtils.hasAuthSearchParamsInURL();

Using the form_post response mode

When the responseMode is set to form_post, the authorization code is sent in the body of a POST request as opposed to in the URL. So, the Single Page Application should have a backend to receive the authorization code and send it back to the Single Page Application.

The backend can then inject the authorization code into a JavaScript variable while rendering the webpage in the server side. But this results in the authorization code getting printed in the HTML of the page creating a threat vector.

To address this issue, we recommend storing the authorization code in a server session variable and providing the Single Page Application a separate API endpoint to request the authorization code. The server, when the request is received, can then respond with the authorization code from the server session.

You can refer to a sample implementation using JSP here.

Storage

Asgardeo allows the session information including the access token to be stored in three different places, namely,

1. Session storage
2. Local storage
3. Web worker
4. Browser memory

Of the four methods, storing the session information in the web worker is the safest method. This is because the web worker cannot be accessed by third-party libraries and data there cannot be stolen through XSS attacks. However, when using a web worker to store the session information, the httpRequest method has to be used to send http requests. This method will route the request through the web worker and the web worker will attach the access token to the request before sending it to the server.

auth.initialize(config);

Models

AuthClientConfig<Config>

The AuthClientConfig<Config> interface extends the AuthClientConfig<T> interface provided by the Asgardeo JavaScript Auth SDK with the Config interface. This table lists the attributes that the AuthClientConfig<T> interface takes.

This table shows the extended attributes provided by the Config interface. | Attribute | Required/Optional | Type | Default Value | Description | |:------------------------------|:------------------------------------------------|:----------------------------------------------------|:-------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | storage | Optional | "sessionStorage", "webWorker", "localStorage" | "sessionStorage" | The storage medium where the session information such as the access token should be stored. | | resourceServerURLs | Required if the storage is set to webWorker | string[] | [] | The URLs of the API endpoints. This is required if the storage method is set to webWorker. Additionally, when API calls are made through the httpRequest or the httpRequestAll method, only the calls to the endpoints specified either in baseURL or in resourceServerURLs attributes will be allowed. Everything else will be denied. | | requestTimeout | Optional | number | 60000 (seconds) | Specifies in seconds how long a request to the web worker should wait before being timed out. | | sessionRefreshInterval | Optional | number | 300 (seconds) | Specifies how often the session state should be checked. To check the authentication state, the authorization endpoint is queried with the prompt parameter set to none. | | checkSessionInterval | Optional | number | 3 (seconds) | Specifies how often the check-session iFrame should be queried to check the session state. This is used to perform single logout. | | enableOIDCSessionManagement | Optional | boolean | false | Flag to enable OIDC Session Management. Set this flag to true to add single logout capabilities into your application. |

The AuthClientConfig Interface

| Attribute | Required/Optional | Type | Default Value | Description | |------------------------------|---------------------------------------------------------------------------------------------------|-----------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| | signInRedirectURL | Required | string | "" | The URL to redirect to after the user authorizes the client app. eg: https//localhost:3000/sign-in | | signOutRedirectURL | Optional | string | The signInRedirectURL URL will be used if this value is not provided. | The URL to redirect to after the user | | clientHost | Optional | string | The origin of the client app obtained using window.origin | The hostname of the client app. eg: https://localhost:3000 | | clientID | Required | string | "" | The client ID of the OIDC application hosted in the Asgardeo. | | clientSecret | Optional | string | "" | The client secret of the OIDC application | | enablePKCE | Optional | boolean | true | Specifies if a PKCE should be sent with the request for the authorization code. | | prompt | Optional | string | "" | Specifies the prompt type of an OIDC request | | responseMode | Optional | ResponseMode | "query" | Specifies the response mode. The value can either be query or form_post | | scope | Optional | string[] | ["openid"] | Specifies the requested scopes. | | baseUrl | Required | string | "" | The origin of the Identity Provider. eg: https://api.asgardeo.io/t/<org_name> | | overrideWellEndpointConfig | Optional | boolean | false | If this option is set to true, then the endpoints object will override endpoints obtained | | endpoints | Optional (Required to provide all endpoints, if wellKnownEndpoint or baseUrl is not provided) | OIDCEndpoints | OIDC Endpoints Default Values | The OIDC endpoint URLs. The SDK will try to obtain the endpoint URLS | | wellKnownEndpoint | Optional (Required if baseUrl or endpoints is not provided) | string | "/oauth2/token/.well-known/openid-configuration" | The URL of the .well-known endpoint. | | validateIDToken | Optional | boolean | true | Allows you to enable/disable JWT ID token validation after obtaining the ID token. | | clockTolerance | Optional | number | 60 | Allows you to configure the leeway when validating the id_token. |

BasicUserInfo

| Attribute | Type | Description | |:----------------|:---------|:---------------------------------------------------------------------------------------------------| | email | string | The email address of the user. | | username | string | The username of the user. | | displayName | string | The display name of the user. It is the preferred_username in the id token payload or the sub. | | allowedScopes | string | The scopes allowed for the user. | | tenantDomain | string | The tenant domain to which the user belongs. | | sessionState | string | The session state. | | sub | string | The uid corresponding to the user to whom the ID token belongs to. |

SignInConfig

| Method | Required/Optional | Type | Default Value | Description | |----------------------|-------------------|-----------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | callOnlyOnRedirect | Optional | boolean | false | Makes sure that this function is executed only after being redirected from the Single-Sign-On page. This will be useful to send a token request after the user authenticates themself with the server. | | fidp | Optional | string | "" | The fidp parameter that can be used to redirect a user directly to an IdP's sign-in page. | | forceInit | Optional | boolean | false | Forces obtaining the OIDC endpoints from the .well-known endpoint. A request to this endpoint is not sent if a request has already been sent. This forces a request. | | key: string | Optional | string | boolean | "" | Any key-value pair to be appended as path parameters to the authorization URL. |

OIDCEndpoints

| Method | Type | Default Value | Description | |-------------------------|----------|------------------------|--------------------------------| | authorizationEndpoint | string | "/oauth2/authorize" | The authorization endpoint. | | tokenEndpoint | string | "/oauth2/token" | The token endpoint. | | userinfoEndpoint | string | "" | The user-info endpoint. | | jwksUri | string | "/oauth2/jwks" | The JWKS URI. | | registrationEndpoint | string | "" | The registration endpoint. | | revocationEndpoint | string | "/oauth2/revoke" | The token-revocation endpoint. | | introspectionEndpoint | string | "" | The introspection endpoint. | | checkSessionIframe | string | "/oidc/checksession" | The check-session endpoint. | | endSessionEndpoint | string | "/oidc/logout" | The end-session endpoint. | | issuer | string | "" | The issuer of the token. |

CustomGrantConfig

| Attribute | Required/Optional | Type | Default Value | Description | |------------------|-------------------|-----------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | id | Required | string | "" | Every custom-grant request should have an id. This attributes takes that id. | | data | Required | any | null | The data that should be sent in the body of the custom-grant request. You can use template tags to send session information. Refer to the Custom Grant Template Tags section for more details. | | signInRequired | Required | boolean | false | Specifies if the user should be sign-in or not to dispatch this custom-grant request. | | attachToken | Required | boolean | false | Specifies if the access token should be attached to the header of the request. 💡 Note : If the request is credentialed, server must specify a domain, and cannot use wild carding. This would lead to CORS errors and if you intend to bypass this behavior per request, add wihCredentials: false to the httpRequest config. | | returnsSession | Required | boolean | false | Specifies if the the request returns session information such as the access token. | | tokenEndpoint | Optional | string | null | Token endpoint is an optional parameter which can be used to provide an optional token endpoint that will be used instead of default token endpoint. |

Custom Grant Template Tags

Session information can be attached to the body of a custom-grant request using template tags. This is useful when the session information is not exposed outside the SDK but you want such information to be used in custom-grant requests. The following table lists the available template tags.

| Tag | Data | |--------------------|--------------------| | "{{token}}" | The access token. | | {{username}}" | The username. | | "{{scope}}" | The scope. | | {{clientID}}" | The client ID. | | "{{clientSecret}}" | The client secret. |

The data attribute

DecodedIDTokenPayload

| Attribute | Type | Description | |--------------------|------------------------|------------------------------------------------| | aud | string | string[] | The audience. | | sub | string | The subject. This is the username of the user. | | iss | string | The token issuer. | | email | string | The email address. | | preferred_username | string | The preferred username. | | tenant_domain | string | The tenant domain to which the user belongs. |

HTTPRequestConfig

This extends the AxiosRequestConfig by providing an additional attribute that is used to specify if the access token should be attached to the request or not. | Attribute | Type | Description | |-------------|-----------|--------------------------------------------------------------------------------| | attachToken | boolean | Specifies if the access token should be attached to the header of the request. |

SignOutError

| Attribute | Type | Description | |-------------------|----------|------------------------| | error | string | The error message. | | error_description | string | The error description. |

Develop

Prerequisites

• Node.js (version 10 or above).
• yarn package manager.

Installing Dependencies

The repository is a mono repository. The SDK repository is found in the lib directory. You can install the dependencies by running the following command at the root.

yarn build

Error Codes

Error code consist of four parts separated by a -.

• The first part refers to the SDK. Example: JS refers to this SDK.

• The second part refers to the code file. Example: MAIN_THREAD_CLIENT refers to the main-thread-client.ts file.

• The third part is the abbreviation of the name of the method/function that threw the error. If there are more than one method/function with the same abbreviation, then a number based on the order of declaration is appended to the abbreviation. Example: HR refers to the httpRequest method.

• The fourth part refers to the type of error and is position. Example: IV02 refers to an invalid argument error and the fact that this is the second error in the method/function. The following error types are available:

  | Error Code | Description | |:-----------|:--------------| | NE | Network Error | | HE | Http Error | | IV | Invalid | | NF | Not Found | | TO | Timeout | | SE | Server Error |

Contribute

Please read Contributing to the Code Base for details on our code of conduct, and the process for submitting pull requests to us.

Reporting issues

We encourage you to report issues, improvements, and feature requests creating Github Issues.

Important: And please be advised that security issues must be reported to security@wso2com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.

License

This project is licensed under the Apache License 2.0. See the LICENSE file for details.