-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Feature: OAuth support for Microsoft Office 365 #46
Comments
Our organisation has just implemented/enforced OAuth2 on our accounts at office365, and tbsync stopped working (asking for new password), even after I updated the main thunderbird email settings. |
I can confirm that removing and adding the account again successfully helped me switching from a password prompt to an OAuth signin, which was necessary for me after two factor authentication was enabled by my organization in Office 365. |
OAUTH2 works fine for syncing emails with Thunderbird with our Office 365 accounts. Interestingly, TbSync (version 4.1 with EAS-4-TbSync 4.1.4) needs additional access permissions. After successfully authenticating the user, an additional popup says: "Administrator permission required. To access resources in your organization, tbsync.jobisoft.de requires permission that only an administrator can grant. Ask an administrator to grant permission for this app so that you can use the app." Why is this? Is this a bug or a feature? |
TbSync has no access to your email access token and I do not think the request for the email access token included the permission to read your calendar and address books. I have no idea why you need admin permission. Your company probably blacklisted 3rd party apps. |
The latest beta supports OAuth 2.0 for O365.
https://tbsync.jobisoft.de
If you switch to beta in your current profile, TbSync should automatically switch from basic auth to OAuth and ask for your permission the next time you sync. You can also create a new Thunderbird profile and install the beta there and do not touch your working profile.
The setup wizard no longer has a passwort field and detects wether you are trying to setup an O365 account or something else. It will either pop a OAuth permission window or a standard password prompt.
That does make the setup for non O365 accounts a bit more ugly I think, but I have no idea how to make the wizard nicer. I should not ask for a password, if OAuth is possible, but I only learn that during discovering.
This should also work with multi factor authorization (MFA)
Feedback is welcome.
The text was updated successfully, but these errors were encountered: