- From: Noah Kantrowitz <
>
- To:
- Subject: [chef] Re: Restrict access to nodes
- Date: Tue, 27 May 2014 03:20:43 -0700
Access to the private key is considered authentication. The only way you know
which node is talking to the API is which key it uses. It is up to you to
ensure these are kept safe, though the default key generation system using
the validation key will write it out securely.
--Noah
On May 27, 2014, at 1:19 AM, Jerry Raj
<
>
wrote:
>
Hi,
>
I've been wading through the tutorials and almost everything works just
>
fine. I had a question about how security works:
>
>
As far as I can tell, once a client is created from the web-UI and its
>
private key generated, a client can connect as any node using the private
>
key. Is it possible to restrict a client to using just a subset of nodes?
>
I'm thinking of a scenario where we want to make sure that the nodes only
>
have access to the runlists configured for them.
>
>
Thanks
>
-Jerry
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
Archive powered by MHonArc 2.6.16.