Managing SSH Authorized Keys with Puppet21 October 2013
In this post, I’ll show you how I extended my solution for managing user accounts with Puppet to include managing SSH authorized keys. With this solution in place, user accounts managed through Puppet can also include their SSH public key, and that public key will automatically be installed on hosts where the account is realized. All in all, I think it’s a pretty cool solution.
Just to refresh your memory, here’s the original Puppet manifest code I posted in the original article; this code uses define-based virtual user resources that you then realize on a per-host basis.
(If the code block showing the Puppet code isn’t appearing above, click here.)
Since I posted this original code, I’ve made a few changes. I switched some of the hard-coded values to parameters (stored in a separate subclass), and I made a few stylistic/syntactic changes based on running the code through
puppet-lint. But, by and large, this is still quite similar to the code I’m running right now.
Here’s the code after I modified it to include managing SSH authorized keys for user accounts:
(Can’t see the code block? Click here.)
Let’s walk through the changes between the two snippets of code:
Two new parameters are added,
$sshkey. These parameters hold, quite naturally, the SSH key type and the SSH key itself.
Several values are parameterized, pulling values from the
You can note a number of stylistic and syntactical changes.
accounts::virtualclass now includes a stanza using the built-in
ssh_authorized_keyresource type. This is the real heart of the changes—by adding this to the virtual user resource, it makes sure that when users are realized, their SSH public keys are added to the host.
With this code in place, you’d then define a user like this:
(Click here if the code block doesn’t appear above.)
The requirement for
Class['accounts::config'] is to ensure that various configuration tasks are finished before the user account is defined; I discussed this in more detail in this post on Puppet, user accounts, and configuration files. Now, when I realize a virtual user resource, Puppet will also ensure that the user’s SSH public key is automatically added to the user’s
.ssh/authorized_keys file on that host. Pretty sweet, eh? Further, if the key ever changes, you need only change it on the Puppet server itself, and on the next Puppet agent run the hosts will update themselves.
I freely admit that I’m not a Puppet expert, so there might be better/faster/more efficient ways of doing this. If you are a Puppet expert, please feel free to weigh in below in the comments. I welcome all courteous comments!Tags: Automation · Linux · Puppet · SSH Previous Post: Installing Open vSwitch on Ubuntu with Puppet Next Post: Technology Short Take #36