My Oracle Support Banner

E1:ORCH OAuth2.0 ClientID And Client Secret Should Be Added To The Request Body Not HTTP Header (Doc ID 2477782.1)

Last updated on NOVEMBER 22, 2019

Applies to:

JD Edwards EnterpriseOne Orchestrator - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Customer wants a way to indicate if an OAuth parameter, defined in the softcoding (connection), is added to the header or body of the Oauth request when oauth authentication is performed. This is used in an external rest connection.

Putting the client id in the client secret values in the http body instead of the request header as office 365 needs them in the body. If put them as parameters, it works perfectly fine, however it's a bit confusing if you have those as separate inputs.

OAuth2 Connections with Office 365 don't work out of the box. If supply a Client ID and Client Secret values, those are added to the HTTP header instead of the request body. Office 365 needs them in the body. There needs to be an option to specify if they should be added to the header or the post body request.


Changes

 

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
Changes
Cause
Solution
References


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