Closed Bug 1573212 Opened 6 years ago Closed 6 years ago

Thunderbird does not support two-factor authentication for a particular provider

Categories

(Thunderbird :: Security, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: pfrank, Unassigned)

Details

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

Actual results:

No support for two-factor authentication. Logins fail.

Which provider? (I'm trying to match the terseness of your report).

Ben, can you continue here.

Flags: needinfo?(benjamin)

Following up - I work at Stanford. They've instituted two-factor authentication for email logins.

I don't know what you mean by "provider." Thunderbird is 60.8.0 (32-bit).

Provider, as in mail provider. Looks like "Stanford" is your provider with whatever 2FA scheme they implemented.

Usually we add oauth2 specific to the provider, for example Yandex in bug 1559972, mail.ru in bug 1231642 or Yahoo in bug 1293958. Office 365 is still in discussion, bug 1528136 (good reading from bug 1528136 comment #15 downwards).

Do you have any details about the 2FA scheme used at Stanford?

Flags: needinfo?(benjamin)
Summary: Thunderbird does not support two-factor authentication and is suddenly useless → Thunderbird does not support two-factor authentication for a particular provider

I don't think there's anything we can improve here.

According to their website Stanford uses DUO and O365 and gsuite access https://uit.stanford.edu/emailcalendar/config#googleapps In the gsuite world you would ideally have a google generated passphrase (NOT the login account password) to use for gmail imap. DUO 2fa typically doesn't enter the picture. The details regarding imap are at https://uit.stanford.edu/service/googleapps/emailcalendar/desktop/thunderbird_imap

You should consult your campus IT staff

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Component: Untriaged → Security
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.