Oracle Access Manager (OAM) 3-Legged OAuth Series Part 1 Of 2
(Doc ID 2832382.1)
Last updated on NOVEMBER 21, 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.
Disclaimer
Postman is a Third Party product.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Third Party product core components functionality falls outside of Oracle/OAM Support. All Support has is what is in the Current Product documentation and KM notes (Past experiences). There may come times when there are issues with said Third Party Product, that OAM support may not be able to resolve, which will require the customer to utilize additional non Oracle resources to resolve.
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?
This document will discuss ...
What artifacts need to be created and how to do so.
All the artifacts for OAuth flows have to be created via the newly exposed REST commands.
There is no User Interface (UI) support for the creation of these artifacts.
The important artifacts to get started are Identity Domain, Resource Server and Client.
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!
