Confirmed users
596
edits
Thunderbird:Autoconfiguration:ConfigFileFormat: Difference between revisions
Jump to navigation
Jump to search
Thunderbird:Autoconfiguration:ConfigFileFormat (view source)
Revision as of 12:23, 29 June 2024
, 29 June 2024→OAuth2: Thunderbird implementation notes
(Re-add implementation note that Thunderbird uses RFC 6764 for CardDAV/CalDAV auto discovery) |
(→OAuth2: Thunderbird implementation notes) |
||
| Line 289: | Line 289: | ||
</pre> | </pre> | ||
Implementation note: While Thunderbird supports `<authentication>OAuth2</authentication>`, it does not support the `<oAuth2>` contents (server URL etc). | |||
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 within the `<incomingServer>`. 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. | ||
Scope: If we set up email, address book, calendar, and webdav, we do *not* want the user go have to go through 4 authentication processes. Yet, a provider might use different scopes for email and calendar, and that is in line with the OAuth2 spec. The solution is to combine several scopes, using [https://tools.ietf.org/html/rfc6749#section-3.3 spaces as separator], in a single auth request. [https://stackoverflow.com/questions/8449544/multiple-scope-values-to-oauth2/51437063#51437063 The order is important]. That's why we deliberately do not make the scope specific to a service or server, but to the entire configuration. We don't want the user to have to authenticate several times in a row. This is a requirement from the end user. | Scope: If we set up email, address book, calendar, and webdav, we do *not* want the user go have to go through 4 authentication processes. Yet, a provider might use different scopes for email and calendar, and that is in line with the OAuth2 spec. The solution is to combine several scopes, using [https://tools.ietf.org/html/rfc6749#section-3.3 spaces as separator], in a single auth request. [https://stackoverflow.com/questions/8449544/multiple-scope-values-to-oauth2/51437063#51437063 The order is important]. That's why we deliberately do not make the scope specific to a service or server, but to the entire configuration. We don't want the user to have to authenticate several times in a row. This is a requirement from the end user. | ||