[Pidgin] #7654: Empty stream features cause pidgin to try non-sasl auth even after a successful sasl authentication

[Pidgin]

#7654: Empty stream features cause pidgin to try non-sasl auth even after a
successful sasl authentication
--------------------+-------------------------------------------------------
 Reporter:  roman   |        Owner:  darkrain42
     Type:  defect  |       Status:  pending   
Milestone:          |    Component:  XMPP      
  Version:  2.5.2   |   Resolution:            
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by darkrain42):

  * status:  new => pending


Comment:

 What exactly would you have Pidgin do in this situation?  As deryni
 already said, the *only* thing that can happen at that point is resource
 binding, but your server isn't advertising resource binding, so Pidgin
 cannot proceed.  Admittedly, Pidgin shouldn't be trying legacy non-SASL
 auth, but the alternative is simply to generate a connection error.

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