hi,
I tried to configure an Authentification Profile based on OAuth 2.0,
but get blocked when configuring the Acces token endpoint.
It looks like it doesn’t like the URL which is fine for me (it’s a custom URL available in our network).
Did anyone face this issue ? (tested on 8.7.6 & Infinity 23)
Hi Can you try doing this steps:
1.Use Postman to manually test the connectivity to the Access Token Endpoint URL from your network environment. This can help identify any connectivity issues or errors returned by the endpoint.
2.Check Endpoint Configuration: Ensure that the Access Token Endpoint URL is correctly configured in your OAuth 2.0 Authentication Profile within Pega. Double-check the spelling, syntax, and any additional parameters required by the endpoint.
Everything works fine with Postman.
It just looks like Pega doesn’t want to save the Authentification Profile because it thinks that the url it’s not valid.
Pega might check the syntax of this url and unfortunately check it wrong in my opinion…
ie.
https://dvl-gateway-apim.xxx.group.abc/token → invalid url
https://dvl-gateway-apim.xxx.group.xyz/token → valid url
@ArnaudW - Issue is with pxIsValidURL validate rule. Verify the DSS regexForAuthProfileURLValidation and need to add below expression. If its present modify if not create a new DSS rule. Its giving issue because of “.” after the server name.
DSS regexForAuthProfileURLValidation
RS : Pega-IntegrationEngine
(?:[([0-9a-fA-F:]+)]|(?:(?:[a-zA-Z0-9%-.~!$&'()*+,;=]+:[a-zA-Z0-9%-.~!$&'()+,;=]@)?([\p{Alnum}-.])))(:\d)?(.*)?
Thank you.
