Active Directory and LDAP

[edit on GitHub]

The Chef Infra Server supports Active Directory and LDAP authentication, which enables users to log in to the Chef Infra Server using their corporate credential and the Manage interface. Without the Manage interface add-on installed, there is no need to enable the Chef Infra Server LDAP functionality. LDAP is not used with Supermarket logins, nor with any Chef Infra Client related authentication.

Configure LDAP

The Chef Infra Server supports using Active Directory or LDAP for any user that has an email address in the LDAP directory. This allows those users to log in to the Chef Infra Server by using their corporate credentials instead of having a separate username and password.

To configure the Chef Infra Server to use Active Directory or LDAP do the following:

1. Install the Chef management console (if it is not already).

2. Add the following settings to the /etc/opscode/chef-server.rb file. These settings must be added to the chef-server.rb file on each machine in the Chef Infra Server frontend deployment of a High Availability installation as well as on Chef servers in a standalone installation.

   Warning

   The following settings MUST be in the config file for LDAP authentication to Active Directory to work:

   • base_dn
   • bind_dn
   • group_dn
   • host

   If those settings are missing, you will get authentication errors and be unable to proceed.

   This configuration file has the following settings for ldap:

   ldap['base_dn']

   The root LDAP node under which all other nodes exist in the directory structure. For Active Directory, this is typically cn=users and then the domain. For example:

   'OU=Employees,OU=Domain users,DC=example,DC=com'
       

   Default value: nil.

   ldap['bind_dn']

   The distinguished name used to bind to the LDAP server. The user the Chef Infra Server will use to perform LDAP searches. This is often the administrator or manager user. This user needs to have read access to all LDAP users that require authentication. The Chef Infra Server must do an LDAP search before any user can log in. Many Active Directory and LDAP systems do not allow an anonymous bind. If anonymous bind is allowed, leave the bind_dn and bind_password settings blank. If anonymous bind is not allowed, a user with READ access to the directory is required. This user must be specified as an LDAP distinguished name similar to:

   'CN=user,OU=Employees,OU=Domainuser,DC=example,DC=com'
       

   Note

   If you need to escape characters in a distinguished name, such as when using Active Directory, they must be escaped with a backslash escape character.

   'CN=example\\user,OU=Employees,OU=Domainuser,DC=example,DC=com'
       

   Default value: nil.

   ldap['bind_password']

   Legacy configuration for the password of the binding user. The password for the user specified by ldap['bind_dn']. Leave this value and ldap['bind_dn'] unset if anonymous bind is sufficient. Default value: nil. As of Chef Server 12.14, this is no longer the preferred command.

   Please use chef-server-ctl set-secret ldap bind_password from the Secrets Management commands.

   chef-server-ctl set-secret ldap bind_password
       Enter ldap bind_password:    (no terminal output)
       Re-enter ldap bind_password: (no terminal output)
       

   Remove a set password using

   chef-server-ctl remove-secret ldap bind_password
       

   ldap['group_dn']

   The distinguished name for a group. When set to the distinguished name of a group, only members of that group can log in. This feature filters based on the memberOf attribute and only works with LDAP servers that provide such an attribute. In OpenLDAP, the memberOf overlay provides this attribute. For example, if the value of the memberOf attribute is CN=abcxyz,OU=users,DC=company,DC=com, then use:

   ldap['group_dn'] = 'CN=abcxyz,OU=users,DC=company,DC=com'
       

   ldap['host']

   The name (or IP address) of the LDAP server. The hostname of the LDAP or Active Directory server. Be sure the Chef Infra Server is able to resolve any host names. Default value: ldap-server-host.

   ldap['login_attribute']

   The LDAP attribute that holds the user’s login name. Use to specify the Chef Infra Server user name for an LDAP user. Default value: sAMAccountName.

   ldap['port']

   An integer that specifies the port on which the LDAP server listens. The default value is an appropriate value for most configurations. Default value: 389 or 636 when ldap['encryption'] is set to :simple_tls.

   ldap['ssl_enabled']

   Cause the Chef Infra Server to connect to the LDAP server using SSL. Synonymous with simple_tls Default value: false. Must be false when ldap['tls_enabled'] is true.

   Note

   It’s recommended that you enable SSL for Active Directory.

   Note

   Previous versions of the Chef Infra Server used the ldap['ssl_enabled'] setting to first enable SSL, and then the ldap['encryption'] setting to specify the encryption type. These settings are deprecated.

   ldap['system_adjective']

   A descriptive name for the login system that is displayed to users in the Chef Infra Server management console. If a value like “corporate” is used, then the Chef management console user interface will display strings like “the corporate login server”, “corporate login”, or “corporate password.” Default value: AD/LDAP.

   Warning

   This setting is not used by the Chef Infra Server. It is used only by the Chef management console.

   ldap['timeout']

   The amount of time (in seconds) to wait before timing out. Default value: 60000.

   ldap['tls_enabled']

   Enable TLS. When enabled, communication with the LDAP server is done using a secure SSL connection on a dedicated port. Synonymous with STARTTLS. This mode is rarely used. When true, ldap['port'] is also set to 636. Default value: false. Must be false when ldap['ssl_enabled'] is true.

   Note

   Previous versions of the Chef Infra Server used the ldap['ssl_enabled'] setting to first enable SSL, and then the ldap['encryption'] setting to specify the encryption type. These settings are deprecated.

   Note

   If the chef-server.rb file does not exist, create a file called chef-server.rb and put it in the /etc/opscode/ directory.

3. Reconfigure the Chef Infra Server and the Chef management console (standalone and frontend group members of a High Availabilty installation):

   chef-server-ctl reconfigure
   

At this point, all users should be able to use their Active Directory or LDAP usernames and passwords to log in to the Chef Infra Server.

Test LDAP Connectivity

Use ldapsearch to test the ability of the Chef Infra Server to use Active Directory or LDAP. First, translate the Chef Infra Server LDAP settings into ldapsearch parameters:

And then from a front end machine (in a high availability or tiered configuration) or from the Chef Infra Server in a standalone configuration, run the following command. Be sure to replace the uppercase placeholders with the values for your organization:

ldapsearch -LLL -H ldap://HOST:PORT -b 'BASE_DN' -D 'BIND_DN' -W '(LOGIN_ATTRIBUTE=YOUR_LDAP_ACCOUNT_USERNAME)'

For example:

ldapsearch -LLL -H ldap://win-ad1.chef.co:389 -b 'OU=Employees,OU=Domain users,DC=opscodecorp,DC=com' -D 'CN=Robert Forster,OU=Employees,OU=Domain users,DC=opscodecorp,DC=com' -W '(sAMAccountName=rforster)'

Output similar to the following is returned:

ldapsearch -LLL -H ldap://win-ad1.chef.co:389 -b 'OU=Employees,OU=Domain users,DC=opscodecorp,DC=com' -D 'CN=Robert Forster,OU=Employees,OU=Domain users,DC=opscodecorp,DC=com' -W '(sAMAccountName=rforster)'
Enter LDAP Password:

dn: CN=Robert Forster,OU=Employees,OU=Domain users,DC=opscodecorp,DC=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
cn: Robert Forster
sn: Forster
c: 0
givenName: Robert
distinguishedName: CN=Robert Forster,OU=Employees,OU=Domain users,DC=opscodecorp,DC
 =com