Version information
This version is compatible with:
- Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
- Puppet >= 4.10.0 < 9.0.0
- , , , , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'tomkrieger-sshkeymgmt', '1.1.0'
Learn more about managing modules with a PuppetfileDocumentation
sshkeymgmt
Table of Contents
- Module description
- Setup - The basics of getting started with sshkeymgmt
- Usage
- Reference
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Acceptance tests
- Changelog
Module description
Sshkeymgmt module is for managing Unix groups and Unix users together with their ssh keys. The module is focused on deploying users in groups. Groups e. g. can be departemens or teams (e. g. system administrators) within your organisation. As a group can consist of one member as well the module is not limited to deploy users and ssh keys in groups.
Users used in ssh key groups which are not defined are simply ignored. A notification is printed to inform about that.
Please make sure to configure your ssh daemon accordingly to the location the ssh authorized_keys files will be located.
Setup
What sshkeymgmt affects
Sshkeymgmt adds, modifies or deletes Unix users and Unix groups on your systems. As it is run with super user privileges it can affect any user on your systems.
Setup Requirements
sshkeymgmt needs puppetlab stdlib and puppetlab concat to work.
Beginning with sshkeymgmt
The most basic setup you could achieve with this module looks something like this:
include '::sshkeymgmt'
or
class { '::sshkeymgmt': }
If there are no Unix users, no Unix groups or no ssh key groups the module will print a notification only.
Usage
Configuration for the class can be done either by Hiera or by writing the configuration directly into the class statement.
Example Hiera data
Configuration of users, groups and ssh key groups can be distributed over different Hiera files. You can for example have all Unix user and group definitions in your most common Hiera file. The ssh groups can be defined in the most recent Hiera file describing the node. Using Hiera reduces coding effort for class usage to
include '::sshkeymgmt'
or
class { 'sshkeymgmt': }
Example common.yaml
---
sshkeymgmt::groups:
test1:
gid: 5001
ensure: present
test2:
gid: 5002
ensure: present
test3:
gid: 5003
ensure: present
sshkeymgmt::users:
test1:
ensure: present
gid: 5001
uid: 5001
homedir: '/home/test1'
sshkeys:
- ssh-rsa AAAA ... Test1
- ssh-rsa AAAA ... Test5
test2:
ensure: present
gid: 5002
uid: 5002
homedir: '/home/test2'
sshkeys:
- ssh-rsa AAAA ... Test2
test3:
ensure: present
gid: 5002
uid: 5003
homedir: '/home/test3'
sshkeys:
- ssh-rsa AAAA ...Test3
test4:
ensure: present
gid: 5004
uid: 5004
homedir: '/home/test4'
sshkeys:
- ssh-rsa AAAA ... Test4
Example node1.yaml
The ssh keys and Unix users can be grouped by teams or departments or whatever groups you want to define.
---
sshkeymgmt::ssh_key_groups:
ops:
ssh_users:
- test1
- test2
dba:
ssh_users:
- test3
- test2
Class usage example
The users, groups and ssh key groups can be defined in Puppet code as well.
$groups = {
'test1' => {
gid => 5001,
ensure => present
}
}
$users = {
'test1' => {
ensure => present,
gid => 5001,
uid => 5001,
homedir => '/home/test1',
sshkeys => ['ssh-rsa AAAA ... Test1', 'ssh-rsa AAAA ... Test5']
}
}
$sshkeygroups = {
'ssh1': => {
'ssh_users' => ['test1', 'test2']
}
}
class { '::sshkeymgmt':
users => $users,
groups => $groups,
ssh_key_groups => $sshkeygroups
}
Reference
See REFERENCE.md
Limitations
This module has been tested on several Unix platforms, and no issues have been identified. But this module does not care about the sshd configuration. Please make sure the ssh authorized_keys files are stored in the location the sshd is expecting.
For an extensive list of supported operating systems, see metadata.json
Development
Contributions are welcome in any form, pull requests, and issues should be filed via GitHub.
Acceptance tests
Please add acceptance tests for your code as well. There's a script run_acceptance_tests.sh in the scripts folder which runs the tests for CentOS 7 and Ubuntu 18.04.
Changelog
See CHANGELOG.md
Reference
Table of Contents
Classes
sshkeymgmt
: Rollout ssh keys, Unix groups and Unix users
Defined types
sshkeymgmt::add_users
: User defined resource add_usersshkeymgmt::create_user
: User defined resource to create unix users
Classes
sshkeymgmt
Create Unix users and Unix groups and roll out the ssh keys of the users. Groups of users can be defined and rolled out. A user is regarded as a user group with only one member.
Examples
include sshkeymgmt
Parameters
The following parameters are available in the sshkeymgmt
class.
users
Data type: Hash
Hash with all defined Unix users
groups
Data type: Hash
Hash with all defined Unix groups
ssh_key_groups
Data type: Hash
Group of users to deploy on a host together with their aah keys
authorized_keys_base_dir
Data type: String
Base directory where to place ssh authorized keys files. Set this parameter if authorized keys files should not be located in user's home directory
Default value: ''
authorized_keys_owner
Data type: String
This parameter must be set if authorized_keys_base_dir is not empty. This parameter sets the owner of the authorized keys file.
Default value: ''
authorized_keys_group
Data type: String
This parameter must be set if authorized_keys_base_dir is not empty. This paremeter sets the group of the authorized keys file.
Default value: ''
authorized_keys_permissions
Data type: String
This parameter must be set if authorized_keys_base_dir is not empty. This parameter sets the file permissions of the authorized keys file.
Default value: ''
authorized_keys_base_dir_permissions
Data type: String
The permissions of the directory containing the ssh kex files if not stored within the user's home directory.
Default value: ''
Defined types
sshkeymgmt::add_users
Add users together with their ssh keys to the local uasers on an Unix host
Parameters
The following parameters are available in the sshkeymgmt::add_users
defined type.
ssh_users
Data type: Array
List of users
sshkeymgmt::create_user
Create Unix users
Parameters
The following parameters are available in the sshkeymgmt::create_user
defined type.
uid
Data type: Integer
Numeric uid
gid
Data type: Integer
Numeric group id
homedir
Data type: String
Home directory of the user. If empty it will be created from '/home' and the username
Default value: ''
comment
Data type: String
Comment describing the user
Default value: ''
shell
Data type: String
The Unix shell foer the user
Default value: '/bin/bash'
password
Data type: String
The password to be set
Default value: '!!'
ensure
Data type: Enum['present', 'absent']
Ensure if the user is present or absent. Valid values are 'present' or 'absent'.
Default value: 'present'
groups
Data type: Array
additional groups the user should belong to
Default value: []
sshkeys
Data type: Array
ssh keys to be added to the users authorized_keys file
Default value: []
Changelog
Release 1.1.0
- Update to PDK version 2.7.1
- bumped dependencies to most current versions
- removed old and added new OS
Release 1.0.0
- Updated to pdk 2.4.0
- Updated dependencies
- Updated supported Puppet versions and supported OSes
Release 0.9.4
- removed puppetlabs translate module. Thanks Ben Ford for the pull request addressing this.
Release 0.9.3
- updated pdk version (not published)
Release 0.9.2
- Added acceptance tests using Puppet Litmus
Release 0.9.1 (not released on Puppet Forge)
- Added a new parameter to make the ssh key base directory permissions configurable
- Added more unit test
Release 0.9.0
Initial release
Dependencies
- puppetlabs-stdlib (>= 4.6.0 < 10.0.0)
- puppetlabs-concat (>= 1.1.0 < 10.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2019 puppet-modules Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.