Skip to main content

Question

 Jeff Myers (JeffM968)
Coforge

Coforge
US
JeffM968 Member since 2016 3 posts
Coforge
Posted: Nov 28, 2023
Last activity: Jan 8, 2024
Posted: 28 Nov 2023 12:59 EST
Last activity: 8 Jan 2024 9:39 EST
Closed

Authentication Profile: Set content-type header as application/json

Hello,

When getting an access token from an OAuth 2.0 Authentication Profile we need to set the content-type header as application/json. 

We see that in this case Pega automatically sets the content-type to application/x-www-form-urlencoded.

How do we set the content-type header to application/json for an OAuth 2.0 Authentication Profile rule?

Thanks

 

***Edited by Moderator Marije to add Capability tags***
To see attachments, please log in.
Pega Platform 8.8.3
Data Integration
Security
System Administration

  • John Paul Raja Christu Raja
Posted: 10 months ago
Updated: 10 months ago
Posted: 8 Jan 2024 9:34 EST
Updated: 8 Jan 2024 9:39 EST
Marije Schillern (MarijeSchillern)
MOD
Senior Knowledge Management Specialist
Pegasystems Inc.
GB

@JeffM968 do you still need help with this issue?

Did you already find the below?

How to pass the body of request in urlencoded form?

Connect Rest with application/x-www-form-urlencoded

How to set Content-type as application/json;charset=UTF-8 in a failed authentication response at service package level

Connect-REST content-type: "application/JSON" not setting in the out going request

Access token response

To see attachments, please log in.

Related content:

Question Solved

Connect-REST content-type: "application/JSON" not setting in the out going request

Question

How to set Content-type as application/json;charset=UTF-8 in a failed authentication response at service package level

Question Solved

Issue retrieving shared link from BOX as Pega resets content-type as multipart message instead of application/json

Question Solved

Why REST Service cannot parse json request if Content-Type header is equal to application/json;charset=UTF-8.

Question

connector with Content-type application/x-www-form-urlencoded is not supported

Question

Is it possible to remove the Content-Type (text;charset=UTF-8) in a 401 Unauthorized REST Service Response

Question

Handle Application/pdf, Application/json response in Connect-Rest

Question

PegaDynamicAuthentication Authentication profile

Question

Proxy settings for the Authentication profile for getting the token

Question

Authentication Profile for rest connector

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice