unable to login OAS -dv re-direct will continuously loop from SSO authentication to Application

Subha Tripathy

Organization Name

Harvard University

Description

We are facing issue with the dv url , After we log off from dv, when we try to login again, we see re-direct will continuously loop from Harvard Key to OAS and you wont be able to login. 

Steps to reproduce: 
Log into OAS-CONV: hart.conv.biprod.huit.harvard.edu/dv/ 
Log out of OAS-CONV 
Attempt to login into OAS-CONV again: hart.conv.biprod.huit.harvard.edu/dv/ 
Here you will see that the re-direct will continuously loop from SSO to OAS and you wont be able to login 
Clear cache 
Log into OAS-CONV: hart.conv.biprod.huit.harvard.edu/dv/ 
Now you can log in again 

Where as Analytics url is working perfectly fine. 

as per oracle support, in the below SR: 

Basically, any approach that needed to open, modify, repack and redeploy any of the *.ear files is not applicable for OAS. Why? It is prone to errors and more than one problem. The easiest example is what happens when you apply a patch, new ear files might be provided with it and those will overwrite your modified files and thus SSO will break.  
SR 3-23522634751 : unable to login OAS -dv re-direct will continuously loop from SSO authentication to Application

Which is not in the case of Analytics.

Requesting to provide a permanent fix for the same.

Use Case and Business Need

Install OAS 5.5.0, configure SSO using SAML2 authentication. 

configure load balancer for analytics and dv.

Steps to reproduce: 
Log into OAS-CONV: hart.conv.biprod.huit.harvard.edu/dv/ 
Log out of OAS-CONV 
Attempt to login into OAS-CONV again: hart.conv.biprod.huit.harvard.edu/dv/ 
Here you will see that the re-direct will continuously loop from SSO to OAS and you wont be able to login 
Clear cache 
Log into OAS-CONV: hart.conv.biprod.huit.harvard.edu/dv/ 
Now you can log in again 

More details

We migrated from OBIEE 12.2.1.4.0 to OAS 5.5.0. Large number of users will be using OAS environment, and its not possible for us to use different authentication methods for analytics and dv as our users are authenticated through sqlauthenticator oracle database.

So this change will put an high impact on our up coming migration to OAS. 

Original Idea Number: 4607ca57b1