I am trying to implement Okta session timeout for my angular 19 and Sprint boot application, I am using okta 6.3.0 version, and my session timeout is 30minutes. I am able to signout of the application successfully and see the okta sign in page with back to sign in option, when i hit the back to sign it is redirecting to the okta dashboard and not my application login.
As a user, back to sign-in should redirect to my application sign-in page how do I implement the same.
To me this sounds like there isn’t a post_logout_redirect_uri being sent by your application during signout. That parameter tells Okta where the user should be redirected after the signout redirect occurs, but when it is not sent, the default behavior is for the user to land on the regular Okta login page. When a user logs in from the default login page, there is no application context available and the user will only be logged into the Okta Dashboard (or the default app for your brand, if its been customized).
Can you check the network events during this logout to confirm whether or not that is the case? You should be able to see what parameters are being sent to /v1/logout, though you will need to ensure you have the “Preserve logs” option enabled in your network tab to track all the requests that happen before and after browser redirects.
I have this as part of my request URL in my network tab → post_logout_redirect_uri=http%3A%2F%2Flocalhost%3A4200%2Flogin, And I am configuring the post logout redirect URI for my session timeout like this
async logout() {
try {
console.log(‘Calling oktaAuth.signOut…’);
await this.oktaAuth.signOut({
postLogoutRedirectUri: window.location.origin + ‘/login’
});
} catch (error) {
console.error(‘Logout failed’, error);
}
}
Can you share some screenshots of what you’re seeing during this flow? For example, where are you are hitting back to sign in?