Question
Bluerose Technology
IN
Last activity: 7 Jul 2023 13:11 EDT
OAuth2.0 authention for Service REST fails
Hi Team,
I have created a service REST, with Oauth2.0 as an authentication mechanism. In my case Oauth2.0 provider is Pega. So I have created Oaut2.0 client registration as in the document below.
I have used client credentials flow in OAuth2.0. I see an issue in logs, like this
Unable to obtain access token for client details in authentication profile configured for connector
(Full logs attached in the Doc). Am I missing anything here?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Updated: 7 Jul 2023 13:11 EDT
Pegasystems Inc.
GB
@SureshP16655111 *** update ***
Our SME has riewed the document again and it looks like there is problem in how the access token is retrieved. Invoking the API involves
Extract:
- Getting the access token
- To obtain an access token in Postman, send the client_id, client_secret, and grant_type in a POST request to the access token endpoint.
- Use the obtained access token while caaling the API
- Use the obtained access token to invoke Pega API REST service that is protected by OAuth 2.0.
We believe you may have omitted to perform step-1 as there is nothing mentioned about this in the document which you attached.
We would suggest that you to refer to this document Pega help documentation (Accessing the Pega API by using OAuth 2.0) that clearly explains how to get the access token (Refer to 1st step under “Configuring the client” section) using postman client.
I hope this helps.
If after the above steps are done and you still have issues then we recommend that you log this as a support incident on the MSP.
Please can you provide the INC reference here so that we can help track it?
Bluerose Technology
IN
@SureshP16655111, Any suggestions?
Pegasystems Inc.
GB
@SureshP16655111 I will check internally to see if I can find any SME to help.
Bluerose Technology
IN
@MarijeSchillern , Is there any update?
Accepted Solution
Updated: 7 Jul 2023 13:11 EDT
Pegasystems Inc.
GB
@SureshP16655111 *** update ***
Our SME has riewed the document again and it looks like there is problem in how the access token is retrieved. Invoking the API involves
Extract:
- Getting the access token
- To obtain an access token in Postman, send the client_id, client_secret, and grant_type in a POST request to the access token endpoint.
- Use the obtained access token while caaling the API
- Use the obtained access token to invoke Pega API REST service that is protected by OAuth 2.0.
We believe you may have omitted to perform step-1 as there is nothing mentioned about this in the document which you attached.
We would suggest that you to refer to this document Pega help documentation (Accessing the Pega API by using OAuth 2.0) that clearly explains how to get the access token (Refer to 1st step under “Configuring the client” section) using postman client.
I hope this helps.
If after the above steps are done and you still have issues then we recommend that you log this as a support incident on the MSP.
Please can you provide the INC reference here so that we can help track it?
-
Suresh Podisetty
Bluerose Technology
IN
@MarijeSchillern , I don't see any option to raise an Incident. Can you please help me with that?
Pegasystems Inc.
GB
Creating a Pega Community account is only the first step – it only gives you access only to the basic online services (reading forum posts, access to some documentation).
All questions about what qualifies as a fully-affiliated account are covered in the Community Account FAQ pages.
To raise support tickets please make sure you are affiliated and able to raise support incidents for your organization.
Our process is documented here:
You may need to get in touch with your company's Account Administrator.
How to check your Account Administrator details on My Support Portal
Below are the steps which need to be followed .
Creating a Pega Community account is only the first step – it only gives you access only to the basic online services (reading forum posts, access to some documentation).
All questions about what qualifies as a fully-affiliated account are covered in the Community Account FAQ pages.
To raise support tickets please make sure you are affiliated and able to raise support incidents for your organization.
Our process is documented here:
You may need to get in touch with your company's Account Administrator.
How to check your Account Administrator details on My Support Portal
Below are the steps which need to be followed .
- Contact the Account Administrator of your organization who can help in affiliating you with the account.
- If you are not aware of an Account Administrator consult your manager.
- If your manager is also not aware contact your colleague or someone else in your organization who is able to download Pega software who helps in providing the Account Administrator of your organization.
For more information about My Pega account display issues visit the My Pega FAQ
For information about the MSP visit the My Support Portal FAQ
-
Suresh Podisetty