Oracle Integration · REST Adapter connection
REST service invoked by the REST Adapter returns 401 Unauthorized
A 401 Unauthorized from a REST service invoked by the Oracle Integration REST Adapter can mean the application credentials on the Connections page are no longer valid. Test the endpoint configuration that uses the connection. The Connections page does not validate credentials, so a successful connection test may not be sufficient.
VerifiedLast verified
01Error text
401 Unauthorized02Likely causes
- The application credentials configured on the Connections page may no longer be valid.
03How to fix it
- Test the endpoint configuration that uses the connection. The Connections page does not validate credentials, so a successful connection test may not be sufficient.
- Update the credentials on the connection if they are no longer valid.
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: NamespaceNotFoundA 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.
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