Open Bug 1594316 Opened 3 years ago Updated 3 years ago

Authentication towards XMPP server fails

Categories

(Chat Core :: XMPP, defect)

defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: rabbe, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Upgrade Thunderbird from 60.9.0 to 68.2.0, on 64-bit Windows 10.

Actual results:

Authentication no longer works towards my XMPP server. Workaround: Uninstall and reinstall 60.9.0.

When trying the different Thunderbird versions no changes were made to personal configuration data, except that the password was re-entered a number of times.

Expected results:

Successful authentication.

If you click "Show Accounts", then right click on the account that is failing to connect there should be an option to "Copy Debug Log". This should have information that will help understand what's happening here. (This might contain some sensitive information, I'm mostly curious in the negotiation between which SASL mechanisms are available / is getting used.)

What XMPP server are you attempting to connect to?

What do you mean that the password had to be re-entered many times?

We did have to fix something with authentication in bug 1527480, so maybe something in there breaks in a particular case.

Component: Instant Messaging → XMPP
Product: Thunderbird → Chat Core
Attached file Debug log
I don't know the details of the server. I hope the log can give some info though.

I re-entered the password because I has been through a corporate password change just recently, so at first I thought it was a password issue.

Below is the log; I replaced a certain real domain name with 'some.where.net':

I don't know the details of the server. I hope the log can give some info though.

I re-entered the password because I has been through a corporate password change just recently, so at first I thought it was a password issue.

The log is attached; I replaced a certain real domain name with 'some.where.net':

You need to log in before you can comment on or make changes to this bug.