Closed Bug 1738330 Opened 4 years ago Closed 4 years ago

Can't create new oauth2 account Mac Catalina

Categories

(Thunderbird :: Account Manager, defect)

Thunderbird 91
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: essin, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:93.0) Gecko/20100101 Firefox/93.0

Steps to reproduce:

1 - chose add new account for service that requires oauth2 - i.e. institutional office365)
2 - entered user name
3 - no point in entering password since oauth2 (thunderbird on other platforms) presents the organizations login screen.
4 - chose configure manually
5 - entered server names and ports (outlook.office365.com:993, smtp.office365.com:587)
6 - click re-test
7 - Correctly sets imap auth method to oauth2 - but - does NOT set auth method for smtp to oauth2.
8 - Never gets organizational login screen
9 - Finish button is never enabled

Actual results:

This has worked on windows and fedora with thunderbird 91.
Create new account with settings as above
Organizational login screen appears
Log in successful
Returns to thunderbird
Click create
Retrieval of email begins

Reviewing other oauth2 bug reports over the last 7 years hints that problems related to this have been around for a while but never addressed.

Expected results:

Create new account with settings as above
Organizational login screen appears
Log in successful
Returns to thunderbird
Click create
Retrieval of email begins

Bug 1622181?

I'm not sure what you're reporting. Assumption #3 is wrong, you should enter the password so that thunderbird can use it - since it's still needed to autodiscover your settings! Then there should be no need configuring manually either....

Daniel?

(In reply to Magnus Melin [:mkmelin] from comment #1)

Bug 1622181?

I'm not sure what you're reporting. Assumption #3 is wrong, you should enter the password so that thunderbird can use it - since it's still needed to autodiscover your settings! Then there should be no need configuring manually either....

Flags: needinfo?(essin)

This doesn't seem right. This is the setup. My email account is with USC. They have an enterprise subscription to Office365.
The login process goes like this if I use the Web mail:

  • I go to https://usc.edu/office365
  • USC displays their organizational login page which does NOT use my email address as the login name, It only uses the username.
  • After entering my user id and USC password, USC then calls DUO.
  • Duo pushes a message to my phone and apple watch (or a voice phone call) to authenticate.
  • Then USC sends an OK message to MS that then displays a dialog where I tell it not to show the dialog next time (but it always does anyway).
  • Then I get into the mail.

So tell me again, which user id and password you think I should enter into the TB screen and how and where do you expect that to be used?

By the way, when it probes the server for settings, it never gets the correct imap or smtp server addresses and it does not get the correct port number for imap and I have to do all of this manually anyway.

Would it not just be simpler to give me oauth2 as a choice as I enter the server addresses and port numbers manually and skip the part about the code trying to guess (unsuccessfully) what to do next?

Flags: needinfo?(essin)

So tell me again, which user id and password you think I should enter into the TB screen and how and where do you expect that to be used?

If you enter a password and it's the wrong one, you will get a message on the screen telling you about this situation, and also an additional field will appear ("Your login") where you can enter the separate user id.

I’ll have to try it again but I don’t recollect seeing the messages and prompts that you describe.

Did you try again? What was the result?

(In reply to Magnus Melin [:mkmelin] from comment #6)

Did you try again? What was the result?

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.