cocoaforge

I allowed Adium to run its autoupdate, allowed it to change its keychain passwords etc., and my gmail, icq and aim accounts all appear to work correctly.

My jabber account at work, though, started asking for its passwords constantly.

I closed Adium, went to KeyChain Access in 10.4.11 and removed the jabber password. Reopened Adium, and reentered password.

no luck..... Other people at work on macs have not had this problem. Their Adium updated and worked just fine.


Ideas? I've also check to see if Growl or Peerguardian could be stepping in here somehow...but I'm not seeing any blocks or anything else that would lead me to believe they are the problem.

Please use this build:
http://adiumx.cachefly.net/Adium_1.2-debug.dmg

and then open Adium, open the Adium Debug Window from the Adium menu, and attempt to connect just your Jabber account which isn't working. Then, email me ( http://adiumx.com/faq/evands for my address) the debug log, and I'll take a look

Log sent.

I'm kind of wondering if the problem hasn't got to do with Adium's handling of the server certificate. It seems to want me to confirm trust on the cert every time.... even though I've looked at the cert in Adium and thrown the "Always Trust" box, and individual settings in the detail.

Another note.... I was able to connect to the server by using a slightly different account name than I should be using....

Our server is set up with the user names being "account@jabber.company.com" Before the upgrade, that name format worked for me. On a whim, I tried logging in as "account@company.com" and it worked with no issues. The guys with the server say they see "account@jabber.company.com" logged in. So ... much goofiness.

I've tried deleting the app support folder for adium with a reinstall, and deleting the certs and passwords from keychain access....but the problem with this one account won't go away.

good luck with the logs and thanks.

I am hang a heck of a time with 1.2.

On launch, it hangs. It is consistent. However, if I disable my connectivity, then launch, it runs. Then, if I reconnect to the network, all of my accounts including my Corporate Jabber account works, with the exception of the GTalk account. I may need to adjust the port there.

I captured a log of this process. It is pretty long. I can send it to you if it helps.

Forgot to mention....I've also seen adium ask to confirm a ticket password (kind of like a kerberos ticket pass) in addition to its own little password confirmation box. Could it be a session ticket that won't clear...or I can't see?

bregan wrote:I am hang a heck of a time with 1.2.

On launch, it hangs. It is consistent. However, if I disable my connectivity, then launch, it runs. Then, if I reconnect to the network, all of my accounts including my Corporate Jabber account works, with the exception of the GTalk account. I may need to adjust the port there.

I captured a log of this process. It is pretty long. I can send it to you if it helps.

http://trac.adiumx.com/wiki/Sampling

carphunter: your company's server reports to Adium that it supports GSSAPI (also called Kerberos5) authentication. Adium sees that you have a GSSAPI identity of some sort on your computer, so it uses this to authenticate. The server then rejects your credentials.

Could you please ask the server's administrator / support group what their comments are about this and let us know?

ok... more playing.

When I talked to the server guys, they basically said "well, you're computer must be storing a ticket that's wrong, or something is confused on the client side that's passing a wrong ticket for the jabber accounts."

FYI....from what I can see, my machine doesn't generate a kerb ticket for anything other than Adium. When I boot the sys and check for a ticket, there's nothing there. Ticket only becomes apparent when I run Adium and enter a ticket password.


So... I did some more playing...with careful reading of password dialogs.

If I use my account@jabber.company.com login, and hit cancel when adium requests my ticket password, and then enter my account password in adium's normal pass request box...the account will work online. If I enter the ticket password...the account will not go online, just cycle asking for my password. Every time I quit adium and restart it, it will ask for my ticket password.

If I use my account@company.com login, I can enter, or not enter the ticket password, and the account will work with the jabber server.

The jabber server knows to check my account@jabber.company.com login pass against my system-wide account@company.com credentials. It's looking kind of like, though, that my mac is having some trouble responding to the server after that happens....like it only sees a valid back-and-forth of name/pass with the account@company.com credentials.

Make sense?


If I had a dialog button in the account settings that said "do not allow kerb. authentication" the problem would go away . (I know it doesn't "fix" the problem.... it just means I don't have to deal with it). I asked if the server guys shut off kerb5 authentication if it would screw things up for other users, and they said it would....so that's not an option.

Having never used Kerberos5 or GSSAPI personally, and having no access to a server which does, you'll have to bear with me. What's a ticket password, and where are you prompted to enter it? Could you screenshot the dialogue presented, as I've never seen it?

And to be sure I'm understanding
1. accountname@company.com works perfectly, except that there seems to be some prompt which is totally ignored? That is, you get asked for a "ticket password" but it doesn't matter what you put, whether it's the right or wrong password?
2. accountname@jabber.company.com (which presumably is the jabber server itself but not the real identity you have?) works only if you enter a wrong password for your "ticket password"?

I'll try to screen shot the process tomorrow.

It's not that I can enter any password for the account@company.com... I have to enter my correct password. I'm just saying if at this request, I hit the cancel button, I can proceed and log in (like it makes the request for the kerb pass...that gets canceled, and then goes on and attempts the login another way)

screenshots and logs sent to your e-mail