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


pam (5) Versions 0.1.0

Installs/Configures pam

cookbook 'pam', '= 0.1.0', :supermarket
cookbook 'pam', '= 0.1.0'
knife supermarket install pam
knife supermarket download pam
Quality -%


Manages PAM services in /etc/pam.d


This cookbook will not set up PAM if you do not already have it installed. It will only modify an existing configuration.

Also, currently it only includes defaults for /etc/pam.d/su. If you want to override any other PAM services, you will first need to transcribe the entire service configuration into the appropriate node attibute, otherwise the PAM file will be overwritten with only the attributes you configure (and your system will become unusable).

Supported Platforms

This cookbook should work fine on Red Hat systems, however it has only been tested on Ubuntu 12.04.


  • node['pam_d']['services'] - Example:
    'su' => {
      'main' => {
        'pam_env' => {
          'interface' => 'session',
          'control_flag' => 'required',
          'name' => '',
          'args' => 'readenv=1',
          'disabled' => false
      'includes' => %w(

NOTE: pam_env in this case is just a placeholder so that we can use a keyed hash instead of an array. disabled is optional but if it is present and set to true, it will prevent the entry from showing up in the PAM service file.



Include pam in a recipe:

include_recipe 'pam'


  1. Fork the repository on Github
  2. Create a named feature branch (i.e. add-new-recipe)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request

License and Authors

Author:: EverTrue, Inc. (

No quality metric results found