browser-authorization
Version: 1.1.4
Release Notes | Change Log
Provides auth functionality for browser environments using OIDC code flow with PKCE.
Usage
Create a new instance of BrowserAuthorizationClient
, passing in needed credentials:
The most common way to use an instance of BrowserAuthorizationClient
will depend on your specific application and workflow. Here's one common way:
Instead of a redirect, you may want to trigger a pop up to handle the sign in process:
After the user signs in, they will be redirected to the redirect url specified in your oidc configuration (developer.bentley.com) Once on that page, you must call:
to complete the process. Once back on your initial page, the call to client.signInSilent
will succeed and you should be authorized.
If the callback occurs on a page where the configured client
is not available, you can use the static method to complete the process:
This will pull the client configuration from localStorage, using the state nonce provided by OIDC to select the proper configuration.
Other notable methods:
client.signOutRedirect()
- starts the signout flow via redirect
client.signOutPopup()
- starts the signout flow via popup.
client.setAdvancedSettings(userManagerSettings)
- Allows for advanced options to be supplied to the underlying UserManager.
Topics
Name | Description |
---|---|
Authorization | For signing a user in and out of an auth service. |
Logging | Logger categories used by this package. |
All | Displays the contents of all topics in this package. |
Last Updated: 29 April, 2025