E-IB: Inbound REST Service Using OAuth2 Token Fails With "Error loading Signing Key from Azure due to IOException or ParseException" Error (Doc ID 2934409.1)

Last updated on MAY 29, 2023

Applies to:

Symptoms

When sending in a request message to a PeopleSoft Provider REST service using OAuth2 authorization/authentication token, it fails with an HTTP 401 "Not Authorized" error, and the following errors are found in the Integration Broker (IB) errorLog.html.

 
Error in the IB errorLog.html
----------------------------------

Steps to replicate:

-----------------------

1. In the Postman web service tool, fetch an OAuth2 token.

2. Post the message to PeopleSoft.

3. Observe the HTTP 401 "Not Authorized" error in Postman, and the errors above in the IB errorLog.html.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.