What is the correct way to use Chef-server's 'validation key'?
Posted
by
Socio
on Server Fault
See other posts from Server Fault
or by Socio
Published on 2012-10-31T09:05:06Z
Indexed on
2012/12/19
23:05 UTC
Read the original article
Hit count: 138
It seems to me that the recommended way of adding clients to a chef server - or my understanding of it - is flawed.
When the chef-client runs, it checks if it has a client key. If the client key does not exist, it then attempts to "borrow" the validation client's identity to register itself with the server. In order to do that, the validation client's private key needs to be copied to the host and placed in /etc/chef/validation.pem.
So the "validation key" is basically the superuser credential, allowing anyone who possesses it full access to the chef server? Am I reading this right?
Surely the correct model would be for clients to generate their own keypair, and submit the public key to the chef server. Clients should never need access to this superuser "validation key".
How can I do it in this, more secure, manner?
© Server Fault or respective owner