LDAP Authentication

Set LDAPIdentityProvider in the identityProviders section to validate username and password against an LDAPv3 server using simple bind authentication.

During authentication, the LDAP directory is searched for an entry that matches the provided username. If a single unique match is found, a simple bind is attempted using the DN of the entry plus the provided password.

Example Configuration Using LDAPIdentityProvider:

apiVersion: installer.kubesphere.io/v1alpha1
kind: ClusterConfiguration
  name: ks-installer
    jwtSecret: ********************************
    authenticateRateLimiterMaxTries: 10
    authenticateRateLimiterDuration: 10m
      accessTokenInactivityTimeout: 30m
      accessTokenMaxAge: 1h
      - name: ldap
        type: LDAPIdentityProvider
        mappingMethod: auto
          managerDN: uid=root,cn=users,dc=nas
          managerPassword: ******
          userSearchBase: cn=users,dc=nas
          loginAttribute: uid
          mailAttribute: mail

For the above example:

insecureSkipVerifyUsed to turn off TLS certificate checks.
startTLSIf specified, connections will use the ldaps:// protocol.
rootCAPath to a trusted root certificate file. Default: use the host’s root CA.
rootCADataA raw certificate file can also be provided inline. Base64 encoded PEM file.
hostThe name and port of the LDAP server.
managerDNDN to use to bind during the search phase.
managerPasswordPassword to use to bind during the search phase.
userSearchBaseThe search base is the distinguished name (DN) of a level of the directory tree below which all users can be found.
userSearchFilterLDAP filter used to identify objects of type user. e.g. (objectClass=person)
loginAttributeUser naming attributes identify user objects, will be mapped to KubeSphere account name.
mailAttributeThe mail attribute will be mapped to the KubeSphere account.

感谢您的反馈。如果您有关于如何使用 KubeSphere 的具体问题,请在 Slack 上提问。如果您想报告问题或提出改进建议,请在 GitHub 存储库中打开问题。