Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

Problems with LDAP Authentication

Check the following:

  • The user's login name in the Management Server must be identical to a uid entry in the LDAP database.

  • Passwords should be stored in the LDAP database in either the userPassword or authPassword field.

  • Plaintext passwords stored in the LDAP are not supported for security reasons.

  • If your LDAP is configured to only allow reading of userPassword or authPassword field under a certain bind name, remember to fill in the LDAP username and LDAP password fields in the administration interface.

  • If you require TLS authentication to the LDAP server, remember to upload a certificate in the LDAP configuration page.

  • If you set TLS mode to Require, make sure you have uploaded a valid certificate for TLS authentication purposes.

  • If the LDAP server is offline, none of the users who have been configured to be authenticated via LDAP will be able to log in.


Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more