@asgardeo/auth-express NPM

Asgardeo Auth Express SDK

Table of Content

Asgardeo Auth Express SDK

Introduction

Asgardeo Auth Express SDK implements OIDC authentication in JavaScript/TypeScript-based server-side apps written with Express Framework. This SDK wraps around the @asgardeo/auth-node to provide framework-specific functionalities for Express enabling the developers to use OIDC authentication in the applications with minimum effort.

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 documentation.

If you are using Asgardeo Cloud as the identity server, 1. Create a Standard-Based Application in the console. 2. In the Protocol section in Asgardeo console, 1. Change Allowed grant types to Code and Refresh Token. 2. Specify the login and logout URLs under Authorized redirect URLs.

      ```
       # default login url:
      https://<host>:<port>/login
        
      # default logout url:
      https://<host>:<port>/logout            
      ```
3. Add the HTTP origin under the Allowed Origin.

Install

Install the library from the npm registry.

npm install @asgardeo/auth-express

Getting Started

//Import Express
const express = require('express');

// Import Cookie Parser to access request cookies.
const cookieParser = require('cookie-parser');

// The SDK provides a client middleware that can be used to carry out the authentication.
const { AsgardeoExpressClient } = require("@asgardeo/auth-express");


// Create a config object containing the necessary configurations.
const config = {
  clientID: "<YOUR_CLIENT_ID>",
  clientSecret: "<YOUR_CLIENT_SECRET>",
  baseUrl: "https://api.asgardeo.io/t/<org_name>",
  appURL: "http://localhost:3000",
  scope: ["openid", "profile"]
};

//Initialize an Express App
const app = express();

// Use cookie parser in the Express App.
app.use(cookieParser())

//Initialize Asgardeo Express Client
const authClient = AsgardeoExpressClient.getInstance(config);

//Define onSignIn method to handle successful sign in
const onSignIn = (res, response) => {
  if (response) {
    res.status(200).send(response);
  }
};

//Define onSignOut method to handle successful sign out
const onSignOut = (res) => {
  res.status(200).send("Sign out successful");
};

//Define onError method to handle errors
const onError = (res, error) => {
  if(error){
    res.status(400).send(error);
  }
};

//Use the Asgardeo Auth Client
app.use(
  AsgardeoExpressClient.asgardeoExpressAuth(onSignIn, onSignOut, onError)
);

//At this point the default /login and /logout routes should be available.
//Users can use these two routes for authentication.

//A regular route
app.get("/", (req, res) => {
    res.status(200).send("Hello World");
});

//A Protected Route

//Define the callback function to handle unauthenticated requests
const authCallback = (res, error) => {
  if(error){
    res.status(400).send(error);
  }
  // Return true to end the flow at the middleware.
  return true;
};

//Create a new middleware to protect the route
const isAuthenticated = AsgardeoExpressClient.protectRoute(authCallback);

app.get("/protected", isAuthenticated, (req, res) => {
    res.status(200).send("Hello from Protected Route");
});

//Start the express app on PORT 3000
app.listen(3000, () => { console.log(`Server Started at PORT 3000`);});

Middleware

asgardeoExpressAuth

asgardeoAuth(
  onSignIn: (res: express.Response, response: TokenResponse) => void,
  onSignOut: (res: express.Response) => void,
  onError: (res: express.Response, exception: AsgardeoAuthException) => void
): any;

Arguments

onSignIn: (res: express.Response, response: TokenResponse) => void
This method will be called when the user successfully signs in.
Arguments
- res: express.Response The res object represents the HTTP response that an Express app sends when it gets an HTTP request.
- response: TokenResponse This object will have the token response from the signIn method. To know more about the TokenResponse, refer to the TokenResponse section.
onSignOut: (res: express.Response) => void
This method will be called when the user signs out successfully.
Arguments
- res: express.Response The res object represents the HTTP response that an Express app sends when it gets an HTTP request.
onError: (res: express.Response, exception: AsgardeoAuthException) => void
This method will be called if an error occurs.
Arguments
- res: express.Response The res object represents the HTTP response that an Express app sends when it gets an HTTP request.
- exception: AsgardeoAuthException The exception object of the error occurred.

Description

The SDK provides a client middleware called asgardeoAuth that provides you with the necessary methods to implement authentication. You can use this middleware to initiate the AsgardeoAuth for your application. By default, the SDK implements the /login and /logout routes so as soon as you use asgardeoAuth middleware, the /login and /logout routes will be available out of the box for the users to authenticate.

Note: The default /login and /logout route names can be customized.To learn more, refer to the ExpressClientConfig section.

Example Usage

