hi, Can some one let me know why this error occur in Pega. The same connect rest rule works in Dev and QA, PROD but not in UAT environment .Any thoughts ? We are on Pega infinity 24.1.1
Could you try re-saving the auth profile you are using for the Connect REST rule? This issue can happen during encryption/decryption. Also, please post the error stack trace it would be helpful for troubleshooting.
Hi @RashmithaM
This is one classic error message which most of us face with Authentication profile instances. This usually occurs when you package Authentication profile instances built in one environment and deploy them to higher environments.
As @RanjithK8179 mentioned, to mitigate this error, you have to re-save the Authentication profile instance in the environment where you are facing this error with appropriate information and you should be good.
To avoid this situation, you can maintain environment specific Authentication profile instances backed by Application Settings so that you need not move the instances into various environments during deployment.
Hope this helps
Regards
JC
As its happening in only UAT, environment specific - it is definitely a config issue as JC mentioned. Typically the client ID / secret is not updated in UAT if you are using OAuth. Any more details on the auth profile configurations can help narrow down the root cause. are you using keystores?