- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2020 06:11 AM
Hi All,
The SSO was working fine on the current MSP prod, however when we brought it to dedicated one and mapped all the setting, the SSO login is giving the error-
Logout successful |
The connection is successful with the Azure AD , however the end user is not able to login to the instance and getting the above error.
Any help would be really great.
Thanks
RMohan
Solved! Go to Solution.
- Labels:
-
Instance Configuration
-
Integrations

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2020 07:32 AM
you may want to review the setting again, look like configuration is not correct. In previous experience using SSO and SAML, a typo or incorrect redirect will cause issue among others.
Regards,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2020 06:19 AM
Can you try a couple of things
In the User account -- make sure you have the same data in your UserId and Email Fields. make sure the email you have in ServiceNow matches up with the email in your source.
you can also try to open the user record from the sys_user table and uncheck the Locked out flag and make sure the active flag is also marked to true.
also to get back in you can bypass the SSO by adding xxxx.service-now.com/login.do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2020 06:23 AM
Hi Miguel,
Thanks for your reply.
Checked that the user ID and the email fields contain the same date and also made sure that the testing users are not locked out and are active in the system.
But still we are getting the logged out error message.
Thanks
RMohan

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2020 07:32 AM
you may want to review the setting again, look like configuration is not correct. In previous experience using SSO and SAML, a typo or incorrect redirect will cause issue among others.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2020 08:00 AM
Hi Miguel,
I did checked thoroughly and found it to be a certificate issue.
Thank you for you help 🙂