Developing API Clients against Oracle Access Management Protected Applications
(Doc ID 2835887.1)
Last updated on JANUARY 27, 2022
Applies to:Oracle Access Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Oracle Access Management (OAM) seamlessly integrates your identities and systems to secure access from anywhere, at any time, and by any method by delivering risk-aware, end-to-end user authentication and single sign-on (SSO). Applications are protected by specifying access control policies that are enforced by the OAM WebGate.
OAM is used by Users accessing legacy and modern applications using Browsers. To improve the User Experience, application developers have adopted new approaches like Single Page Applications (SPAs), AJAX Clients to improve/augment/replace current applications. As a result, API clients are increasingly being used to access OAM protected applications.
Provided by Development
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
|API Client Interaction vis-à-vis OAM|
|Considerations for developing API Clients|