On Fri, Aug 19, 2005 at 08:38:44AM -0400, Katz, Dov B (IT) wrote: > 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. Indeed the auth iq I used to send was not ok. My client requests the auth options first, so I made the component do the same. And I got it working. [OUT]<route to='[EMAIL PROTECTED]' from='[EMAIL PROTECTED]' id='1' type='auth'><iq type='get'><query xmlns='jabber:iq:auth'><username>konst</username></query></iq></route> [IN]<route from='[EMAIL PROTECTED]' to='[EMAIL PROTECTED]' type='auth'><iq type='result'><query xmlns='jabber:iq:auth'><username>konst</username><digest/><password/><resource/></query></iq></route> That's pretty cool. I'll investigate it this way so far. Will get back to you with questions if I have some. Thanks for your help! -- konst at http://thekonst.net/ _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
