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.
Error - ldap://<ldap_server_ip>:<Port>/ Invalid credentials - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Error - ldap://<ldap_server_ip>:<Port>/ Invalid credentials
KB0756703

Error - ldap://<ldap_server_ip>:<Port>/ Invalid credentials


4782 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

When running a Test Connection Probe from LDAP Server administrators get an error as - ldap://<ldap_server_ip>:<Port>/ Invalid credentials

Make sure this user account has login and read access to the server

Cause

In most of the cases the cause of the issue is the Login Distinguished Name and the Password doesn't match.

In some cases the error is misleading, in such cases cause of the issue could be user doesn't have a valid access to the starting search directory.

Resolution

  1. Check the login distinguished name and password is correct.
  2. In cases where error is misleading check user has valid access to the starting search directory.
  3. Run LDAP Search command on the LDAP Server - 
    ldapsearch -x -D "<login_distinguished_name>" -w <Password> -H <LDAP Server:port> -b "<Starting Search Directory>""(&(objectClass=person))"
  4. Alternatively customer can install 3rd party LDAP Search tools like Jxplorer to check the issue further.
  5. To further debug administrators can enable LDAP debug system properties and check the issue in system logs.
    Property Name - glide.ldap.debug
    Type  - True/False.

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.