You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log in to App1 using a custom federated authenticator. Do not log out.
Attempt to log in to App2 using the same browser.
Behavior:
When credentials are entered on the App2 login page and submitted, the page reloads instead of proceeding. However, after the reload, the authenticator flow works as expected.
Note: This issue occurs only when the user is authenticated in the first app using a custom federated authenticator and then tries to SSO into another account from the same browser.
The following error appears in the server terminal:
[2025-02-10 01:37:46,714] [c7197e5a-94c5-4fce-8d3d-2ffaa893057b] ERROR {org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore} - Error while storing session data org.wso2.carbon.identity.application.authentication.framework.exception.SessionSerializerException: Error while serializing the session object
at org.wso2.carbon.identity.application.authentication.framework.store.JavaSessionSerializer.serializeSessionObject(JavaSessionSerializer.java:45)
at org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore.setBlobObject(SessionDataStore.java:742)
at org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore.persistSessionData(SessionDataStore.java:642)
at org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore.storeSessionData(SessionDataStore.java:484)
at org.wso2.carbon.identity.application.authentication.framework.cache.AuthenticationContextCache.addToCache(AuthenticationContextCache.java:127)
wjc-gojm-vmr.2025-02-10.01_37.GMT+5_30.mp4
Version
No response
The text was updated successfully, but these errors were encountered:
Description
Feature:
Erroneous Scenario:
Behavior:
When credentials are entered on the App2 login page and submitted, the page reloads instead of proceeding. However, after the reload, the authenticator flow works as expected.
Note: This issue occurs only when the user is authenticated in the first app using a custom federated authenticator and then tries to SSO into another account from the same browser.
The following error appears in the server terminal:
wjc-gojm-vmr.2025-02-10.01_37.GMT+5_30.mp4
Version
No response
The text was updated successfully, but these errors were encountered: