Version information
This version is compatible with:
Start using this module
Add this module to your Puppetfile:
mod 'jza34-realmd', '1.1.0'Learn more about managing modules with a PuppetfileDocumentation
realmd
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with realmd
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Overview
Prepare the client to be enrolled with realmd. Apply it then use realm command to enrolled the client.
Module Description
It installs all extra packages Realmd ask for when discovering a samba4 controller.
It declares the "sssd" service and make sure it runs!
It fixes a "bug" aborting the join when the directory /var/lib/samba/private
is not found. (it creates this directory)
It configures PAM to make home directories of users who successfully log in with a Samba4 account
Setup
Include this class "Realmd".
Log in the client, apply puppet then:
realm join MYDOMAIN.COM
After prompting for the samba4 administrator password, if join is successful you can login with a samba4 user credential:
su mydomainuser
You should be authenticated and your homedirectory created
Parameters
use fully qualified names
A boolean to set the sssd.conf value for use_fully_qualified_names.
When true then domain users must use a login with @my.domain.name at the end
Example: su seb@example.com.fr
When false then domain users need no more the domain name.
Example: su seb
(Default false)
ldap id mapping
A boolean to set the sssd.conf value for ldap_id_mapping.
When true then the host will not use IDs from the domain controller. The host will create a intermediate database with IDs. It is necessary when the controller does not keep UNix-like ids in its database.
When false then no IDs is created from the host but they are queried to the domain controller (like family name, etc...)
It is an important parameter because these IDs are written to the host disk in the home folder for the domain users
If false you keep same id for same user everywhere because it is managed by the controller
If true every host will generate different IDs for same user!
But you must be certain that the domain controller has UNix-ids in its database for all users, and a unique one...
Please note that to change this parameter after enrolment will cause domain users home folders unusable beacause bad IDs.
If ldap id mapping value changes, puppet agent will rename /home/MYREALM to /home/MYREALM.bak
(Default false)
disable pwquality
Disable local password policy and use the one from the samba4 controller.
Please note that it will change pam.d files and will make the PAM utility pam-auth-config unusable.
Be careful if you customize this part because you can lock you out from the host if PAM is badly touched...
(Default true)
homedir
A string representing the path where realm users will create their homedir
(Default /home/$::realm_domain)
Reference
PAM SSSD Samba4
Limitations
At this point it is Debian only but RedHat users may easily adapt it. Work in progress.
Development
1.1.0
- Remove params.pp and put all variables in init.pp
- Remove parameter realm_name replaced by a new external fact realm_domain
- New paramater 'homedir' to set the 'sssd.conf' value 'override_homedir'
1.0.7
- Better README
Dependencies
- puppetlabs/stdlib (>= 1.0.0)
The MIT License (MIT) Copyright (c) 2016 jza34 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.