[jdev] Incorrect Encoding

ARP alexandrepires2007 at yahoo.com.br
Wed Nov 15 13:47:16 CST 2006

Thx Guys,

But I made this and did not work:

auth_info := 
StrTobase64(chr(0)+'alpires2000 at gmail.com'+chr(0)+'mypassword');

send('<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" 

Well, the server continues answering with:

<failure  xmlns="urn:ietf:params:xml:ns:xmpp-sasl">


----- Original Message ----- 
From: "Norman Rasmussen" <norman at rasmussen.co.za>
To: "Jabber software development list" <jdev at jabber.org>
Sent: Wednesday, November 15, 2006 4:27 PM
Subject: Re: [jdev] Incorrect Encoding

> 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/ 


Você quer respostas para suas perguntas? Ou você sabe muito e quer compartilhar seu conhecimento? Experimente o Yahoo! Respostas !

More information about the JDev mailing list