Question
Capgemini
GB
Last activity: 27 Feb 2024 5:11 EST
Custom component authentication not working in Pega Infinity 23
I have a Pega infinity 23 server running in our private cloud.
We developed a custom component and during phase of authentication it is working differently to what is mentioned in this article
Instead of asking for the inputs mentioned there, it asks for Pega server url and authentication service alias
Up on entering those details, it opens Pega login screen in a browser and when submitted with login crendetials its throwing an error.
Need your support to overcome this issue.
***Edited by Moderator Marije to add Product version '23 tags***
Accepted Solution
Updated: 27 Feb 2024 5:11 EST
Pegasystems Inc.
US
Hi Sateesh,
It appears you have moved up to a newer version of DX Component Builder and so the documentation to follow is likely this:
You should be able to move you prior components to a newly created project.
With earlier 8.8 release we defaulted to the "confidential" OAuth 2.0 password credentials flow (DX-CustomComponents OAuth 2.0 client registraton record). We have since moved to prefer the "public" OAuth 2.0 authorization code grant flow (DX-ComponentDev OAuth 2.0 client registration record).
Also see this link for the latest settings within tasks.config file:
- Vinod
ComponentMaker Limited
GB
@SateeshB6784Please post a screen shot of the error.
Capgemini
GB
@Niall Riddell , up on entering credentials in the login page it redirects to this page.
ComponentMaker Limited
GB
Pegasystems Inc.
GB
@SateeshB6784 please can you confirm if your issue is resolved?
Please mark Neil's answer with Accept Solution if so.
Accepted Solution
Updated: 27 Feb 2024 5:11 EST
Pegasystems Inc.
US
Hi Sateesh,
It appears you have moved up to a newer version of DX Component Builder and so the documentation to follow is likely this:
You should be able to move you prior components to a newly created project.
With earlier 8.8 release we defaulted to the "confidential" OAuth 2.0 password credentials flow (DX-CustomComponents OAuth 2.0 client registraton record). We have since moved to prefer the "public" OAuth 2.0 authorization code grant flow (DX-ComponentDev OAuth 2.0 client registration record).
Also see this link for the latest settings within tasks.config file:
- Vinod