Skip to content
Statseeker Technical Support
  • There are no suggestions because the search field is empty.

How do I Troubleshoot LDAP to Statseeker access?

  1. Ping the LDAP Server and see if there is a response
  2. Telnet to LDAP (389) or secure (636)
    telnet LDAP_IP 389
  3. Run a ldapsearch from statseeker to see if the objects are getting returned.
    For secure LDAP with AD
    ldapsearch -x -H ldaps://LDAP_IP:636 -b "BASE_DN" -D "BIND_DN" -w "BIND_PASSWORD" -s sub "objectclass=*"

     

    For not secure LDAP with AD
    ldapsearch -x -H ldap://LDAP_IP:389 -b "BASE_DN" -D "BIND_DN" -w "BIND_PASSWORD" -s sub "objectclass=*"
  4. If the query comes back successfully (success is not 0), then it means the information provided in the GUI is incorrect. 

    TheMajority of the times it would be to do with the BIND_DN not being kept to a username
  5. If everything fails, then the best way to investigate is by placing not Apache but it's ldap module in debug mode as below:

    - switch to root user
    - edit /var/local/statseeker/ss/etc/httpd.conf
    - add the line, LogLevel authnz_ldap:debug
    - restart apache

    You can then see the errors in ~/base/log/httpds.errors