Sammenlign revisjoner
Automatic Conversion of Google mail accounts to OAuth 2.0 Authentication
Revisjon 246087:
Revisjon 246087 av denyshon den
Revisjon 250655:
Revisjon 250655 av firefox877 den
Nøkkelord:
Oppsummering av søkeresultater:
Thunderbird 91.8.0, released 5th April 2022, converts Gmail accounts to OAuth 2.0 in compliance with Google's schedule for requiring this login method.
Thunderbird 91.8.0, released 5th April 2022, converts Gmail accounts to OAuth 2.0 in compliance with Google's schedule for requiring this login method.
Innhold:
Thunderbird 91.8.0, released 5th April 2022, converts the authentication method of Gmail accounts to OAuth 2.0 to help users comply with [https://support.google.com/accounts/answer/6010255 Google's requirement of OAuth 2.0 for Gmail logins]. These changes are '''required''' by Google.
{note}We recommend updating to the latest version of Thunderbird for the latest security fixes and many other bug fixes and improvements. However, if you want to continue using an old version of Thunderbird below 91.8.0 at your own risk, you will have to change the authentication method to ''OAuth2'' yourself. You can also use the following steps to double-check that your authentication method is actually set to ''OAuth2'':
Do {button ≡} > {menu Account Settings} > {menu YourAccount} > {menu Server Settings} > {menu Authentication method} and ensure it is set to ''OAuth2''.{/note}
{warning}'''Cookies and javascript must be enabled for OAuth 2.0 to work.''' If you have rejected cookies in Thunderbird, the OAuth process will fail because some cookies must be accepted to store data between page updates. '''You need to accept cookies at least temporarily using one of the methods described below.'''{/warning}
== How to avoid or correct an OAuth failure caused by rejected cookies ==
First, verify your general setting for cookies in Thunderbird:
* Do {button ≡} > {menu Preferences} > {menu Privacy & Security} > {menu Web Content}.
* Look at the checkbox '''Accept cookies from sites'''.
If '''Accept cookies from sites''' is '''not''' checked, do one of the following and then go through the OAuth login process again:
* Create an exception to accept cookies from ''Google'':
** Click the nearby {button Exceptions…} button to open the ''Exceptions - Cookies'' dialog.
** In the ''Address of website'' input box, enter '''https://accounts.google<!---->.com'''.
** Pick {button Allow}, then {button Save Changes}.
* Alternatively, accept ''all'' cookies:
** Set the checkmark for '''Accept cookies from sites'''.
After you have gone through the OAuth process, if you prefer, you can again reject cookies, because receiving and sending mail will work with cookies rejected. But rejecting all cookies or removing the exception has the disadvantage that when the OAuth token for Gmail access expires at some date in the future, the OAuth dialog will show up and fail again until you accept the required cookies.
For greater detail about cookies, see the article [[Privacy panel - Remote content and cookie settings in Thunderbird]].
== How to avoid or correct an OAuth failure caused by disabled javascript ==
* Do {button ≡} > {menu Preferences} > {menu General} > {menu Config Editor}.
* Paste this into the ''Search preference name'' searchbox: '''javascript.allow.mailnews'''.
** If you see a search result line with '''javascript.allow.mailnews''' which contains '''false''', you must change it to '''true''' by clicking the ''Toggle'' [[Image:Fx71aboutconfig-ToggleButton]] button to the right.
** If you see a line with '''javascript.allow.mailnews''' which contains '''true''' or a {button +} button at the end of the line, then no change is needed.
== Check if the proper authentication tokens have been saved ==
* Do {button ≡} > {menu Settings} > {menu Privacy & Security} > {menu Passwords}> {menu Saved Passwords}.
** If account authentication was set to '''OAuth2''' and the OAuth login was successful, you should see entries for each username (gmail account) of the form
: '''oauth://accounts.google<span>.</span>com (https://mail.google<span>.</span>com/ …)'''
;{note}'''Note:''' The ''oauth'' entry is an OAuth2 authentication token, and not a password.{/note}
;* If account authentication was set to '''OAuth2''' and OAuth login was '''not''' successful, check your password entries for providers of the following form and delete them:
: '''imap://imap.gmail<span>.</span>com (imap://imap.gmail<span>.</span>com)'''
: '''smtp://smtp.gmail<span>.</span>com (smtp://smtp.gmail<span>.</span>com)'''
If you're still having problems, you can [https://support.mozilla.org/questions/new/thunderbird/form ask a question in Thunderbird support].
Starting from version 91.8.0, when updating from a version lower than 91.8.0, Thunderbird will convert the authentication method of Gmail accounts to OAuth 2.0 to help users comply with [https://support.google.com/accounts/answer/6010255 Google's requirement of OAuth 2.0 for Gmail logins]. These changes are '''required''' by Google.
{note}We recommend updating to the latest version of Thunderbird for the latest security fixes and many other bug fixes and improvements. However, if you want to continue using an old version of Thunderbird below 91.8.0 at your own risk, you will have to change the authentication method to ''OAuth2'' yourself. You can also use the following steps on any newer version of Thunderbird to double-check that your authentication method is actually set to ''OAuth2''.{/note}
== Ensure that your Thunderbird Gmail account is set to OAuth2 ==
=== Outgoing Server (SMTP) ===
# Do {button ≡} > {menu Account Settings}
# Select your account (e.g. {menu Jane@example.com}) from the account list on the left.
# At the bottom of the settings pane, look for {menu Outgoing Server (SMTP)}.
# Click on the {button Edit SMTP Server…} button on the right.
# In the SMTP Server dialog, ensure that {menu Authentication method} is set to ''OAuth2''.
# Click on the {button OK} button to confirm your SMTP Server settings.
=== Incoming Server ===
# Do {button ≡} > {menu Account Settings}
# Select your account (e.g. {menu Jane@example.com}) from the account list on the left.
# Underneath your account entry, select the {menu Server Settings} subsection (if it is not visible, you may need to toggle the {button >} button first).
# Ensure that {menu Security Settings} > {menu Authentication method} is set to ''OAuth2''.
{warning}'''Cookies and javascript must be enabled for the OAuth 2.0 setup process to work.''' If you have rejected cookies in Thunderbird, the OAuth setup process will fail because some cookies must be accepted to store data between page updates. '''You need to accept cookies at least temporarily using one of the methods described below.'''{/warning}
== How to avoid or correct an OAuth failure caused by rejected cookies ==
First, verify your general setting for cookies in Thunderbird:
* Do {button ≡} > {menu Preferences} > {menu Privacy & Security} > {menu Web Content}.
* Look at the checkbox '''Accept cookies from sites'''.
If '''Accept cookies from sites''' is '''not''' checked, do one of the following and then go through the OAuth login process again:
* Create an exception to accept cookies from ''Google'':
** Click the nearby {button Exceptions…} button to open the ''Exceptions - Cookies'' dialog.
** In the ''Address of website'' input box, enter '''https://accounts.google<!---->.com'''.
** Pick {button Allow}, then {button Save Changes}.
* Alternatively, accept ''all'' cookies:
** Set the checkmark for '''Accept cookies from sites'''.
After you have gone through the OAuth process, if you prefer, you can again reject cookies, because receiving and sending mail will work with cookies rejected. But rejecting all cookies or removing the exception has the disadvantage that when the OAuth token for Gmail access expires at some date in the future, the OAuth dialog will show up and fail again until you accept the required cookies.
For greater detail about cookies, see the article [[Privacy panel - Remote content and cookie settings in Thunderbird]].
== How to avoid or correct an OAuth failure caused by disabled javascript ==
# Do {button ≡} > {for not tb102}{menu Preferences}{/for}{for tb102}{menu Settings}{/for} > {menu General}
# From the bottom right corner of the '''General''' settings pane, click {button Config Editor}.
# Copy or type this into the ''Search preference name'' searchbox: '''javascript.enabled'''
# You should now see a single search result line for the setting '''javascript.enabled'''.
#* If '''javascript.enabled''' is '''true''', no change is needed.
#* If '''javascript.enabled''' is '''false''', you need to change it to '''true''' by clicking the ''Toggle'' [[Image:Fx71aboutconfig-ToggleButton]] button to the right.
== Check if the proper authentication tokens have been saved ==
* Do {button ≡} > {menu Settings} > {menu Privacy & Security} > {menu Passwords}> {menu Saved Passwords}.
** If account authentication was set to '''OAuth2''' and the OAuth login was successful, you should see entries for each username (gmail account) of the form
: '''oauth://accounts.google<span>.</span>com (https://mail.google<span>.</span>com/ …)'''
;{note}'''Note:''' The ''oauth'' entry is an OAuth2 authentication token, and not a password.{/note}
;* If account authentication was set to '''OAuth2''' and OAuth login was '''not''' successful, check your password entries for providers of the following form and delete them:
: '''imap://imap.gmail<span>.</span>com (imap://imap.gmail<span>.</span>com)'''
: '''smtp://smtp.gmail<span>.</span>com (smtp://smtp.gmail<span>.</span>com)'''
If you're still having problems, you can [https://support.mozilla.org/questions/new/thunderbird/form ask a question in Thunderbird support].