Closed Bug 1330049 Opened 7 years ago Closed 5 years ago

Add OAuth2 support for outlook/office365.com

Categories

(Thunderbird :: Account Manager, enhancement)

45 Branch
Unspecified
All
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1528136

People

(Reporter: disasterlistmanager, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161208153507

Steps to reproduce:

Changed my office365.com imap account Authentication method to OAuth2, since both outlook/office365.com support it


Actual results:

Doesn't work


Expected results:

It should work
I read in another bug that support had to be added on a per server basis.

I'm curious, why is this? Why can't generic OAuth2 support be added, then just deal with problematic servers in one-off bugs?
See Bug 1231642.  And ask an outlook tech to do the required work.
(In reply to alta88 from comment #2)
> See Bug 1231642.  And ask an outlook tech to do the required work.

precisely
Blocks: 1310389
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → All
now I have two votes on this tracker for 7 years :)

Does this help:

https://sourceforge.net/p/davmail/mailman/message/36440669/

DavMail is an opensource app By Mickaël Guessant

Can his code be recycled in TB if he consents ?

There's this configurable bit either as text or GUI fields:

davmail.oauth.clientId=12345678-1234-5678-9abc-123456789abc
davmail.oauth.redirectUri=https://login.microsoftonline.com/common/oauth2/nativeclient

How does this enhancement request relate to:

https://bugzilla.mozilla.org/show_bug.cgi?id=1528136

They look the same to me.

This one is older, but the other one has more useful comments, so I'll mark this a DUP.

No longer blocks: 1310389
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE

Ok, I'll bite...

Are you saying that OAUTH2 is the same thing as 2FA?

As far as I know, they are completely different - but maybe if this one is fixed, it will also provide OAUTH2 support?

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