Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
New AD users cannot login to Servicenow instance with SSO: ERROR *** *** Script: User: [Username] not found - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • New AD users cannot login to Servicenow instance with SSO: ERROR *** *** Script: User: [Username] not found
KB0788105

New AD users cannot login to Servicenow instance with SSO: ERROR *** *** Script: User: [Username] not found


11286 Views Last updated : Apr 8, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

  • Newly provisioned SSO Users fail to logon to Servicenow and they are immediately redirected to the    external_logout_complete.do page
  • The following error is observed in the System log "ERROR *** *** Script: User: [Username] not found"
  • In the node logs the error "SAMLRequestIDGenerator: can’t get request id from session." was observed

Cause

Once a user is successfully authenticated, the last step in the authentication process is to validate the user is to identify the user in the sys_user table based on the value in the 'User field' configured in the advanced section of the Identity Provider record. In this occasion it was trying to validate a valid name against an email address. As the email address did not match the name, the user was not found. It is important to validate the name against the 'user_name' or validate the email against the email address so the values can match

Resolution

From the logs it was identified that subjectUserName was a user name but the user_field was 'email' which is not a valid match

To resolve the issue it was necessary to navigate to the advanced section of the Identity provider record and update the 'User Field' column with 'user_name' instead of 'email'


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.