OAuth 2.0 Authentication Token from Opa Hub for REST API not Succesfull from Postman (Doc ID 2696850.1)

Last updated on JULY 01, 2024

Applies to:

Oracle Policy Automation - Version 12.2.14 and later
Information in this document applies to any platform.

Symptoms

Symptoms:
----------------
OAuth 2.0 authentication token from OPA hub for REST API not successful from Postman.

Steps to reproduce the issue:
-----------------------------------------
Give the Access Token Authentication a name.
Select Client Credentials
Auth URL: https://your_site_interface/opa-hub/api/auth
Enter the API Client you created or decided to use
Enter the password you set up.
Select Send client credentials in body
Click Request Token

Error:
--------
Error:Error: Could not complete OAuth 2.0 token request: {"\n\n\nError 404--Not Found\n\n\n
\n

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

\n\n\n\n\n\n"}