Skip to content
3SL header
3SL_Logo_Medium

3SL Blog

From concept to creation

  • Home
  • Blog
  • News
  • Newsletters
  • Hints & Tips
  • Articles
  • FAQ

LDAP Troubleshooting Checklist

LDAP Connection Problems/Unknown User Issues?

Work through the following checklist as setting up the ldap_config file to match your LDAP settings can be difficult:

  1. Enable the trace log by setting the LDAP_TRACE attribute to TRUE in the ldap_config file. The ldap_trace.log file is written to a file in the logs/user directory this can be used to diagnose your problem.

    Screenshot showing tracing enabled in the ldap_config file
    Enabling tracing in the ldap_config file
  2. If you are using Windows® Active Directory, run the Active Directory Users and Computers browser from the Windows Domain Controller and check what the DN (Distinguished Name) is for the domain. From this browser you can also find out where the users are stored.
  3. On other LDAP servers, use the setup tool for the LDAP server to find out the correct DN and user areas.
  4. Check the correct Protocol is being used.
  5. Check that the correct level in the LDAP directory structure is being used as the BIND_DN and also that the correct BIND_PASSWD is being used.
  6. If the LDAP server is running securely, is the ldap_config file setup correctly?
  7. To test that you are connecting to the LDAP server correctly without checking the user authentication, set AUTO_LDAP_LOGIN from TRUE to FALSE. This would help to show where the problem is, i.e. either an issue with the connection to the LDAP server or whether there is a problem searching the correct user location on the LDAP server.
  8. LDAP verification will not succeed if the user’s LDAP structure contains multiple UIDs, e.g. if you have UID=manager and UID=yourname.
  9. If you are failing to login and you receive an LDAP message confirming the password or username could be incorrect but the LDAP response message is blank then it is likely you have a case match issue with the entered username and the username returned from LDAP, and Cradle is rejecting the entered username. To resolve this issue you can set the UID_IGNORE_CASE to true.

For further information on LDAP see our previous blog entry or for more on Cradle integration with LDAP please refer to our online help.

TweetShareNewsletter
CategoriesHints & Tips Tagslogin, settings/configuration/prefs/customise

Post navigation

Previous PostPrevious Why do I get a ‘Item Not Completed’ message?
Next PostNext Quick Data Analysis
November 2026
MTWTFSS
 1
2345678
9101112131415
16171819202122
23242526272829
30 
« Oct    

Archive

Search

Categories

Tags

Cradle-7.7 workflow INCOSE c_io graphs Project Manager items commands formal documents process flow diagram (PFD) skills language user interface (UI) dashboards publish administration Risk testing Cradle-7.4 Cradle support newsletter requirements management new features / release Windows sidebar installation Cradle product versions Systems Engineering (SE) dates/times categories change control training Cradle-7.3 3SL forms errors images Citrix SysML Toolsuite Cyber Essentials social media Document Loader general interest settings/configuration/prefs/customise reports linux Cradle-7.2 cross references / links hierarchies diagrams Risks SaaS Cradle database users PDUID distributor white papers Model Based Systems Engineering (MBSE) modelling database project management history anti-virus queries definitions document management Cradle-7.1 source documents output/printing project schema Cradle-7.6 information capture Cradle modules baselines Web Access office tools import/export login metrics projects frames Cradle discussions user requirements views iso9001 Risk Management compliance and traceability Web Publisher alerts Document Publisher G-Cloud Cradle licences configuration management lifecycle WorkBench hierarchy diagrams (HID) start page deals

Copyright

Copyright© 1987 - Structured Software Systems Ltd. All rights reserved. Cradle® is a registered trademark of 3SL in the UK and other countries.
Blog – Privacy Proudly powered by WordPress