Unable to Create Agile SDK Session After Redirecting Load Balancer Non-SSO URL to SSO URL
(Doc ID 2829656.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Agile PLM Framework - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
Unable to create Agile SDK session using load balancer URL after redirecting non-SSO URL: /Agile/default/login-cms.jsp to SSO URL: /Agile/PLMServlet
Expected Behavior
- Able to create Agile SDK session using load balancer URL. SDK session needs to be load balanced
- Web Client users accessing to non-SSO URL: /Agile/default/login-cms.jsp will be redirected to SSO URL: /Agile/PLMServlet
To be SSO authenticated, users must access to Web Client using SSO URL: https://{server_name}.{domain_com}/Agile/PLMServlet
Facts
- Hardware load balancer (i.e. F5) is being used as load balancer
- URLs accessed by Web Client and SDK are pointing to load balancer URL
Steps
The issue can be reproduced at will with the following steps:
- Implement SSO to Agile
- Configure hardware load balancer to redirect non-SSO URL:
- Fails to create SDK session
Changes
Below changes are made:
- Configured Single Sign On (SSO) to Agile Application Server
- Configured hardware load balancer to redirect non-SSO URL to SSO URL
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 |
Changes |
Cause |
Solution |
References |