[jdev] SASL debugging

Yves Goergen nospam.list at unclassified.de
Fri Dec 9 03:22:59 CST 2005

On 09.12.2005 06:05 (+0100), Vinod Panicker wrote:
> I thought you said it was an encoding error.  The encoding on these
> stanzas look fine to me.

Google Talk said it doesn't like the encoding. ejabberd comes further
and reports not authorised.

> From what I see from the decoded response
> that you are sending, the "realm" is missing, although its an optional
> parameter IIRC -

As far as I understood the SASL RFC, the realm is selected by the server
and the client must pass it back as-is. My server doesn't set a realm,
so nothing is sent back.

> Usually, a not-authorized means that you are missing the right
> credentials (incorrect username/password).  Do check on that as the
> first thing.

Username + password are ok, I can log in using these in Psi (which uses
the iq-auth thing instead of SASL, I haven't looked at that JEP yet).

But I want to add the PLAIN mechanism anyway so I can test it with that
one, too.

Yves Goergen "LonelyPixel" <nospam.list at unclassified.de>
"Does the movement of the trees make the wind blow?"
http://newsboard.unclassified.de - Unclassified NewsBoard Forum

More information about the JDev mailing list