Skip to content
3SL header
3SL_Logo_Medium

3SL Blog

From concept to creation

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

Day: 30 May 2017

Posted on 30th May 201731st May 2017

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
May 2017
MTWTFSS
1234567
891011121314
15161718192021
22232425262728
293031 
« Apr   Jun »

Archive

Search

Categories

Tags

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

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