Could not get access token when using JWT Token Profile in Authentication profile- OAuth 2.0 authentication issue.
Hello,
I am having a bit of an issue on how to use JWT profile as authentication schema within Authentication Profile.
We have created the Authentication Profile with JWT profile as authentication schema and when we run the REST connector with authentication profile, Its giving below error.
Access token endpoint invocation failed : {ErrorMessage=Response status : 400 Bad Request, statuscode=400}
* Attached Debug Details
Plus, if we used the same data (which is pass from pega side) in postman, its working fine and it's returning the token.
Thanks,
Nuwan
***Edited by Moderator Marissa to add Support Case details***
***Edited by Moderator Marije to add Enhancement (BUG-861639 ) tag***
Accepted Solution
Updated: 8 Nov 2024 15:37 EST
Evonsys
NL
@MarijeSchillern INC-B948 was created and provided enhancement in 23.1.2 version.
Pegasystems Inc.
GB
@NuwanD54 The error message indicates a "400 Bad Request" response, which typically means that the server could not understand the request due to invalid syntax. This could be due to an incorrect JWT token, incorrect reference of the JWT token in the Authentication Profile, or incorrect settings in the Authentication Profile.
Creating an Authentication profile
if you are unable to get help on the forum I suggest that you log a support incident via the MSP. Please provide the INC id here so we can help track it.
Accepted Solution
Updated: 8 Nov 2024 15:37 EST
Evonsys
NL
@MarijeSchillern INC-B948 was created and provided enhancement in 23.1.2 version.
Pegasystems Inc.
GB
@NuwanD54 I really appreciate you having shared this information.
To recap, service provider requires x5c header which is String list, that is currently not supported in header of JWT token profile.
Value List supported for headers in token profile When using a JWT profile as authentication schema within Authentication Profile, running the REST connector with authentication profile generated the error "Access token endpoint invocation failed". To address this, support has been added for a Value List for headers in token profile.
So that all users might benefit from your update, I will provide the full list of product versions where issue has been corrected:
Fixed in:
23.1.2: BUG-861639,
24.1.2: BUG-881836
24.2: BUG-881837