Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,309
Community Members
 
Community Events
168
Community Groups

Invalid authzid error using Pidgin with HipChat

We've installed HipChat on an in-house server last week so we could test it out. We really liked the ability to use any XMPP client to connect to the service but having some difficulty getting it to work.

We followed the link here to test a few Pidgin clients but getting the error "invalid-authzid".  A debug dump of the login is below. Any thoughts as to why this isn't working? The BOSCH URL (never used it before) does not seem to work as explained in the link either.

The people using Pidgin connect to three other XMPP servers (two Cisco services, one Jabberd service) at various locations and they don't have this problem with these other hosts so we don't believe it's a client-side issue.  Thank you!

(13:26:34) sasl: Mechs found: PLAIN X-HIPCHAT-OAUTH2
(13:26:34) jabber: Sending (ssl) (some.user@my.domain.net/xmpp): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga='http://www.google.com/talk/protocol/auth' ga:client-uses-full-bind-result='true'>password removed</auth>
(13:26:34) jabber: Recv (ssl)(78): <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><invalid-authzid/></failure>
(13:26:34) sasl: Mechs found: X-HIPCHAT-OAUTH2
(13:26:34) sasl: No worthy mechs found
(13:26:34) connection: Connection error on 0x55a5d53fc5c0 (reason: 0 description: Invalid authzid)
(13:26:34) jabber: Recv (ssl)(16): </stream:stream>
(13:26:34) account: Disconnecting account some.user@my.domain.net/xmpp (0x55a5d4988e60)
(13:26:34) connection: Disconnecting connection 0x55a5d53fc5c0
(13:26:34) jabber: Sending (ssl) (some.user@my.domain.net/xmpp): </stream:stream>
(13:26:34) jabber: jabber_actions: have pep: NO
(13:26:34) jabber: jabber_actions: have pep: YES
(13:26:34) jabber: jabber_actions: have pep: NO
(13:26:34) connection: Destroying connection 0x55a5d53fc5c0

 

0 comments

Comment

Log in or Sign up to comment