Oracle Access Manager (OAM) Protected Resource URL Does Not Use Expected Authentication Scheme
(Doc ID 2866786.1)
Last updated on OCTOBER 06, 2023
Applies to:
Oracle Access Manager - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
Calling a protected resource works but uses the wrong authentication scheme
Scenario
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?
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 |