This is what I get (changed myName and myPass from real ones) using my gmail account and PSI
<?xml version="1.0"?> <stream:stream xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client" to="gmail.com" > <stream:stream from="gmail.com" id="E454CB10" xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"> <iq type="get" id="auth_1" to="gmail.com" > <query xmlns="jabber:iq:auth"> <username>myname</username> </query> </iq> <iq from="gmail.com" type="result" id="auth_1" > <query xmlns="jabber:iq:auth"> <username/> <resource/> <password/> </query> </iq> <iq type="set" id="auth_2" to="gmail.com" > <query xmlns="jabber:iq:auth"> <username>myname</username> <password>mypass</password> <resource>Psi</resource> </query> </iq> <iq from="gmail.com" type="error" id="auth_2" > <query xmlns="jabber:iq:auth"> <username>myname</username> <password/> <resource>Psi</resource> </query> <error type="auth" code="403" > <forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">username or password not correct</text> </error> </iq> On 8/23/05, Ulrich Staudinger <[EMAIL PROTECTED]> wrote: > We'll soon know - tomorrow is approaching swiftly! > > > > Fabio Forno schrieb: > > >Chris Chen wrote: > > > > > >>From what I can tell, after TLS negotiation, Google supports the > >>following mechanisms: > >> > >>PLAIN > >>X-GOOGLE-TOKEN > >> > >> > > > >Yes now I can get the mechamisms too. I've tried using plain, my gmail > >account and talk.google.com as realm with no success :/ > > > > > > > _______________________________________________ > jdev mailing list > jdev@jabber.org > http://mail.jabber.org/mailman/listinfo/jdev > _______________________________________________ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
