Adium

Opened 12 years ago

Closed 12 years ago

#9801 closed defect (fixed)

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

Reported by: cross Owned by: evands
Milestone: Adium 1.3 Component: Adium Core
Version: Severity: normal
Keywords: wildfire jabber Cc:
Patch Status:

Description

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.

Attachments (1)

adium1.3b.log (8.1 KB) - added by Chris Ross 12 years ago.
Segment of debug window contents that occurred during attempted login

Download all attachments as: .zip

Change History (9)

Changed 12 years ago by Chris Ross

Attachment: adium1.3b.log added

Segment of debug window contents that occurred during attempted login

comment:1 Changed 12 years ago by David Smith

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).

comment:2 Changed 12 years ago by Evan Schoenberg

Owner: changed from nobody to Evan Schoenberg
Status: newassigned

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.

comment:3 Changed 12 years ago by Chris Ross

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.

comment:4 Changed 12 years ago by Evan Schoenberg

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.

comment:5 Changed 12 years ago by Evan Schoenberg

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

comment:6 Changed 12 years ago by Chris Ross

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.

comment:7 Changed 12 years ago by Chris Ross

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

comment:8 Changed 12 years ago by Evan Schoenberg

Milestone: Adium X 1.3
Resolution: fixed
Status: assignedclosed

Excellent. You're welcome! :)

Note: See TracTickets for help on using tickets.