Oracle Access Manager (OAM) Protected Resource URL Does Not Use Expected Authentication Scheme
(Doc ID 2866786.1)
Last updated on MAY 12, 2022
Applies to:Oracle Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Calling a protected resource works but uses the wrong authentication scheme
Two protected urls:
- http(s)://<FQDN_RESOURCE1> with type 1 authentication
- http(s)://<FQDN_RESOURCE2><QUERY_STRING_VALUE> with type 2 authentication
When accessing ...
http(s)://<FQDN_RESOURCE><QUERY_STRING_VALUE> type 1 authentication is triggered.
Why, the expectation is that the type 2 authentication would be triggered?
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