General discussion about Chef

authentication/openid


Chronological Thread 
  • From: snacktime <snacktime@gmail.com>
  • To: chef@lists.opscode.com
  • Subject: authentication/openid
  • Date: Sun, 19 Apr 2009 23:56:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=wurE9MbNxlodko64eZ1V5230rEFkeFt5m95YAvLvIvAUvRdJG1zfvCW6iAxx1oNKpV 6kjj8J4bNS+hzyxVG+IOAcNL8+ER9wzDcBzODjh3XsU8L3+bKOzqfai37hBEbQAzc9f7 zU8XbeNuu5+vktL/HLI52Nfqz3HDMLB70X9Ng=
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.

§