Hi all, could anyone explain the rationale behind using openID as the
authentication layer and how easy it is to swap out…
Also what authentication schemes are supported?
Many thanks
Joel
–
$ echo “kpfmAdpoofdufevq/dp/vl” | perl -pe ‘s/(.)/chr(ord($1)-1)/ge’
On 14/07/2009, at 9:20 PM, Joel Merrick wrote:
Hi all, could anyone explain the rationale behind using openID as the
authentication layer and how easy it is to swap out...
Swapping it out is not an (easy) possibility, at this stage. You'd
have to slice and dice some code, and that'd be very dicey work.
Also what authentication schemes are supported?
OpenID authn will be removed in favor for a signed key mechanism in
0.8.0, which many of our users are looking forward too 
Regards,
--
AJ Christensen, Software Engineer
Opscode, Inc.
E: aj@opscode.com
On Tue, Jul 14, 2009 at 11:10 AM, Arjuna Christensenaj@opscode.com wrote:
On 14/07/2009, at 9:20 PM, Joel Merrick wrote:
Hi all, could anyone explain the rationale behind using openID as the
authentication layer and how easy it is to swap out...Swapping it out is not an (easy) possibility, at this stage. You'd have to
slice and dice some code, and that'd be very dicey work.
I imagined it wouldn't be
Also what authentication schemes are supported?
OpenID authn will be removed in favor for a signed key mechanism in 0.8.0,
which many of our users are looking forward too
That sounds much more functional. I only became aware of chef
recently, but the one thing turning me away from using it more is the
lack of support for other auth schemes. I'll continue with my testing
and wait the 0.8.0 release with baited breath
Regards,
AJ Christensen, Software Engineer
Opscode, Inc.
E: aj@opscode.com
--
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'