Ejabberd 2.1.6 as far i know, doesnot support GSSAPI
So... it's ok for me, because we need to replace Active Directory with Samba PDC domain in a nearest future
But we still want to authorize clients on a server in a password-free manner/way. And i think, SASL EXTERNAL is reasonable choice for this.
But.. Ejabberd 2.1.6 doesnt support client authentication by supplying a valid client SSL certificate!
Hmm... Tell me please, maybe, in the upcoming 3.0.0 release branch normal SASL support will be in a place?
DRVTiny wrote: Ejabberd 2.1.6
Ejabberd 2.1.6 as far i know, doesnot support GSSAPI
You are right. But there's a patch that you can apply to ejabberd 2: http://www.ejabberd.im/cyrsasl_gssapi
Ejabberd 2.1.6 doesnt support client authentication by supplying a valid client SSL certificate!
Hmm... Tell me please, maybe, in the upcoming 3.0.0 release branch normal SASL support will be in a place?
I guess you refer tohttp://xmpp.org/extensions/xep-0178.html
I do not see any reference to implementation of that protocol in http://www.ejabberd.im/protocols
You could sponsorship the development of that feature.
But... is this a feature nor
But... is this a feature nor absolutely standard widely used SASL mechanism?
SASL required; SASL EXTERNAL optional
But... is this a feature nor absolutely standard widely used SASL mechanism?
Support for SASL negotiation is required:
http://tools.ietf.org/html/draft-ietf-xmpp-3920bis-22#section-6.2
But support for the SASL EXTERNAL mechanism is optional, not required.