Triggering an integration using Oauth 2.0 fails with 401 Unauthorized / The path to the certificate is invalid
(Doc ID 2600295.1)
Last updated on OCTOBER 17, 2019
Applies to:
Oracle Integration - Version 17.4.1 and laterInformation in this document applies to any platform.
Symptoms
Triggering an integration using an Oauth 2.0 token fails with 401 Unauthorized. In the logfiles, the following errors related to certificates can be seen:
[2019-09-30T18:20:35.590+00:00] [xxxxxxx_server_1] [ERROR] [] [oracle.wsm.resources.security] [tid: [ACTIVE].ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 168c82ba-330f-4191-aca1-e0ee78e4c2ef-00108ec0,0] [APP: Cloud Adapter Inbound Http App] [partition-name: DOMAIN] [tenant-name: GLOBAL] [oracle.wsm.policy.name: oracle/multi_token_rest_service_policy] The path to the certificate is invalid. [[
Validation failed for the certificate "Subject DN:- CN=idcs-xxxxxxxxxxxxxxxxxxxxxxx, CN=Cloud9, CN=sslDomains, Serial Number:- xxxxxxxxxxxx, Issuer DN:- CN=Cloud9CA-2, DC=cloud, DC=oracle, DC=com", Failed due to : Path does not chain with any of the trust anchors.
]]
[2019-09-30T18:20:35.591+00:00] [xxxxxxx_server_1] [ERROR] [WSM-00062] [oracle.wsm.resources.security] [tid: [ACTIVE].ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 168c82ba-330f-4191-aca1-e0ee78e4c2ef-00108ec0,0] [APP: Cloud Adapter Inbound Http App] [partition-name: DOMAIN] [tenant-name: GLOBAL] [oracle.wsm.policy.name: oracle/multi_token_rest_service_policy] The path to the certificate used for the signature is invalid.
]
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |