Currently, I’m working on setting an integration between SAP Concur API web services and PEGA.
Concur requires Oauth 2.0 as the method of authentication, I’ve set my Authentication profile using the Client secret and ID provided by Concur’s portal.
However, Concur needs a request token, that is used to call the refresh token that APIs will use.
Everything on Postman works, but I haven’t been able to execute any successful call of the APIs from PEGA, every time I try, it says there was a problem creating the OAuth profile.
Any suggestions on how to configure the Authentication Profile will be great!
@Junicavi if you get no further help here I would suggest you contact our Pega consulting services.
Based on the context provided, it seems you are facing issues with the OAuth 2.0 authentication while integrating SAP Concur API with Pega. Here are some suggestions:
Ensure that you have correctly configured the OAuth 2.0 authentication profile in Pega with the correct Client ID and Client Secret provided by Concur’s portal.
Make sure you have selected the correct Grant Type in the OAuth 2.0 authentication profile. If Concur requires a request token, you might need to use the ‘Authorization Code’ grant type.
Ensure that the Access Token Endpoint and other endpoints are correctly configured in the OAuth 2.0 authentication profile.
If Concur requires a refresh token, ensure that the ‘Use Refresh Token if Available’ checkbox is selected in the OAuth 2.0 authentication profile.
Remember to save the OAuth 2.0 authentication profile after making these changes. If the issue persists, it might be necessary to debug the issue further by checking the logs for more detailed error messages.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
This is a GenAI-powered tool. All generated answers require validation against the provided references.