On This Page
Create an Okta app integration
Before you can sign a user in, you need to create an Okta app integration that represents your single-page application.
Sign in to your Okta organization with your administrator account.
In the Admin Console, go to Applications > Applications.
Click Create App Integration.
Select OIDC - OpenID Connect as the Sign-in method.
Select Single-Page Application as the Application type and click Next.
Note: It is important to choose the appropriate application type for apps that are public clients. Failing to do so may result in Okta API endpoints attempting to verify an app's client secret, which public clients are not designed to have, and would break the sign-in or sign-out flow.
Enter a name for your app integration (or leave the default value).
Select Authorization Code and Refresh Token as the Grant type. This enables Authorization Code flow with PKCE for your application and the ability to refresh the access token when it expires without prompting the user to re-authenticate.
Enter values for the Sign-in redirect URIs. This is the callback from Define a callback route. Add values for local development (for example,
http://localhost:8080/authentication/login-callbackfor Blazor) and production (for example,
If your OpenID Connect client has multiple redirect URIs and you want to use a single redirect URI with a wildcard for the subdomain, select the Allow wildcard * in sign-in redirect URI checkbox.
Caution: The use of wildcard subdomains is discouraged as an insecure practice, since it may allow malicious actors to have tokens or authorization codes sent to unexpected or attacker-controlled pages. Exercise caution if you decide to include a wildcard redirect URI in your configuration.
See the parameter Details section on the Apps API Reference page for configuration guidance on the use of wildcard subdomains.
In the Trusted Origins section, add the Base URI of your application during local development, such as
http://localhost:8080. Also, add any base URIs where your application runs in production, such as
https://app.example.com. These URIs are added as trusted origins in your Okta org and can be managed by navigating to Security > API and selecting the Trusted Origins tab. See Enable Trusted Origins.
In the Assignments section, select Allow everyone in your organization to access for everyone to access your app, or Limit access to selected groups and specify the groups that can access your app.
Click Save to finish creating the Okta app integration.
On the General tab, scroll to General Settings and click Edit.
If Refresh Token is selected as a Grant type, the Refresh Token section appears. Refresh token rotation is automatically set as the default refresh token behavior.
Note: The default number of seconds for the Grace period for token rotation is set to 30 seconds. You can change the value to any number between 0 and 60 seconds. After the refresh token is rotated, the previous token remains valid for this amount of time to allow clients to get the new token. Using a value of 0 indicates that there is no grace period.
In the LOGIN section, specify an Initiate login URI to have Okta initiate the sign-in flow. When Okta redirects to this URI (for example,
https://example:0000.com/login), the client is triggered to send an authorize request. This URI is also used when users reset their passwords while signing in to the app. Okta redirects the user back to this URI after the password is reset so that the user can continue to sign in.
Click Save to update the Okta app settings.
XMLHttpRequest to the Okta API with the Okta session cookie. For instructions on setting trusted origins, see Grant cross-origin access to websites.
Note: You should only grant access to specific origins (websites) that you control and trust to access the Okta API.