Oracle Access Manager (OAM) OpenID Connect (OIDC) Client Integration Flow Uses Incorrect "redirect_uri"
(Doc ID 2939248.1)
Last updated on AUGUST 01, 2024
Applies to:
Oracle Access Manager - Version 12.2.1.4.0 to 12.2.1.4.230106 [Release 12c]Information in this document applies to any platform.
Symptoms
Accessing protected resource goes to the third-party server using incorrect redirect_uri=http(s)://<OAM_SERVER_FQDN>:<PORT_VALUE_1>/oam/server/auth_cred_submit, instead of redirect_uri=http(s)://<OAM_SERVER_FQDN>:<PORT_VALUE_2>/oam/server/auth_cred_submit.
- Configure Oracle Access Manager (OAM) with an OIDC Client (e.g Keycloack) using OpenIDConnectPlugin per 39 OIDC Client Integrations with Social Identity Providers
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 |
| References |