app.use(
  AsgardeoExpressClient.asgardeoExpressAuth(onSignIn, onSignOut, onError)
);

protectRoute

protectRoute(callback: UnauthenticatedCallback): (req: express.Request, res: express.Response, next: express.nextFunction);

Arguments

callback: UnauthenticatedCallback
This function handles the callback for the unauthenticated users. To know more about implementing the UnauthenticatedCallback type, refer to the UnauthenticatedCallback section.

Description

This middleware function can be used to protect a route. When this function is passed down to a route, it will check if the session cookie exists on the request and if not it will call the callback function and if the cookie is there, the request will proceed as usual.

Example Usage

const authCallback = (res, error) => {
  res.redirect(`/?message=${ error }`);
  return true;
};

const isAuthenticated = protectRoute(authCallback);

app.get("/protected", isAuthenticated, (req, res) => {
    res.status(200).send("Hello from Protected Route");
});

APIs

The SDK provides a singleton client class called AsgardeoExpressClient that provides you with the necessary methods to implement authentication. You can instantiate the class and use req.asgardeoAuth inside a request to access this class in order to use the provided methods.

constructor

AsgardeoExpressClient.getInstance(config: ExpressClientConfig, store?: Store);

Arguments

config: ExpressClientConfig
This contains the configuration information needed to implement authentication such as the client ID, server origin etc. Additional configuration information that is needed to configure the client, can be passed down from this object (Eg: A custom login path). To learn more about what attributes can be passed into this object, refer to the ExpressClientConfig section.
Example
```
const config = {
    clientID: "<YOUR_CLIENT_ID>",
    clientSecret: "<YOUR_CLIENT_SECRET>",
    baseUrl: "<YOUR_BASE_URL>",
    appURL: "http://localhost:3000",
    scope: ["openid", "profile"]
};
```
store: Store (optional)
This is the object of interface Store that is used by the SDK to store all the necessary data used ranging from the configuration data to the access token. By default, the SDK is packed with a built-in Memory Cache Store. If needed, you can implement the Store to create a class with your own implementation logic and pass an instance of the class as the second argument. This way, you will be able to get the data stored in your preferred place. To know more about implementing the Store interface, refer to the Data Storage section.

Description

This returns an instance of the AsgardeoExpressClient class and if the class is not instantiated already, it will create a new instance and return it.

Example Usage

app.use(AsgardeoExpressClient.getInstance(config, store););

getIDToken

getIDToken(userId: string): Promise<string>

Returns

idToken: Promise<string> A Promise that resolves with the ID Token.

Description

This method returns the id token.

Example

const idToken = await authClient.getIDToken("a2a2972c-51cd-5e9d-a9ae-058fae9f7927");

getBasicUserInfo

getBasicUserInfo(userId: string): Promise<BasicUserInfo>

Arguments

userId: string (optional)
If you want to use the SDK to manage multiple user sessions, you can pass a unique ID here to generate an authorization URL specific to that user. This can be useful when this SDK is used in backend applications.

Returns

basicUserInfo: Promise<BasicUserInfo> An object containing basic user information obtained from the id token.

Description

This method returns the basic user information obtained from the payload. To learn more about what information is returned, checkout the DecodedIDTokenPayload model.

Example

// This should be within an async function.
const basicUserInfo = await authClient.getBasicUserInfo("a2a2972c-51cd-5e9d-a9ae-058fae9f7927");

getOIDCServiceEndpoints

getOIDCServiceEndpoints(): Promise<OIDCEndpoints>

Returns

oidcEndpoints: Promise<OIDCEndpoints> An object containing the OIDC service endpoints returned by the .well-known endpoint.

Description

This method returns the OIDC service endpoints obtained from the .well-known endpoint. To learn more about what endpoints are returned, checkout the OIDCEndpoints section.

Example

// This should be within an async function.
const oidcEndpoints = await authClient.getOIDCServiceEndpoints();

getDecodedIDToken

getDecodedIDToken(userId?: string): Promise<DecodedIDTokenPayload>

Arguments

userId: string (optional)
If you want to use the SDK to manage multiple user sessions, you can pass a unique ID here to generate an authorization URL specific to that user. This can be useful when this SDK is used in backend applications.

Returns

decodedIDTokenPayload: Promise<DecodedIDTokenPayload> The decoded ID token payload.

Description

This method decodes the payload of the id token and returns the decoded values.

Example

// This should be within an async function.
const decodedIDTokenPayload = await authClient.getDecodedIDToken("a2a2972c-51cd-5e9d-a9ae-058fae9f7927");

getAccessToken

getAccessToken(userId?: string): Promise<string>

Arguments

