Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


openldap (50) Versions 1.12.2

Installs and configures OpenLDAP (slapd) an open source implementation of LDAP.

cookbook 'openldap', '= 1.12.2', :supermarket
cookbook 'openldap', '= 1.12.2'
knife supermarket install openldap
knife supermarket download openldap
Quality -%

openldap Cookbook

Configures a server to be an OpenLDAP master, OpenLDAP replication slave, or OpenLDAP client.



Ubuntu 10.04 was primarily used in testing this cookbook. Other Ubuntu versions and Debian may work. Red Hat and derivatives are not fully supported, but we take patches.


  • openssh
  • nscd
  • openssl (for slave recipe)


Be aware of the attributes used by this cookbook and adjust the defaults for your environment where required, in attributes/openldap.rb.

Client node attributes

  • openldap[:basedn] - basedn
  • openldap[:server] - the LDAP server fully qualified domain name, default 'ldap'.node[:domain].

Server node attributes

  • openldap[:slapd_type] - master | slave
  • openldap[:slapd_rid] - unique integer ID, required if type is slave.
  • openldap[:slapd_master] - hostname of slapd master, attempts to search for slapd_type master.
  • openldap[:manage_ssl] - Whether or not this cookbook manages your SSL certificates. If set to true, this cookbook will expect your SSL certificates to be in files/default/ssl and will configure slapd appropriately. If set to false, you will need to provide your SSL certificates prior to this recipe being run. Be sure to set openldap[:ssl_cert] and openldap[:ssl_key] appropriately.
  • openldap[:ssl_cert] - The full path to your SSL certificate.
  • openldap[:ssl_key] - The full path to your SSL key.
  • openldap[:cacert] - Your certificate authority's certificate (or intermediate authorities), if needed.

Apache configuration attributes

Attributes useful for Apache authentication with LDAP.

COOK-128 - set automatically based on openldap[:server] and openldap[:basedn] if those attributes are set. openldap[:auth_bindpw] remains nil by default as a default value is not easily predicted.

  • openldap[:auth_type] - determine whether binddn and bindpw are required (openldap no, ad yes)
  • openldap[:auth_url] - AuthLDAPURL
  • openldap[:auth_binddn] - AuthLDAPBindDN
  • openldap[:auth_bindpw] - AuthLDAPBindPassword



Sets up the system for using openldap for user authentication.


Empty recipe, you may want client.


Install the openldap client packages.


Set up openldap to be a slapd server. Use this if your environment would only have a single slapd server.


Sets the node['openldap']['slapd_type'] to master and then includes the openldap::server recipe.


Sets the node['openldap']['slapd_type'] to slave, then includes the openldap::server recipe. If the node is running chef-solo, then the node['openldap']['slapd_replpw'] and node['openldap']['slapd_master'] attributes must be set in the JSON attributes file passed to chef-solo.


Edit Rakefile variables for SSL certificate.

On client systems,

include_recipe "openldap::auth"

This will get the required packages and configuration for client systems. This will be required on server systems as well, so this is a good candidate for inclusion in a base role.

On server systems, if there's only one LDAP server, then use the openldap::server recipe. If replication is required, use the openldap::master and openldap::slave recipes instead.

When initially installing a brand new LDAP master server on Ubuntu 8.10, the configuration directory may need to be removed and recreated before slapd will start successfully. Doing this programmatically may cause other issues, so fix the directory manually :-).

$ sudo slaptest -F /etc/ldap/slapd.d
str2entry: invalid value for attributeType objectClass #1 (syntax
=> ldif_enum_tree: failed to read entry for /etc/ldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif
slaptest: bad configuration directory!

Simply remove the configuration, rerun chef-client. For some reason slapd isn't getting started even though the service resource is notified to start, so start it manually.

$ sudo rm -rf /etc/ldap/slapd.d/ /etc/ldap/slapd.conf
$ sudo chef-client
$ sudo /etc/init.d/slapd start

A note about certificates

Certificates created by the Rakefile are self signed. If you have a purchased CA, that can be used.

We provide two methods of managing SSL certificates, based off of openldap[:manage_ssl].

If openldap[:manage_ssl] is true, then this cookbook manage your certificates itself, and will expect all certificates, intermediate certificates, and keys to be in the same file as defined in openldap[:ssl_cert].

Be sure to update the certificate locations in the templates as required. We suggest copying this cookbook to the site-cookbooks for such modifications, so you can still pull from our master for updates, and then merge your changes in.

However, if openldap[:manage_ssl] is false, then you will need to place the SSL certificates on the client file system prior to this cookbook being run. This provides you the flexibility to provide the same set of SSL certificates for multiple uses as well as in one place across your environment, but you will need to manage them.
- Set openldap[:ssl-cert], openldap[:ssl_key], and openldap[:cacert] appropriately.
- Ensure that that user openldap can access these files. Watch out for apparmor and SELinux if you are placing your SSL certificates in a non-default location.

New Directory

If installing for the first time, the initial directory needs to be created. Create an ldif file, and start populating the directory.


Set the password, openldap[:rootpw] for the rootdn in the node's attributes. This should be a password hash generated from slappasswd. The default slappasswd command on Ubuntu 8.10 and Mac OS X 10.5 will generate a SHA1 hash:

$ slappasswd -s "secretsauce"

Set this by default in the attributes file, or on the node's entry in the webui.

License & Authors

Copyright:: 2009, Opscode, Inc

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

No quality metric results found