[Pidgin] #5149: XMPP "Not Authorized" when trying to login using 2.4.0 on Windows

[Pidgin]

#5149: XMPP "Not Authorized" when trying to login using 2.4.0 on Windows
-----------------------+----------------------------------------------------
  Reporter:  jmitchem  |       Owner:  nwalp
      Type:  defect    |      Status:  new  
  Priority:  minor     |   Milestone:       
 Component:  XMPP      |     Version:  2.4.0
Resolution:            |    Keywords:       
   Pending:  0         |  
-----------------------+----------------------------------------------------
Comment (by jmitchem):

 Thanks for getting back to me so quickly.

 I believe we're using Wildfire.  It seems Wildfire became Openfire, but I
 don't think we've upgraded since the name change.

 The guy who set it up got everything working so that we could use it
 onsite and offsite, but he is no longer with the company.  As far as I
 know, nobody has touched it since.

 (And frankly, up until now, we haven't had any problems whatsoever with
 any of the clients we've used: Gaim, Pidgin, Psi, or whatever that
 whiteboarding over Jabber software is... Coccinella, I believe.)

 I looked at that issue-thread you linked, but I really wasn't able to
 follow most of it.  Specifically, I don't know anything about SASL,
 GSSAPI, what xmpp.fqdn is, or how any of that has relevance to why I'm no
 longer authorized to a server that I'm clearly authorized to.

 About as much as I follow is that it's somehow a Jive/Wildfire/Openfire
 issue, and not a Pidgin issue, and the fix is to go modify the server
 somehow.  However, I don't have access to modify anything on the server
 itself.

 Is there anything I can do from the client side to make Pidgin connect
 with our existing server? or am I going to have to stick with out-of-date
 versions?

-- 
Ticket URL: <http://developer.pidgin.im/ticket/5149#comment:2>
Pidgin <http://pidgin.im>
Pidgin