Question
Ministry of Justice - Spain
ES
Last activity: 13 Sep 2024 9:59 EDT
Authentication Profile Oauth2.0: need to pass header to access token endpoint
Hi,
We need to invoke a REST authentication service from our customer, in order to get the access token to authenticate Pega application when consuming other customer's REST services.
This access token service needs a header in order to return the access token.
From REST connector wizard if we call the access token endpoint and set an specific header we get the token in the response, but this can not be set in the Oauth 2.0 authentication profile rule.
Anyone knows how this can be addressed?
Thanks in advance.
Evonsys
AU
@JuanaMariaBlanco Did you get a solution for this? We have the same problem at the moment.
Updated: 19 Mar 2024 0:06 EDT
Maantic Inc
IN
@JuanaMariaBlanco So how this can be addressed is two fold api call . so basically Oauth is another api call which fetches bearer token in return.
What I suggest is create a rest for that and store the bearer token in node level data page.
Secondly when you do the actual endpoint REST call pass it under auth headers tag it should work fine.
I faced the same when consuming google API's did the same. Be sure to flush data page based on token expiration which will be part of the inital token response generally its 3600 seconds or 1hr just check it.
Corporaci?n Credomatic SA
CR
@Soham_Chanda1107 Pega ensures that this type of call is carried out without any problem, the request itself is authenticated and then that token is sent in the header or query param to the resource. Pega ensures that this type of call is carried out without any problem, the request itself is authenticated and then that token is sent in the header or query param to the resource.
but i have the same problem