Forge Home

ldap

manager ldap client

9,758 downloads

8,929 latest version

1.4 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.0.8 (latest)
  • 0.0.7
  • 0.0.6
  • 0.0.4
  • 0.0.3
  • 0.0.1 (deleted)
released May 12th 2015

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'phagedorn-ldap', '0.0.8'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add phagedorn-ldap
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install phagedorn-ldap --version 0.0.8

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

phagedorn/ldap — version 0.0.8 May 12th 2015

ldap

forked from https://github.com/jfryman/puppet-openldap. thanks a lot

This is the ldap module.

This currently stands as the scratch file for the LDAP module. While under development, it has the following goals.

  • Provide a generic LDAP type
    • OpenLDAP (2.3 and 2.4 branches)
    • Allow configuration of many types of LDAP servers
      • Each installed type will have a custom provider
    • Provide the ability to create add-on hooks
      • Kerberos
      • RADIUS
      • SASL
      • DNS

Scope of initial module are the following operating systems

  • Debian Squeeze
  • Debian Lenny
  • Centos 5
  • Fedora 14
  • Ubuntu Maverick
  • Ubuntu Lucid
  • OpenSuSE

TODO: Client, add SSL Support TODO: Client, add SASL Support

Default SSL support: CERT and KEY @ /etc/ssl/{cert,key}/ldap.pem

BUG: When testing by applying server-only configuration, manifest will install client libraries as well. Does implying server configuration mean that I want to automatically setup a client?

Things that are needed:

  • Authenticated Bind for PAM (Want to create a user to bind as)
  • Break up PAM.D modules into individual templates and re-use across linux variants as appropriate.