Oracle Integration · REST Adapter (RPST security policy)
RPST and OCI Service Invocation: NamespaceNotFound
Short answer
A 404 NamespaceNotFound through the Oracle Integration REST Adapter with the RPST and OCI Service Invocation policy means the policy or dynamic group is not set correctly. Set the policy to perform the required operations.
VerifiedLast verified
01Error text
{"code":"NamespaceNotFound","message":"You do not have authorization to perform this request, or the requested02Likely causes
- The OCI Service Invocation policy is not set for the operations needed.
- The dynamic group is set to the instance ID. RPST expects the resource ID, not the instance ID.
03How to fix it
- Set the policy to perform the required operations.
- When creating the dynamic group, set
resource.id = 'client_ID', where client_ID is the client ID of the OAuth application of your Oracle Integration instance.
04Official documentation
→Related errors
- OAuth: The token has already been consumedThis REST Adapter error in Oracle Integration means the connection could not refresh its access token, because no refresh token was received or the refresh token expired. Verify that the connection receives a refresh token. Make sure the scope includes offline_access.
- OCI Object Storage Search API returns 401 NotAuthenticatedThis 401 from the OCI Object Storage Search API through the Oracle Integration REST Adapter usually points to invalid credentials or an unsupported wildcard search. Make sure the file name being searched does not contain the character.
- RPST and OCI Service Invocation: BucketAlreadyExistsA BucketAlreadyExists error through the Oracle Integration REST Adapter can mean the policy only lets the dynamic group read buckets, so creating a bucket fails. Create a policy that allows writing to the bucket.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Oracle Integration work:Open Oracle Integration jobsOracle Integration rates and salaries