[ejabberd] Can't mix XMPP and non-SASL auth

Christoph Schmidt csc at newbase.de
Tue Nov 9 13:58:19 MSK 2004

Magnus Henoch wrote:

> But when the client sends version='1.0' and then tries to use non-SASL
> authentication, ejabberd never answers.  The reason the client tries
> to do this is that it understands stream features, but doesn't have an
> SASL library loaded.
> Can/should this be fixed?  If so, ejabberd might also advertise the
> stream feature "http://jabber.org/features/iq-auth", as described in
> JEP-0078.

This is strictly XMPP-compliant. A client claiming it supports XMPP 1.0 
should not try to use an unadvertised feature.
Anyway, as ejabberd understands jabber:iq:auth, it could advertise and 
handle it...

> Magnus
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd

More information about the ejabberd mailing list