OAM Impersonation Results in 500 Internal Server Error at Impconsent.jsp Page
(Doc ID 2193901.1)
Last updated on APRIL 30, 2023
Applies to:Oracle Access Manager - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 11g]
Information in this document applies to any platform.
OAM Impersonation is not working in certain scenarios in OAM 220.127.116.11 and 18.104.22.168.
When OAM is front-ended with a LBR/proxy server, starting impersonation might result in HTTP/1.1 500 Internal Server Error when calling impconsent.jsp page (e.g http(s)://lbr_hostname:lbr:port/oam/pages/impconsent.jsp?request_id=....).
The following errors can be seen in OAM server logs:
- 'UnknownHostname' error
- 'java.net.ConnectException: Tried all: 1 addresses, but could not connect over HTTP to server <lbr_hostname>:<lbr:port>' (if there is a firewall blocking connections from Weblogic server to LBR)
- 'bad_certificate' error when the LBR is configured on SSL (if the Weblogic server is unable to validate the LBR certificate)
Start impersonation using a load balancer or a proxy server front-ending OAM servers instead of OAM server hostname.
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