Oracle Access Manger Windows Native Authentication (WNA) Login Scenarios
(Doc ID 1278339.1)
Last updated on FEBRUARY 03, 2020
Applies to:Oracle Access Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Oracle Access Manger WNA login Scenarios...
When the browser being used is configured to use Integrated Windows Authentication and
a resource that this protected by OAM kerb auth module is called…
If a Kerberos ticket is identified (received by OAM - irrespective of the domain), it is tried to be authenticated against the KDC configured with OAM. If Authentication fails, user is denied access.
If a NTLMSSP ticket is identified (received by OAM) authentication fails
If the browser being used is not configured to use Integrated Windows Authentication. When a resource that this protected by OAM kerb auth module, no TGT is supplied, a browser basic auth windows is displayed; where you can enter a valid username/pwd format combination that is defined by the default OAM Identity store User login attribute. In other words if a Kerberos ticket can't be identified (received by OAM- irrespective of browser, OS, domain-login etc), fallback mechanism will be invoked.
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
|Oracle Access Manger WNA login Scenarios|