OAuth Clients can be assigned privileges or roles. The documentation describes both ways: https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/19.1/aelig/OAUTH-reference.html#GUID-7887BC66-6D42-…
Privileges for the client can be specified at the time of creating the OAuth Client using the p_privilege_names parameter of OAUTH.CREATE_CLIENT procedure.
Privileges can also updated after a client has been created using the p_privilege_names parameter of the OAUTH.UPDATE_CLIENT procedure.
If you already have a role with all of the privileges assigned that you would like assigned to the OAuth client, after the client is created, you would use OAUTH.GRANT_CLIENT_ROLE to assign the role and all of its privileges to that OAuth Client. OAUTH.REVOKE_CLIENT_ROLE can be used to remove the role from the client if needed.
Apologies for the delay in replying. Thanks for the info, it helped a lot.
The problem I am seeing (from Postman) is when I have an OAUTH client with a privilege directly assigned to it, it will not let me get a token. I am not sure if this is to do with Postman itself or not.
I shall give it a try in getting the token via CURL and see what is the outcome.
Are you using HTTPS? If you try and send a POST request to the token request endpoint (http://localhost:8080/ords/schemaalias/oauth/token ) you will receive an error saying that the resource can only be accessed over HTTPS.
If you want to use OAuth over HTTP, you will need to edit your defaults.xml and add the following entry: