When Configured For Web Single Sign On (WebSSO) Using Oracle Access Manager (OAM), The Username Field Is Blank After OAM Intercepts The Requests And Redirects Back To Primavera P6 Login Page Or Recieve Error: "404 Not Found"
(Doc ID 1580267.1)
Last updated on OCTOBER 16, 2023
Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version 7.0 and laterInformation in this document applies to any platform.
Symptoms
Using Oracle Access Manager (OAM) 11.1.1.5, configured to use an 11g Webgate with Oracle HTTP Server:
ACTUAL BEHAVIOR
-----------------------
ACTUAL BEHAVIOR #1:
- When connecting to a web product (P6 EPPM) hosted under WebLogic and using the Oracle HTTP Server as a proxy (also configured with a OAM webgate 11g), the webgate 1) intercepts the request, 2) presents the user with the Authentication scheme configured for the web product, 3) directs the user back to web application configured with OHS, but does not pass the OAM_REMOTE_USER header key to populate automatically the applications username field (which is what the application is designed to use by default).
ACTUAL BEHAVIOR #2:
- Another symptom is when connecting to a web product (P6 EPPM) hosted under WebLogic and using the Oracle HTTP Server as a proxy (also configured with a OAM webgate 11g), the webgate 1) intercepts the request, 2) presents the user with the Authentication scheme configured for the web product, 3) directs the user back to web application configured with OHS, but when directed back to the Web Application, the following error occurs -- "404 Not Found; The requested URL /p6/action/login was not found".
EXPECTED BEHAVIOR
-----------------------
After successful authentication of OAM, for the application to launch and the header key to be passed to the application. The default header key configured with the web product = OAM_REMOTE_USER.
ENVIRONMENT ASSUMPTIONS (to rule out environmental setup issues)
-----------------------
- P6 (web product) was set to WebSSO within the P6 Administration Application and pointing to OAM_REMOTE_USER as the header key
- P6 (web product) was configured as a proxy plugin to an HTTP server (example = OHS, using "How To Configure Oracle HTTP Server (OHS) 11g As A Proxy To WebLogic For Primavera P6 Web Applications (Doc ID 1446675.1)")
- The proxy plugin was configured for the OAM Webgate
- An OAM application domain was created and configured to protect the web application context root (example = /p6 & /p6/)
- Connection to P6 (web product) is being made through the web tier configured for a proxy to P6 and with the OAM Webgate (and a direct connection to the weblogic node is not being used)
-----------------------
- P6 (web product) was set to WebSSO within the P6 Administration Application and pointing to OAM_REMOTE_USER as the header key
- P6 (web product) was configured as a proxy plugin to an HTTP server (example = OHS, using "How To Configure Oracle HTTP Server (OHS) 11g As A Proxy To WebLogic For Primavera P6 Web Applications (Doc ID 1446675.1)")
- The proxy plugin was configured for the OAM Webgate
- An OAM application domain was created and configured to protect the web application context root (example = /p6 & /p6/)
- Connection to P6 (web product) is being made through the web tier configured for a proxy to P6 and with the OAM Webgate (and a direct connection to the weblogic node is not being used)
Changes
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 |