userId: string (optional)
If you want to use the SDK to manage multiple user sessions, you can pass a unique ID here to generate an authorization URL specific to that user. This can be useful when this SDK is used in backend applications.

Returns

accessToken: Promise<string> The access token.

Description

This method returns the access token.

Example

// This should be within an async function.
const accessToken = await authClient.getAccessToken("a2a2972c-51cd-5e9d-a9ae-058fae9f7927");

revokeAccessToken

revokeAccessToken(userId?: string): Promise<FetchResponse>

Arguments

userId: string (optional)
If you want to use the SDK to manage multiple user sessions, you can pass a unique ID here to generate an authorization URL specific to that user. This can be useful when this SDK is used in backend applications.

Returns

A Promise that resolves with the response returned by the server.

Description

This method clears the authentication data and sends a request to revoke the access token. You can use this method if you want to sign the user out of your application but not from the server.

Example

// This should be within an async function.
const revokeToken = await auth.revokeAccessToken("a2a2972c-51cd-5e9d-a9ae-058fae9f7927");

requestCustomGrant

requestCustomGrant(config: CustomGrantConfig, userId?: string): Promise<TokenResponse | FetchResponse>

Arguments

config: CustomGrantConfig
The config object contains attributes that would be used to configure the custom grant request. To learn more about the different configurations available, checkout the CustomGrantConfig model.
userId: string (optional)
If you want to use the SDK to manage multiple user sessions, you can pass a unique ID here to generate an authorization URL specific to that user. This can be useful when this SDK is used in backend applications.

Returns

A Promise that resolves with the token information or the response returned by the server depending on the configuration passed.

Description

This method can be used to send custom-grant requests to Asgardeo.

Example

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);
});

updateConfig

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

