How to Enable CRUD (create, read, update, delete) Operations via REST APIs for the OAM OAuth SecretKey
(Doc ID 2937021.1)
Last updated on JULY 26, 2024
Applies to:
Oracle Access Manager - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Goal
In OAM 12c, the lifecycle for OAuth secret keys using REST APIs is not allowed. The only possible action is to create a secret key using a BASIC authorization header.
However, in OAM 11g it was possible to create, get, update, and delete a secret key using an access token (BEARER authorization header).
What steps are required to allow the same secret key operations via REST APIs in OAM 12c?
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! |
In this Document
Goal |
Solution |
References |