You need to configure PPM to accept headers from a successful Oracle Access Manager authentication in order to automatically log in to the PPM applications.
- Notes: For OAM and OHS version 12.2.1.4, make the following configuration changes to make it work with PPM application:
- In OHS, comment the below line in the “httpd.conf” file:
Header always set X-Content-Type-Options nosniffFile Location: {OHS_HOME}/user_projects/domains/{ohsinstance}_domain/config/fmwconfig/components/OHS/{ohsinstance}/ - In OAM, add the following line in the “User Defined Parameters” in OAM webgate through OAM console:
X-Content-Type-Options=false - The above OHS and OAM settings are however not applicable for PPM 19.0.1.0 and later versions.
PPM can be configured to accept any HTTP header variables. Configure the following registry values to control the names and values of the HTTP header variables used for integration:
Note: all registry values discussed below may be inserted into the Registry under the key: HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Primavera Portfolio Management\Portfolios\Server\UI
Registry Value: SSO Authentication Type HTTP Header Name (String)
- Data: The name of the HTTP header variable that contains the authentication type.
- Default: OAM_AUTH_TYPE
Registry Value: SSO Authentication Type HTTP Header Value (String)
- Data: The value assigned to SSO Authentication Type HTTP Header and indicates that the service provider authenticate users.
- Default: Negotiate
Registry Value: SSO Authenticated User HTTP Header Name (String)
- Data: The name of the HTTP header variable that contains the name of the user authenticated by SSO.
- Default: OAM_REMOTE_USER
Registry Value: Registry Value "SSO Logout URL" (String)
- Data: The value of SSO Logout URL that redirects user to the SSO Logout screen.
- Default: SSO Logout URL
Note: PPM uses the "raw" HTTP header interface. As a result, the name of the HTTP headers within PPM registry entries should include the "HTTP_" prefix.