Question
Enigma Metaverse
IN
Last activity: 5 Aug 2025 2:10 EDT
Authentication Failed error - User is Kicked out in mobile App
Hi Everyone,
When I tried to log in to the Pega mobile application, I encountered an "authentication failed" message on the login screen. Could someone please help resolve this issue? FYI: The development works fine in the development environment, but when the same code is deployed to the pre-production environment, it causes an issue
Thank you in advance!
Accepted Solution
Updated: 5 Aug 2025 2:10 EDT
Enigma Metaverse
IN
The exact error message encountered during authentication was "Authentication failed". According to Pega documentation, this error typically occurs due to an incorrect client secret on the mobile client.
Troubleshooting mobile app misconfiguration and authentication issues--> you can refer here
To resolve the issue, I deleted the OAuth 2.0 client registration rule associated with the Mobile Channel. After that, I saved and rebuilt the Mobile Channel, which successfully resolved the authentication problem.
my suggestion is please ensure that the OAuth configuration, Mobile Channel, and the respective certificates are properly migrated to the higher environments to avoid similar issues
EvonSys
IN
Can you check for Hosting In mobile app under configuration whether it is set to pre-prod env URL, as you have deployed it directly, it would still be pointing to dev env.
Enigma Metaverse
IN
@Kishore Kumar Madduri Hi Kishore
Thank you for the suggestion. I checked the hosting configuration in the mobile app, and it is set to the pre-prod environment URL. However, the URL changes to the staging environment when providing credentials (dt1 to stg)
HCA Healthcare
US
If you're seeing "authentication failed" on the Pega mobile app only in the pre-production environment, it may be due to incorrect authentication service setup, missing trusted certificate, or environment-specific URL mismatch. Ensure the correct authentication service (like SSO or basic auth) is selected in the mobile channel configuration and that it points to the right pre-prod URL. Also, check if the pre-prod environment’s SSL certificate is valid and trusted on the mobile device. Clear the mobile app cache or reinstall the app to avoid caching issues. Lastly, make sure the mobile build is generated specifically for the pre-prod environment if environment-specific settings are used
Updated: 17 Jul 2025 3:51 EDT
Enigma Metaverse
IN
Thanks for your detailed response regarding the "authentication failed" issue on the Pega mobile app in the pre-production environment. I wanted to update you that I have resolved the issue. The root cause was that the mobile app was deployed to pre-prod without being rebuilt in the dev environment after merging branch development in the ruleset. The issue was resolved by deleting the OAuth 2.0 client registration mobile rule and then rebuilding the mobile app in the pre-prod environment so that OAuth 2.0 client registration created.
Pegasystems Inc.
CA
Could you please confirm the exact error message that occurred during authentication? We never encountered this issue in the higher environments. Could you please ensure the OAuth, Mobile Channel and respective certs are migrated to higher environemnt?
Accepted Solution
Updated: 5 Aug 2025 2:10 EDT
Enigma Metaverse
IN
The exact error message encountered during authentication was "Authentication failed". According to Pega documentation, this error typically occurs due to an incorrect client secret on the mobile client.
Troubleshooting mobile app misconfiguration and authentication issues--> you can refer here
To resolve the issue, I deleted the OAuth 2.0 client registration rule associated with the Mobile Channel. After that, I saved and rebuilt the Mobile Channel, which successfully resolved the authentication problem.
my suggestion is please ensure that the OAuth configuration, Mobile Channel, and the respective certificates are properly migrated to the higher environments to avoid similar issues