Oracle Access Manager (OAM) 3-Legged OAuth Series Part 2 Of 2
(Doc ID 2832947.1)
Last updated on JULY 31, 2024
Applies to:
Oracle Access Manager - Version 12.2.1.3.0 and later Information in this document applies to any platform.
Goal
The following Information is from a previous Oracle blog post that is no longer available. This is a living document and will be modified/improved as needed.
Oracle Access Manager (OAM) 12c is a full-fledged OAuth server supporting 2-legged and 3-legged flows across Multi Data Centers (MDC).
This is the document is the first of a 3 part series which talks about the following ...
What are the artifacts in OAM for OAuth/OIDC, how do we create them?
How do we setup OAM/OAuth Server to support the 3-legged flows?
In the previous part, Oracle Access Manager (OAM) 3-Legged OAuth Series Part 1 Of 2 (Doc ID 2832382.1), it discussed the necessary artifacts and how they are created.
This document will discuss ...
How a Client Application (DemoClientId - which we created previously) can initiate a browser based 3 Legged OAuth flow(AuthZ Code or Implicit) against the OAM/OAuth Server.
Solution
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
