- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi, all
I am configuring SSO.
I have configured the ID provider, performed a test connection, and activated it.
After that, when I tried to log in to ServiceNow with SSO, I encountered the situation shown in the attached image.
I am using Auth0, and when I checked its logs, there is a record of a successful login.
What settings in ServiceNow might be incorrect?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Can you confirm whether you have configured SSO Source?
Ref: Configure users for Multi-Provider SSO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @RyoyaFukuda
It seems there is mismatch between SSO properties and SSO NameID policy .
Use same field for both like Email or user name.
Validate this two configurations:
1)Name ID policy field value has been set to
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
2)System Property glide.authenticate.multisso.login_locate.user_field value has been set to email
Azure SSO error with ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you @Tanushree Maiti
As per your instructions, I have changed the settings. I changed the system property from "user_name" to "email".
When I try to log in again with SSO, the following error message is displayed:
"*** Script: Ensure that the user you are trying to login is from the correct source, as mentioned in user's sso source field in servicenow instance.: no thrown error"
I have put the sysID of what is defined in the identity provider in the user's SSO source.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you @Tanushree Maiti
There was a blank space between "sso:" and the sysID in the SSO source.
After removing it, I was able to log in correctly with SSO!
Thank you very much!
