From: Norman R. <no...@ra...> - 2010-06-13 19:05:49
|
This is fixed by this patch: http://github.com/normanr/xmpppy/commit/9518b54e12051d1ae0894b47264cc7f5f3c6b1ba On Sun, Jun 13, 2010 at 10:20 AM, mahdieh saeed <mah...@gm...>wrote: > Hi , > I want to use xmpppy for connecting into "jabberd2" server.My code is: > > jid=xmpp.protocol.JID('ex...@ja...') > cl=xmpp.Client(jid.getDomain(),debug=['always']) > cl.connect() > cl.auth(jid.getNode(),'123') > > But authentication has been failed.Debug reports are : > > DEBUG: sasl start Plugging <xmpp.auth.SASL instance at 0x934422c> > into <xmpp.client.Client instance at 0x934034c> > DEBUG: dispatcher info Registering handler <bound method > SASL.SASLHandler of <xmpp.auth.SASL instance at 0x934422c>> for "challenge" > type-> ns->(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: dispatcher warn Registering namespace > "urn:ietf:params:xml:ns:xmpp-sasl" > DEBUG: dispatcher info Registering protocol "unknown" as > xmpp.protocol.Protocol(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: dispatcher info Registering protocol "default" as > xmpp.protocol.Protocol(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: dispatcher warn Registering protocol "challenge" as > xmpp.protocol.Protocol(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: dispatcher info Registering handler <bound method > SASL.SASLHandler of <xmpp.auth.SASL instance at 0x934422c>> for "failure" > type-> ns->(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: dispatcher warn Registering protocol "failure" as > xmpp.protocol.Protocol(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: dispatcher info Registering handler <bound method > SASL.SASLHandler of <xmpp.auth.SASL instance at 0x934422c>> for "success" > type-> ns->(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: dispatcher warn Registering protocol "success" as > xmpp.protocol.Protocol(urn:ietf:params:xml:ns:xmpp-sasl) > DEBUG: socket sent <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" > mechanism="PLAIN">a2hhckBqYWJiZXIubXkAa2hhcgAxMjM=\n</auth> > DEBUG: socket got <failure > xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> > <incorrect-encoding/> > </failure> > DEBUG: nodebuilder down DEPTH -> 2 , tag -> > urn:ietf:params:xml:ns:xmpp-sasl failure, attrs -> {} > DEBUG: nodebuilder down DEPTH -> 3 , tag -> > urn:ietf:params:xml:ns:xmpp-sasl incorrect-encoding, attrs -> {} > DEBUG: nodebuilder up DEPTH -> 3 , tag -> > urn:ietf:params:xml:ns:xmpp-sasl incorrect-encoding > DEBUG: nodebuilder up DEPTH -> 2 , tag -> > urn:ietf:params:xml:ns:xmpp-sasl failure > DEBUG: dispatcher ok Got urn:ietf:params:xml:ns:xmpp-sasl/failure > stanza > DEBUG: dispatcher ok Dispatching failure stanza with type-> > props->[u'urn:ietf:params:xml:ns:xmpp-sasl'] id->None > DEBUG: sasl error Failed SASL authentification: <incorrect-encoding > /> > DEBUG: sasl stop Plugging <xmpp.auth.SASL instance at 0x934422c> > out of <xmpp.client.Client instance at 0x934034c>. > > But username and password is correct and I can connect into it by > "pidgin".But when connect into gmail account every thing is okay. Does any > body know about my problem? > > > Regards > > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Xmpppy-devel mailing list > Xmp...@li... > https://lists.sourceforge.net/lists/listinfo/xmpppy-devel > > -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |