Installs/configurates kerberos version 5. This cookbook uses the original MIT kerberos implementation.

• Ubuntu

Might work on Debian, too. Only tested on Ubuntu 12.04 LTS.

This recipe installs the kerberos library files and creates and manages the krb5.conf configuration. It is needed for all other recipes.

See the Attributes section for more information about the krb5.conf

This cookbook installs the kerberos programs like kinit, klist.

Basic kdc implementation: package installation, service and kdc.conf management.

It is not designed to create a working kerberos REALM. Currently it is only tested in combination with kdc-ldap.

DB plugin for kdc and kadmind to store all kerberos information in LDAP.

The sensitive information service key file and key stash file are not managed or created by chef.

Setups a kadmind serverice. No configuration.

The krb5.conf is generated from the node attributes. Currently only two features are not supported: including other files or directories and loading of profile modules.

Every section is covered by an own hash under node['krb5']:

• node['krb5']['libdefaults']: Contains various default values used by the Kerberos V5 library.
• node['krb5']['login: Contains default values used by the Kerberos V5 login program, login.krb5(8).
• node['krb5']['appdefaults']: Contains default values that can be used by Kerberos V5 applications.
• node['krb5']['realms']: Contains subsections keyed by Kerberos realm names which describe where to find the Kerberos servers for a particular realm, and other realm-specific information.
• node['krb5']['domain_realm']: Contains relations which map subdomains and domain names to Kerberos realm names. This is used by programs to determine what realm a host should be in, given its fully qualified domain name.
• node['krb5']['logging']: Contains relations which determine how Kerberos entities are to perform their logging.
• node['krb5']['capaths']: Contains the authentication paths used with non-hierarchical cross-realm. Entries in the section are used by the client to determine the intermediate realms which may be used in cross-realm authentication. It is also used by the end-service when checking the transited field for trusted intermediate realms.
• node['krb5']['dbdefaults]']: Contains default values for database specific parameters.
• node['krb5']['dbmodules']: Contains database specific parameters used by the database library.
• node['krb5']['plugins']: Contains plugin module registration and filtering parameters.

Use the tag as key inside the hash.

true, false, Integers and Strings as value are supported. To set multiple values for a tag use an array (multiple lines will be generated). Use a subhash to generate a subsection. All tags which have nil as value will be ignored. So previous setted options can be removed (e.g. in overwrite_attributes).

Please read the krb5.conf(5) man page for more information about the syntax and a list about a supported options.

The kdc recipe managed the kdc.conf file. It has the same syntax like krb5.conf and the following sections:

• node['krb5']['kdcdefaults']: Contains parameters which control the overall behaviour of the KDC.
• node['krb5']['kdcrealms']: Contains subsections keyed by Kerberos realm names which describe per-realm KDC parameters. The section name inside the file is only realm. To avoid collisions with the realms section of krb5.conf another attribute name is used.

Please read the kdc.conf(5) man page for more information about the syntax and a list about a supported options.