Oracle Integration · REST-based adapters
403 error when accessing an OAuth-protected API
Short answer
A 403 from an OAuth-protected API in Oracle Integration means the access token does not grant access to the API being called. Examine the OAuth configuration carefully.
VerifiedLast verified
01Error text
403 error (forbidden)02Likely causes
- The access token was obtained for a scope that does not cover the API being accessed.
- The user who gave consent is not the resource owner or owner of the API.
- The access token expired or is no longer valid.
- The authorization server revoked access to the resource.
03How to fix it
- Examine the OAuth configuration carefully.
- Work with the target API owner or administrator. The authorization server best describes the exact cause.
04Official documentation
→Related errors
- 401-Unauthorized with basic authentication when MFA is enabledA 401-Unauthorized when you invoke Oracle Integration with basic authentication can mean the identity domain is configured with multi-factor authentication, which basic authentication does not support. Disable multi-factor authentication for the account used with basic authentication.
- Certificate import fails: extra data given to DerValue constructorThis Oracle Integration log error appears when importing a certificate issued by a certificate authority fails. Obtain a fixed certificate from the certificate authority.
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