OAM OpenIDConnectPlugin Access Token EndPoint Fails Resulting KEY_USERNAME Not Being Set
(Doc ID 2967382.1)
Last updated on AUGUST 14, 2023
Applies to:Oracle Access Manager - Version 126.96.36.199.230317 and later
Information in this document applies to any platform.
OAM as OpenID proxy fails with error : "An incorrect username and password are specified"
IDPorten/DIFI and IDCS are configured using OpenIDConnectPlugin. While using OpenIDConnectPlugin the connection to the token endpoint is failing resulting in the KEY_USERNAME parameter not being set/passed to downstream plugins. Access token is not getting generated and returns returned HTTP response code 400 i.e. "Bad Request"
Example : java.io.IOException: Server returned HTTP response code: 400 for URL: https://<URL>/oauth2/v1/token
Configured OAM 12c as OpenID proxy, IDPorten/DIFI and IDCS are configured using OpenIDConnectPlugin.
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