The choices are: * OAuth SASL http://tools.ietf.org/html/draft-ietf-kitten-sasl-oauth-08
IMHO it would work fine with OpenID Connect since OpenID Connect is based on OAuth 2.0.
* OpenID SASL http://tools.ietf.org/html/rfc6616 * SAML SASL http://tools.ietf.org/html/rfc6595 http://tools.ietf.org/html/draft-ietf-kitten-sasl-saml-ec-03 The answer will depend on the type of systems you want to inter-work with. Ciao Hannes On 09/18/2012 03:21 AM, Randy Turner wrote:
What about a combination...OpenID Connect ? Peter Saint-Andre <[email protected]> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/17/12 3:00 PM, Ivan Martinez wrote: > I'm currently considering wether to use OAuth2 or OpenID2 in my > server. Which one do you think will be more adopted as a user > authentication mechanism in XMPP servers?. Which companies are > planing to use each of them?. IMHO it is much more likely that people will implement and deploy OAuth2 than OpenID for XMPP authentication. /psa -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBXlNAACgkQNL8k5A2w/vwhhgCfdakf/6wV7D+shOKcerR6bcTP YFYAoI60RJcxNcz3Uj7X0kA1CWfz9pot =0TLT -----END PGP SIGNATURE-----
