I am using Gaim as a client to our corporate Intranet chat server and it was working great. However, I just reinstalled my OS and when I try to connect to that chat server again I get a "not authorized" message. I enabled debug tracing and near as I can figure the client and server exchange some sort of keys. So, my guess is that with the reinstall my gaim has a new key, but the server stored the old key. Can anyone confirm/deny that assumption? Is there a way to fix this on the client end, or do I have to get the admins to do some work?
Thanks,
Isaac
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using Gaim as a client to our corporate Intranet chat server and it was working great. However, I just reinstalled my OS and when I try to connect to that chat server again I get a "not authorized" message. I enabled debug tracing and near as I can figure the client and server exchange some sort of keys. So, my guess is that with the reinstall my gaim has a new key, but the server stored the old key. Can anyone confirm/deny that assumption? Is there a way to fix this on the client end, or do I have to get the admins to do some work?
Thanks,
Isaac
Which protocol is this with?
It's the Jabber protocol.
Post the Debug Window XML output of your trying to connect.
jabber: Sending: <?xml version='1.0' ?>
jabber: Sending: <stream:stream to='192.168.200.74' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
jabber: Recv (573): <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="cvchat" id="60ef398b" xml:lang="en" version="1.0"><stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>ANONYMOUS</mechanism></mechanisms><auth xmlns="http://jabber.org/features/iq-auth"/><register xmlns="http://jabber.org/features/iq-register"/></stream:features>
jabber: Sending: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
jabber: Recv (50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
jabber: Sending (ssl): <stream:stream to='192.168.200.74' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
jabber: Recv (ssl)(512): <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="cvchat" id="60ef398b" xml:lang="en" version="1.0"><stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism><mechanism>DIGEST-MD5</mechanism><mechanism>ANONYMOUS</mechanism></mechanisms><auth xmlns="http://jabber.org/features/iq-auth"/><register xmlns="http://jabber.org/features/iq-register"/></stream:features>
sasl: Mechs found: PLAIN CRAM-MD5 DIGEST-MD5 ANONYMOUS
jabber: Sending (ssl): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
jabber: Recv (ssl)(212): <challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">cmVhbG09ImN2Y2hhdCIsbm9uY2U9IlVZZi9wVmZqVWttU1J2aVNnMmVQT01MM01sTDlPc0pvL29wSU0vOUIiLHFvcD0iYXV0aCIsY2hhcnNldD0idXRmLTgiLGFsZ29yaXRobT0ibWQ1LXNlc3Mi</challenge>
sasl: DIGEST-MD5 client step 2
jabber: Sending (ssl): <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9ImlzYWFjLndhZ25lciIscmVhbG09ImN2Y2hhdCIsbm9uY2U9IlVZZi9wVmZqVWttU1J2aVNnMmVQT01MM01sTDlPc0pvL29wSU0vOUIiLGNub25jZT0iRW5KUHF4ZVdkNGpEY0lDMjVpU3piOVNzbFZiejkxaTFWbG1GdmxVQmpaND0iLG5jPTAwMDAwMDAxLHFvcD1hdXRoLGRpZ2VzdC11cmk9InhtcHAvMTkyLjE2OC4yMDAuNzQiLHJlc3BvbnNlPWUzYjgzODc2ZTY1ZmM3MDIxYjUyYzlhOTkyMWRiMjIy</response>
jabber: Recv (ssl)(77): <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized/></failure>
account: Disconnecting account 0x813e988
connection: Disconnecting connection 0x85fbea8
connection: Destroying connection 0x85fbea8