Arguments

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(# AuthClientConfig) 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

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

isSignOutSuccessful

static isSignOutSuccessful(signOutRedirectURL: string): boolean

This is a static method.

Arguments

signOutRedirectURL: string
The URL to which the user is redirected to after signing out from the server.

Returns

isSignedOut: boolean A boolean value indicating if the user has been signed out or not.

Description

This method returns if the user has been successfully signed out or not. When a user signs out from the server, the user is redirected to the URL specified by the signOutRedirectURL in the config object passed into the constructor of the AsgardeoAuthClient. The server appends path parameters indicating if the sign-out is successful. This method reads the URL and returns if the sign-out is successful or not. So, make sure you pass as the argument the URL to which the user has been redirected to after signing out from the server.

Example

const isSignedOut = auth.isSignOutSuccessful(<signout_redirect_url>);

didSignOutFail

static didSignOutFail(signOutRedirectURL: string): boolean

This is a static method.

Arguments

signOutRedirectURL: string
The URL to which the user is redirected to after signing out from the server.

Returns

didSignOutFail: boolean A boolean value indicating if sign-out failed or not.

Description

This method returns if sign-out failed or not. When a user signs out from the server, the user is redirected to the URL specified by the signOutRedirectURL in the config object passed into the constructor of the AsgardeoAuthClient. The server appends path parameters indicating if the sign-out is successful. This method reads the URL and returns if the sign-out failed or not. So, make sure you pass as the argument the URL to which the user has been redirected to after signing out from the server.

Example

const isSignedOutFailed = auth.isSignOutSuccessful(<signout_redirect_url>);

Data Storage

Since the SDK was developed with the view of being able to support various storage approaches, the SDK allows developers to use their preferred mode of storage. To that end, the SDK allows you to pass a store object when using the asgardeoAuth middleware. This store object contains methods that can be used to store, retrieve and delete data. The SDK provides a Store interface that you can implement to create your own Store class. You can refer to the Store section to learn mire about the Store interface.

There are three methods that are to be implemented by the developer. They are

setData
getData
removeData

The setData method is used to store data. The getData method is used to retrieve data. The removeData method is used to delete data. The SDK converts the data to be stored into a JSON string internally and then calls the setData method to store the data. The data is represented as a key-value pairs in the SDK. The SDK uses four keys internally, and you can learn about them by referring to the Data Layer section. So, every JSON stringified data value is supposed to be stored against the passed key in the data store. A sample implementation of the Store class using the browser session storage is given here.

class NodeStore implements Store {
    public setData(key: string, value: string): void {
        sessionStorage.setItem(key, value);
    }

    public getData(key: string): string {
        return sessionStorage.getItem(key);
    }

    public removeData(key: string): void {
        sessionStorage.removeItem(key);
    }
}

Models

ExpressClientConfig

This model has the | Attribute | ---------------------------- | appURL | clientID | baseUrl | clientHost | clientSecret | enablePKCE | prompt | responseMode | scope | endpoints | overrideWellEndpo | wellKnownEndpoint | validateIDToken | clockTolerance | sendCookiesInRequests | cookieConfig | loginPath | logoutPath | globalAuth following attributes. | Required/Optional | Type | Default Value | Description | | ----------------- | --------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | Required | string | "" | The base URL of the application. eg: https//localhost:3000 | | Required | string | "" | The client ID of the OIDC application hosted in the Asgardeo. | | Required* | string | "" | The origin of the Identity Provider. eg: https://api.asgardeo.io/t/<org_name> | | Optional | string | The origin of the client app obtained using window.origin | The hostname of the client app. eg: https://localhost:3000 | | Optional | string | "" | The client secret of the OIDC application | | Optional | boolean | true | Specifies if a PKCE should be sent with the request for the authorization code. | | Optional | string | "" | Specifies the prompt type of an OIDC request | | Optional | ResponseMode | "query" | Specifies the response mode. The value can either be query or form_post | | Optional | string[] | ["openid"] | Specifies the requested scopes. | | Optional | OIDCEndpoints | OIDC Endpoints Default Values | The OIDC endpoint URLs. The SDK will try to obtain the endpoint URLS | using the .well-known endpoint. If this fails, the SDK will use these endpoint URLs. If this attribute is not set, then the default endpoint URLs will be | used. However, if the overrideWellEndpointConfig is set to true, then this will override the endpoints obtained from the .well-known endpoint. | intConfig | Optional | boolean | false | If this option is set to true, then the endpoints object will override endpoints obtained | from the .well-known endpoint. If this is set to false, then this will be used as a fallback if the request to the .well-known endpoint fails. | | Optional | string | "/oauth2/token/.well-known/openid-configuration" | The URL of the .well-known endpoint. | | Optional | boolean | true | Allows you to enable/disable JWT ID token validation after obtaining the ID token. | | Optional | number | 60 | Allows you to configure the leeway when validating the id_token. | | Optional | boolean | true | Specifies if cookies should be sent in the requests. | | Optional | cookieConfig | cookieConfig Default Values | Specifies the maxAge, httpOnly and sameSite values for the cookie configuration. | | Optional | string | /login | Specifies the default login path. | | Optional | string | /logout | Specifies the default logout path. | | Optional | boolean | false | Specifies if all the routes should be protected or not. |

Important: When specifying a custom login and logout path using loginPath and logoutPath attributes, make sure you add these URLs in the Authorized redirect URLs section in the Asgardeo Console. Also make sure you add the baseURL in the Allowed originssection as well.

Store

Method	Required/Optional	Arguments	Returns	Description
`setData`	Required	key: `string`, value: `string`	`Promise<void>`	This method saves the passed value to the store. The data to be saved is JSON stringified so will be passed by the SDK as a string.
`getData`	Required	key: `string`\	`string`	This method retrieves the data from the store and returns a Promise that resolves with it. Since the SDK stores the data as a JSON string, the returned value will be a string.
`removeData`	Required	key: `string`	`Promise<void>`	Removes the data with the specified key from the store.

cookieConfig

Method	Required/Optional	Type	Default Value	Description
`maxAge`	Optional	`number`	90000	The maximum age of the cookie.
`httpOnly`	Optional	`boolean`	`true`	Setting this true will make sure that the cookie inaccessible to the JavaScript `Document.cooki`e API.
`sameSite`	Optional	`string`	`lax`	Specifies the value for sameSite (Lax / Strict / None) attribute.
`secure`	Optional	`boolean`	`false`	Specifies whether the cookie is secure or not. This will be needed to set to true when `sameSite` attribute is set to `None`.

TokenResponse

Method	Type	Description
`accessToken`	`string`	The access token.
`idToken`	`string`	The id token.
`expiresIn`	`string`	The expiry time in seconds.
`scope`	`string`	The scope of the token.
`refreshToken`	`string`	The refresh token.
`tokenType`	`string`	The token type.
`session`	`string`	The session ID.

UnauthenticatedCallback

(res: express.Response, error: string) => boolean;

Description

This method is used to handle the callback from a protected route. You may use this function to get the request object and the error message to redirect the user to the desired error page or to redirect to the login page and authenticate the user.

Example

const authCallback = (res, error) => {
  res.redirect(`/?message=${ error }`);
  return true;
};

Develop

Prerequisites

Node.js (version 10 or above).
npm 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.

npm run build

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.

@asgardeo/auth-node express uuid

@infinitebrahmanuniverse/nolb-_asg @everything-registry/sub-chunk-89 @zalastax/nolb-_asg

0.1.2

2 years ago

0.1.1

2 years ago

0.1.0

2 years ago