Question
1
Replies
37
Views
GE Medical Systems Polska Sp. z o.o.
Posted: April 6, 2020
Last activity: April 7, 2020
Closed
Pega 8.4 : Authentication Profile - Custom Provider miss Authorization code endpoint
For Authentication Profile, now we can only define Custom provider as Auth2.0 Provider rule was deprecated.
In the new version for Grand Type: Client Credentials -> Authorization code endpoint is not available as it used to be on the Auth2.0 Provider rule, which makes connection to fail. I already checked that changing Grant Type to "Authorization code" and defining Authorization code endpoint is not bringing any results - connection still fails.
Please let me know how I can define Authorization code endpoint using Grand Type as Client Credentials?
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
'Authorization code' and 'Client Credentials' are two different grants.
'Authorization endpoint' will be available for 'authorization code' grant flow. In 'Client Credentials' grant, the client app directly talks to token endpoint with its credentials, so authorization endpoint is not involved in that flow.
Appropriate fields are displayed based on 'grant type' selection and authentication profile for the grant flow is created.
Can you put some detail on the error you are seeing ?