Register today for Oracle CloudWorld. October 17th - 20th, Las Vegas

Register now

Hillel Cooperman, Senior VP of User Experience Design, has a message for you on Oracle CloudWorld

Watch now
Oauth 2.0 causes errors with co-located integration — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Oauth 2.0 causes errors with co-located integration

Accepted answer
31
Views
8
Comments

Summary:

Can't call co-located integration when initial integration is Oauth 2.0 and is called from an external source. Looking for the easiest to implement resolution and to understand why the error happens in the first place.

Content (required):

I am working on a set of two integrations in Oracle Integration Cloud. Integration A (REST) will call Integration B (SOAP). In order to trigger Integration A I need to provide a bearer token.

When I send a POST request to Integration A within OIC (by clicking the "play" button --> "Test" link --> submitting a POST request in the OIC test console) Integration B triggers successfully. However, when I send a POST request from an external source (Postman software on my laptop), Integration A fires but when it gets to the point of triggering Integration B, there is an error:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!