On Sun, Sep 24, 2006 at 06:25:23PM +0300, Roman at Alax.Info wrote: > Hi, > > Could anybody please shed some light on the weird problem with > jabber.org server (not others!) > > I telnet to jabber.org 5222 and send the following text: > > <?xml version="1.0"?> > <stream:stream xmlns:stream="http://etherx.jabber.org/streams"; > xmlns="jabber:client" to="jabber.org"> > <iq type="set" to="jabber.org" id="auth_2"> > <query xmlns="jabber:iq:auth"> > <username>AAA</username> > <password>BBB</password> > <resource>Test</resource> > </query></iq> > > AAA and BBB are 100% valid values (I can use the to login using Psi IM) > > I receive in response: > > <?xml version='1.0'?><stream:stream xmlns='jabber:client' > xmlns:stream='http://etherx.jabber.org/streams' id='293036105 > ' from='jabber.org' xml:lang='en'> > <iq type='error' from='jabber.org' id='auth_2'> > <query xmlns='jabber:iq:auth'> > <username>AAA</username> > <password>BBB</password> > <resource>Test</resource> > </query> > <error code='401' type='auth'><not-authorized > xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error> > </iq> > > That is the error is "unauthorized". The same plain text authorization > works on other servers. The same error code I receive trying to > authorize on jabber.org using digest authorization and via TLS > connection to port 5223. > > Many thanks in advance and please accept my apologies if posted into > wrong list. > I'm not sure if it can be caused by that, but, you did not <iq type='get'><query xmlns='jabber:iq:auth'/></iq> to ask what fields are needed for the authorization. Maybe you have to do that first.
Not talking about the fact that this way is deprecated and you should use SASL. -- This email was generated by a biological random generator. If you want more random text, just respond to this email. Michal "vorner" Vaner
pgpM4YbnXyX55.pgp
Description: PGP signature
