Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

ds_389

Sets up the DS389 service on RHEL servers allowing for multiple directories to be controlled
Project URLRSS FeedReport issues

14,148,734 downloads

14,146,995 latest version

3.0 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.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 1.0.1 (latest)
  • 1.0.0
  • 0.1.4
  • 0.1.3
  • 0.1.1
  • 0.1.0
released Mar 19th 2015
This version is compatible with:
  • Puppet Enterprise 3.2.x
  • Puppet 3.x
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'jlcox-ds_389', '1.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jlcox-ds_389
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jlcox-ds_389 --version 1.0.1

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
Tags: service, directory, ldap, 389ds

Documentation

jlcox/ds_389 — version 1.0.1 Mar 19th 2015

This is the 389_DS module.

To set up a server with the DS389 service you will need to add the following classes to you manifest

class {'ds_389::install' : }
class {'ds_389::service' : }

These Classes will install the packages and also set the service to start on boot.

To create a new directory site you can use the following format

ds_389::site { 'api' : suite_spot_group => 'nobody', suite_spot_user_id => 'nobody', modify_ldif_file => [ 'base_api.ldif', 'ssl.ldif', 'plugin.ldif', ], add_ldif_file => [ 'top_dn.ldif', 'user_group_ou.ldif', ], schema_extension => [ '99user.ldif', ], root_dn => 'cn=Directory Manager', root_dn_pwd => '1234qwer', server_port => '4389', server_ssl_port => '4636', suffix => 'dc=some_org', base_data => 'true', }

modify_ldif_file This array is a list of template names (less the .erb extension) that are located in the templates folder in this module. If there are no files to be imported into the database then this can be set to 'none'.

add_ldif_file This array list contains ldif files that do not have any local customisations that need to be applied and are located in the template directory.

schema_extension These are extension files that need to be copied into the ldap site directory. These files are located in the files/schema_extesion directory of this module.

base_data base ldif files files that need to appied o a site. This can either be a single file or 'true' which will deploy all files listed in 'manifests/base_load_list.pp' These files are located in the modules files/base_data directory