Error when trying to log into Wildfire jabber server (1.2.5)

[cross]

Adium 1.2.4 has no trouble allowing me to log into either my jabber.org account, or my account on my corporate jabber server (Wildfire 2.5.1). With adium 1.2.5, I can't log into either of them. I do *not* have my passwords saved and expect to be prompted for them. The problem with my jabber.org account was fixed by the 1.3prerelease mentioned in bug #9748. However, using either 1.2.5 or 1.3svn20080502 still fails to log into my account on the wildfire server. The error in the preference Account tab is "Error: Invalid challenge from server".

The segment of the debug output from when I tried to log into that account with 1.3svn20080502 is attached.

[cross]

Segment of debug window contents that occurred during attempted login

[Catfish_Man]

Wildfire 2.5.1 is pretty ancient... lots of bugs fixed since then, including at least one that fixed some Adium login issues. (I work for Jive, the company that makes Wildfire, now known as Openfire).

[evands]

It's failing authorization with DIGEST-MD5 because no password is sent and your account does require a password. It then tries the next mech, CRAM-MD5. I think that having tried DIGEST-MD5 and failed, our [source:trunk/Utilities/dep-build-scripts/libpurple_jabber_use_builtin_digestmd5.diff libpurple_jabber_use_builtin_digestmd5.diff] patch applied to libpurple causes all subsequent mechs to fail bizarrely now. That patch was applied to work around an ancient Wildfire bug, IIRC, and shouldn't be needed now that we can fall back to PLAIN as necessary.

[cross]

Okay, cool. Perhaps the subsequent mechs fail because you throw out the SASL object? Or, does that get constructed with each pass through the code path? Anyway, glad you have an idea what's up, and I look forward to seeing a fix/adjustment. Thanks.

[evands]

It gets remade, but the auth type actually gets set to DIGEST-MD5 rather than SASL and stays there, so attempts on any other mech incorrectly go through the custom DIGEST code path.

[evands]

Please try  Adium_1.3svn20080507 which should hopefully fix this problem.

[cross]

Thanks. Not near a Mac at the moment, but I'll give it a try tonight. I should have that answer for you by 02:00 GMT.

[cross]

Didn't get to it until this morning, but it does in fact fix the problem. Thanks much!

[evands]

Excellent. You're welcome! :)