Define the sign-out callback

Signing out of Okta requires the app to open a browser and navigate to the end session endpoint. Okta ends the user's session and immediately redirects the user back to your application. To do this, you must define a callback route for the sign-out process, which means that you need to whitelist the post sign-out URL in your Okta application settings. If you don't specify a post_logout_redirect_uri, then the browser is redirected to the Okta sign-in page.

Open your Okta Developer Console:

Go to Console

1. Select Applications, and then select your application.

2. Select General and click Edit.

3. In the Logout redirect URIs section, add the base URI of your application.

   • Android
   • Angular
   • ASP.NET
   • ASP.NET Core 2.x
   • ASP.NET Core 3.x
   • iOS
   • Node Express
   • React
   • Spring Boot
   • Vue.js

   Signing out of Okta requires the app to open a browser and navigate to the end session endpoint. Okta destroys the user's session and immediately redirects back to your application. To do this, you must define a callback route for the sign-out process.

   Make sure that the endSessionRedirectUri in OIDCConfig is the same as the one defined in the Logout redirect URI section. For example, if you are creating the OIDCConfig by builder:

   config = new OIDCConfig.Builder()
       .clientId("{clientId}")
       .redirectUri("com.okta.example:/login")
       .endSessionRedirectUri("com.okta.example:/logout")
       .scopes("openid", "profile", "offline_access")
       .discoveryUri("https://com.okta.example")
       .create();
   

   Using a JSON file:

   {
     "client_id": "{clientId}",
     "redirect_uri": "com.okta.example:/login",
     "end_session_redirect_uri": "com.okta.example:/logout",
     "scopes": [
       "openid",
       "profile",
       "offline_access"
     ],
     "discovery_uri": "https://com.okta.example"
   }
   

4. Click Save.

Next: Sign users out of Okta