I am unable to connect to an external services via REST connector with an Authentication Profile configured with an Oauth 2.0 Provider with Client Credentials Grant Type, Basic authentication scheme, configured an access token endpoint URL and send token access in header.
With the above mentioned configuration provided by the API market where the Rest services are exposed. I always get a HTTP Status Response 403 Forbidden.
If i try from postman with the same configuration i can get the access token properly with the same client ID and Credentials and get a proper response from the service.
I wonder whether i am missing some kind of Auth profile, Oauth 2.0 Provider rule or i can use Pega Rest connector to achieve this as it is not implemented to use this type of configuration with Client Credentials obtaining access token through endpoint url.
Please have a look at the attached document with screenshots of exception, log files, tracer some questions and my final conclusion.
Any help on this would be much appreciated. It is urgent for us to connect to this external Rest service.
Rest connector test connectivity iseems to be k. See attached word document wit test connectivity outcome.
The issue seems to be the authentication that it is failing. i could be missing something or the type of authenticaiton am using it is simply not supported by PEGA.
Find attached a documetn with rules configuration in our system and test performed.
Find attached tracer xml file of a failure execution.
You will see in screenshots attached in last documents that we we have to provide an Authorization header (Bearer type) with a JSON Web Token (JWT) when calling a REST Connector for server to server authentication.
I have just read that Pega version 8.2.5 does no support Authorization header of bearer type and JWT, is that correct? if so, is there any workaround or way to fix this? I mean it is posisible to make a REST connector works with this type of authorization by customizing activities, java steps, etc ...