The <sequence/> + <token/> (and <hash/> are for (optional) zero-knowledge authentication, but you can just send your <digest/> and authenticate that way. For more on zero-knowledge auth, go here:
http://docs.jabber.org/draft-proto/html/zerok.html Peter -- Peter Saint-Andre email/jabber: [EMAIL PROTECTED] web: http://www.saint-andre.com/ On Tue, 2 Oct 2001, Dan Bray wrote: > 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
