This article explains a Single Logout (SLO) failure that can occur when an application's session is longer than the Okta session. When the application sends an SLO request upon its own session timeout, Okta does not process it because the corresponding Okta session has already expired. This leaves the user improperly logged out from the broader session context.

• Single Logout (SLO)
• Security Assertion Markup Language (SAML)

The Single Logout (SLO) process fails because the Okta session expires independently and earlier than the application's session. When the application sends the SLO request, there is no active Okta session to receive and process it, preventing the logout from completing successfully.

To resolve this behavior, a specific feature must be enabled for the organization. Contact Okta Support and reference this article to have the feature enabled.