Last activity: 29 Apr 2019 4:46 EDT
SSO Login Issue for a particular user
We are using SSO URL to login our applications and most of the users are able to login with out any issues. But specfic user(s) are not able to login using SSO url and they are getting below issues while login. We have verified the user profile in pega and it seems every thing is fine and looking correct.
"Authentication response protocal:Name is required"
Pleasse see the attached file for the error message details.
Can any one please help, if you are aware of this issue and solution for the same.
Thanks in advance for your help.
Can you please re-create new id for non-working user by resaving working operator ?
If this is not feasible, I suggest you use chrome extension for SSO/SAML debugger:
Once you install this, tracer both, working and non-working and compare to see why its not working for specific users.
Thanks for the reply.
We have tried to re-create new id for non-working user by resaving working operator and still we have this issue.
Just want to check with you on SSO/SAML debugger, is it posisble to trace the users whose are not able login with SSO.
Just to add more information on this issue.
We see suddenly user was able to login one day and then stopped working automactically,this happend for 2 users for couple of times and rest of the users are able to login without any issues.
What is your Pega version?
We are using Pega 7.4 Version.
This Chrome extension will show the SAML debugging info on its console.
I suggest you install that in system and see how it works, more info can be found on web on this chrome extension.
I know this is not the solution, but u can give a try once as per your statement the configuration for the working and non-working -operator are same.
- Stop the Application server.
- Stop DB services.
- Start the DB Services and start the server.
I am recommending this because few times it will load the proper configuration from DD and war changes too will reflect correct.
Any deployments happened in PROD before the issue was reported ? If yes have you checked the Package contents ?
This is happeing in Dev and UAT and the users(2 members) who has the issues,they dont have access to PROD.
Except those 2 users, remainig users are able to access all the environments with out any issues.
If it is feasible then you can try to decomission the node and replace it with a new node.It helped for a customer so you can also use that.