I think this may be due to the type of auth you are doing... Are you sure that you are allowed to auth with user/password/resource?
See how another type of client like winjab/exodus auth's you and clone that kind of packet for your auth-set packet. Does that work? D -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Konstantin Klyagin Sent: Friday, August 19, 2005 8:35 AM To: Jabber software development list Subject: Re: [jdev] jabber:iq:auth in the component:accept namespace? On Thu, Aug 18, 2005 at 07:53:18AM -0400, Katz, Dov B (IT) wrote: Thanks a lot for your answer. I still have some questions though. > I have ldapauth.dovkatz.com which is an external "accept" > component handling auth. This was possible in jabberd 1.4.2x by > having <auth>jid</auth> in the config... So first you make your own > unique JIDs up for your local component's "user sessions". > This allows you to segregate incoming routed traffic. Is it possible to implement the same scheme with the default auth component and xdb as a user info storage? > SEND: > <route to="[EMAIL PROTECTED]/super" > from="[EMAIL PROTECTED]/SomeResource" id="CTG-C2S-0" > type="auth"> > <iq to="[EMAIL PROTECTED]/super" id="189" type="set"> > <query > xmlns="jabber:iq:auth"><username>dovkatz</username><password>*******</ > pa > ssword><resource>super</resource> > </query> > </iq> > </route> > RECV: > <route to="[EMAIL PROTECTED]/SomeResource" > from="ldapauth.dovkatz.com" id="CTG-C2S-0" type="auth"> <iq id="189" > type="result"><query > xmlns="jabber:iq:auth"><username>dovkatz</username><resource>super</re > so > urce></query> > </iq> > </route> I tried to do the same, but my transcript looks different: [IN]<handshake/> So as soon as I complete the component auth, I do: [OUT]<route to='[EMAIL PROTECTED]' from='[EMAIL PROTECTED]' id='1' type='auth'><iq to='[EMAIL PROTECTED]' id='2' type='set'><query xmlns='jabber:iq:auth'><username>konst</username><password>****</passwor d></query></iq></route> [IN]<route from='[EMAIL PROTECTED]' to='[EMAIL PROTECTED]' type='auth'><iq id='2' type='error'><query xmlns='jabber:iq:auth'><username>konst</username><password>****</passwor d></query><error code='406'>Not Acceptable</error></iq></route> Using <route/> stanzas sounds like a good idea. I wish I could get through this "Not Acceptable" problem. Thanks again. -- konst at http://thekonst.net/ _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
