Confirmed users
591
edits
Thunderbird:Autoconfiguration:ConfigFileFormat: Difference between revisions
Thunderbird:Autoconfiguration:ConfigFileFormat (view source)
Revision as of 03:33, 2 January 2021
, 2 January 2021→OAuth2: Stay consistent in capitalization
(Document OAuth2, status quo and where we should be, and limitations of the OAuth2 spec) |
(→OAuth2: Stay consistent in capitalization) |
||
| Line 245: | Line 245: | ||
<authentication>OAuth2</authentication> | <authentication>OAuth2</authentication> | ||
<authentication>password-cleartext</authentication> | <authentication>password-cleartext</authentication> | ||
< | <oAuth> | ||
<issuer>login.yahoo.com<issuer> | <issuer>login.yahoo.com<issuer> | ||
<scope>mail-w<scope> | <scope>mail-w<scope> | ||
<authURL>https://api.login.yahoo.com/oauth2/request_auth</authURL> | <authURL>https://api.login.yahoo.com/oauth2/request_auth</authURL> | ||
<tokenURL>https://api.login.yahoo.com/oauth2/get_token</tokenURL> | <tokenURL>https://api.login.yahoo.com/oauth2/get_token</tokenURL> | ||
< | <oAuth> | ||
</incomingServer> | </incomingServer> | ||
</pre> | </pre> | ||
Note that the `< | Note that the `<oAuth>` contents are not yet supported by Thunderbird. They are planned to be supported later, removing the need to hardcode these parameters. As of today, `<authentication>OAuth2</authentication>` is supported. | ||
Note that there are two `<authentication>` elements. This allows a fallback, in case a client does not support OAuth2 or does not have a client key for this OAuth2 issuer and therefore cannot authenticate with this issuer. | Note that there are two `<authentication>` elements. This allows a fallback, in case a client does not support OAuth2 or does not have a client key for this OAuth2 issuer and therefore cannot authenticate with this issuer. | ||