XMPP getting ' not Authorized ' when joining an p/w protected, already open chat

Source: Internet
Author: User
Tags vcard

When a XMPP password protected are already set up in a window with the account being logged back in, Pidgin tries to log Into the without a password and fails with a "not Authorized" error. Double-clicking on the Buddy List would log into the the properly.

This bug is seems to crop up in a specific set of criteria, but given that situation happens often (at least for me), it is still annoying. I hiberate my laptop often and go on VPN, so it comes up every time the network is re-connected.

Steps to Reproduce (100% reproducible on my side):

1. Log into password-protected XMPP chat room.2. Keep window open.3. Disable account or disconnect Internet connection4. Enable account or Re-connect Internet connection5. Error occurs when Pidgin attempts to relog into.

Relevant debug lines (with added line breaks):

(09:23:23)  jabber: Sending  (SSL)   ([Email protected]/spark):  <presence to = ' [email protected]/sineswiper ' ><priority>1</priority><c xmlns= ' http://jabber.org/ Protocol/caps '  node= ' http://pidgin.im/'  hash= ' sha-1 '  ver= ' i22w7cegorwdbnu0ziqwgpxr0go= '/> <x xmlns= ' Http://jabber.org/protocol/muc '/></presence> (09:23:23)  jabber: Recv  (SSL) (393):  <presence to= "[Email protected]/spark"  from= "[Email protected]/sineswiper]  type= "Error" ><priority>1</priority><c xmlns= "Http://jabber.org/protocol/caps"  node= "http://pidgin.im/"  hash= "Sha-1"  ver= "i22w7cegorwdbnu0ziqwgpxr0go="/><x xmlns= "Http://jabber.org/protocol/muc"/><error code= "401"  type= "auth" ><not-authorized  xmlns= "Urn:ietf:params:xml:ns:xmpp-stanzas"/&GT;&LT;/ERROR&GT;&LT;/PRESENCE&GT; (09:23:53)  gtkconv: setting active conversation on toolbar 0a3ee998 (09:23:53)  jabber: Sending  (SSL)   ([Email protected]/spark):  <presence to= ' [Email protected]/sineswiper ' >< priority>1</priority><c xmlns= ' http://jabber.org/protocol/caps '  node= ' http://pidgin.im/'  hash= ' sha-1 '  ver= ' i22w7cegorwdbnu0ziqwgpxr0go= '/><x xmlns= ' http://jabber.org/protocol/ Muc ' ><password>password</password></x></presence> (09:23:53)  jabber: recv   (SSL) (419):  <presence to= "[Email protected]/spark"  from= "[email protected]/ Mrsadmin "><priority>1</priority><c xmlns=" Http://jabber.org/protocol/caps " node=" http://pidgin.im/" hash=" Sha-1 " ver=" i22w7cegorwdbnu0ziqwgpxr0go= "/><x xmlns=" Vcard-temp: X:update "><photo/></x><x xmlns=" Http://jabber.org/protocol/muc#user "><item  Jid= "[Email protected]/1d4c2a8e " affiliation=" owner " role=" moderator "/></x></presence> (09:23:53)   jabber: sending  (SSL)   ([Email protected]/spark):  <iq type= ' get '  id= ' PURPLE93A1B4DC '  to= ' [email protected] ' ><query xmlns= ' http://jabber.org/protocol/disco# Info '  node= ' http://jabber.org/protocol/muc#traffic '/></iq> (09:23:53)  jabber: recv   (SSL) (462):  <presence to= "[Email protected]/spark"  from= "[email protected]/ Normaluser1 "><priority>1</priority><query xmlns=" Jabber:iq:last " seconds=" 300 "/ ><c xmlns= "Http://jabber.org/protocol/caps"  node= "http://pidgin.im/"  hash= "Sha-1"   Ver= "i22w7cegorwdbnu0ziqwgpxr0go="/><x xmlns= "Vcard-temp:x:update" ><photo/></x><x  xmlns= "Http://jabber.org/protocol/muc#user" ><item jid= "[Email protected]/spark"   Affiliation= "None"  role= "parTicipant "/&GT;&LT;/X&GT;&LT;/PRESENCE&GT; 

Note the difference between the presence requests. The first one does not send out a password via XML, and the second one does (which is the manual double-click into the RO OM). So, Pidgin was clearly not sending the password out when it should.


This article from "Cantgis" blog, declined reprint!

XMPP getting ' not Authorized ' when joining an p/w protected, already open chat

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.