[jdev] Incorrect Encoding

Norman Rasmussen norman at rasmussen.co.za
Wed Nov 15 13:27:06 CST 2006


On 11/15/06, Norman Rasmussen <norman at rasmussen.co.za> wrote:
> My guess this is a bug on Google's end.  I wonder if any of the google
> guys would be able to confirm this.

woops, my bad.  I thought Google's servers were totally wrong, turns
out they just _require_ the SASL auth data when the auth mech is
picked.

On 11/15/06, Matthias Wimmer <m at tthias.eu> wrote:
> It means that the <auth/> element should contain a zero byte, followed
> by your username, followed by a zero byte, and your password. This data
> should be BASE64-encoded.
>
> How this works is not part of the XMPP standard, but part of the
> definition of the SASL PLAIN mechanism.

eg: try:

<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl"
mechanism="PLAIN">AHJvYgBzZWNyZXQ=</auth>

where AHJvYgBzZWNyZXQ= is base64 (\0rob\0secret\)

i.e. use base64(\0<username>\0<password>)  The first \0 is important!

-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/



More information about the JDev mailing list