OAUTH Client can not be approved when privilege field is modified
(Doc ID 2736755.1)
Last updated on MARCH 12, 2021
Applies to:Oracle REST Data Services - Version 20.2.1 and later
Information in this document applies to any platform.
When creating an ORDS Client, it can be approved as long as the default Required Privileges (RESTful Service Editing) is not changed.
As soon as a custom privilege is added (or default value is replaced) the client can no longer be approved
create a client through: /oauth/clients/ UI and populate all the fields
Scenario 1: If the Required privileges keeps default value :RESTful Service Editing, the client can be approved and appears on the page: http://<hostname>:<IP>/ords/<schema>/oauth/approvals/
Scenario 2: If another privilege is added along with RESTful Service Editing or a single custom privilege is in that field, the OAUTH client can no longer be approved.
When trying to approve, the redirect returns
in the URL
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