- From: Joel Merrick <joel.merrick@gmail.com>
- To: chef <chef@lists.opscode.com>
- Subject: [chef] OpenID choices
- Date: Thu, 30 Jul 2009 10:43:47 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=QLm0LbTe/9PZ92mE+JRcZY4e/RU5WSUVJ1pK52C2eH7pOLG6Rb43LfSaWUhQlkOi1q WFLzN+wsKN2kZlWm0SkCnyveR9R5UPeBlmvRK3cB5SNEs3p9y83tJtLEbJexC4YpTiWl GZPYC8iCbeS/+dGrMH/he6B3xCK3TAb09dH8k=
Hi all,
What are people's preferred choices for running their own OpenID server?
I have to admit that I've never used OpenID for systems authorisation
before, so I'm open to suggestions.
On a side note, anyone know when the non-OpenID (ssl / ssh key
sharing?) auth layer will be available? I've got a feeling I'm not
going to be able to get $WORK around to the idea of using it in this
fashion, mainly because it's not something I or many of the other
engineers have used.
Cheers in advance,
Joel
--
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
- [chef] OpenID choices, Joel Merrick, 07/30/2009
Archive powered by MHonArc 2.6.16.