My Oracle Support Banner

Looping Occurs in SAML2 Authentication with Two Applications (Doc ID 2738719.1)

Last updated on JANUARY 08, 2024

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


SAML2 authentication environment:

    Client  ----+---- appA (deployed on WebLogic)
             ----+---- appB (deployed on WebServer)

When transitioning from appA to the page of appB that performs another SAML authentication, that works fine.
But when returning to appA, looping occurs in SAML2 Authentication.

Two JSESSIONIDs can be seen in network capture as below:

The issue can be reproduced with the following steps:

    1. Access appA from the client -> WebLogic sends JSESSIONID=A to the client.
    2. Access appB from the client -> WebServer sends JSESSIONID=B to the client.
    3. Access appA from the client again -> JSESSIONID=A and JSESSIONID=B are sent to WebLogic.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.