powered by Jive Software

2.5.3 - username/password no longer valid

I just upgraded to 2.5.3 and find that I can no longer login to my gmail.com account with the same username and password. It worked fine in the previous version. Anyone else finding this? Windows Vista.

Hey, I reported this issue in: SPARK-768

Thanks,

Francisco

More info: I confirmed same username/password works fine on Vista in 2.5.2

Here is the debug raw packets sent/received on 2.5.3, with some values deleted to protect the innocent (debug output not possible in 2.5.2). The received error is “invalid authzid”. Note I deleted the id sent, but maybe it is incorrectly encoded because it extremely often seems to have a “=” at the end of the base 64 encoding? Please add this info to bug report.

Raw sent packets

<stream:stream to=“gmail.com” xmlns=“jabber:client” xmlns:stream=“http://etherx.jabber.org/streams” version=“1.0”>

<starttls xmlns=“urn:ietf:params:xml:ns:xmpp-tls”/>

<stream:stream to=“gmail.com” xmlns=“jabber:client” xmlns:stream=“http://etherx.jabber.org/streams” version=“1.0”>

<auth mechanism=“PLAIN” xmlns=“urn:ietf:params:xml:ns:xmpp-sasl”>[deleted]==</auth>

<presence id="[deleted]" type=“unavailable”></presence>

</stream:stream>

Raw received packets

<?xml version=“1.0” encoding=“UTF-8”?><stream:stream from=“gmail.com” id="[deleted]" version=“1.0” xmlns:stream=“http://etherx.jabber.org/streams” xmlns=“jabber:client”>

<stream:features><starttls xmlns=“urn:ietf:params:xml:ns:xmpp-tls”><required/></starttls>&l t;mechanisms xmlns=“urn:ietf:params:xml:ns:xmpp-sasl”><mechanism>X-GOOGLE-TOKEN< /mechanism></mechanisms></stream:features>

<proceed xmlns=“urn:ietf:params:xml:ns:xmpp-tls”/>

<?xml version=“1.0” encoding=“UTF-8”?><stream:stream from=“gmail.com” id="[deleted]" version=“1.0” xmlns:stream=“http://etherx.jabber.org/streams” xmlns=“jabber:client”>

<stream:features><mechanisms xmlns=“urn:ietf:params:xml:ns:xmpp-sasl”><mechanism>PLAIN</mechanis m><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></st ream:features>

<failure xmlns=“urn:ietf:params:xml:ns:xmpp-sasl”><invalid-authzid/></failur e></stream:stream>

Found base 64 encoding of auth id to potentially look a bit askew.