Single Page Application Not Handling HTTP 302 (Redirect) From SSO Logic
(Doc ID 2938005.1)
Last updated on AUGUST 29, 2024
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.3.1.10 and laterInformation in this document applies to any platform.
Symptoms
On : 11.3.1.10 version, General
ACTUAL BEHAVIOR
---------------
While upgrading from V10.2.0.39 to V11.3.1.13, users have encountered a number of "Intermittent Issues".
A majority of these "Intermittent Issues" have been traced back to the fact that V11 (which is a "single page" application) is not properly handling HTTP 302 (Redirect) from SSO logic.
Changing the 'Session Update Time' in Siteminder Agent configuration from 23 minutes to 4 hours has limit the occurrences of these "Intermittent Issues".
EXPECTED BEHAVIOR
-----------------------
The OIPA application should be built to properly handle HTTP 302 (Redirect) that come from SSO integration after the user has been logged in longer
than the "Sessions Update Time" configured in our ADMINS00 Siteminder Agent.
Need the V11 base code to be updated to properly handle HTTP 302 (Redirect) from theSSO logic.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an SSO enable environment.
2. Login and process any sort of actions for an elapsed time that exceeds the "Sessions Update Time" .
3. Workaround is to have users can just logoff, logon, and try it again.
Cause
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
Symptoms |
Cause |
Solution |
References |