PLAIN SASL authentication fails to authenticate clients that are sending bare JIDs
"We just ran into a problem doing Authentication withWildFire using the Open Source SoapBox Framework and SASL Plain.
The SoapBox Framework is using a bare JID ("user@server")as the authid that's passed across the link. The Jive server is expectingonly a user name ("user").
The RFC doesn't really say either way, and I figurethis is a good chance to get it clarified.
(The SoapBox Framework now can do both, but I would sureprefer just one or the other)