The hash + sequence values are for zero-k authentication.. Checkout: http://docs.jabber.org/draft-proto/html/zerok.html
for docs.. Also, if you see <digest/> returned, you should still be able to authenticate, but 0k auth is a "stronger" mechanism for auth'ing... Winjab (actually JabberCOM does this) automatically picks the "best" supported auth type for logging in based on the available types in the iq-result. Peter M. ----- Original Message ----- From: "Dan Bray" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 02, 2001 9:09 AM Subject: [JDEV] Authorization Help > I'm writing my own special purpose Jabber client and am having trouble with > the authentication. I am able to connect to Jabber.com with the following > exchange: > > SEND:<iq type="get" id="JCOM_2"><query > xmlns="jabber:iq:auth"><username>jdbray</username></query></iq> > RECV:<iq type='result' id='JCOM_2'><query > xmlns='jabber:iq:auth'><username>jdbray</username><password/><digest/><resou > rce/></query></iq> > > I respond with the hashed digest. However, when I attempt to connect to > jabber.org I get a different response which includes a <sequence> and > <token>. Winjab (which can connect) returns a <hash> value. I can't find > this in the docs and don't know what to use to generate the hash or what the > difference is betweent he <has> and <digest> tags. > > All help is appreciated. > > Dan > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
