- From: snacktime <snacktime@gmail.com>
- To: chef@lists.opscode.com
- Subject: Re: authentication/openid
- Date: Mon, 20 Apr 2009 00:15:41 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ICTookyqsbEHfJvtszOBqP5IfYMTtvvGgOIKu5cAptu6C4Q5LbjzE0PS5ZJ3vrp7Uq ztAzPt2l3Oa8vq3XA5QIAW96grTlcDFT3HbZVi7PrGYoJxEsfeaSb8LCbmOIuaihFukp LlENH1VYWgePJCD2lYb2Nf5RNwX77GfF7/R7U=
Ok so it looks like chef serves as an openid server also. So just register with chef-client, make the node an admin, and login to the web ui with that? Is that correct?
On Sun, Apr 19, 2009 at 11:56 PM, snacktime
<snacktime@gmail.com> wrote:
What's the intended way to restrict access to the server and web ui? For the web ui it looks like you need to run your own openid provider and set it as an approved provider. For chef clients it looks like it's ssl client certs. Is that correct?
Chris
Archive powered by MHonArc 2.6.16.