|
|
| Line 247: |
Line 247: |
| </incomingServer> | | </incomingServer> |
| </emailProvider> | | </emailProvider> |
|
| |
| <oAuth2>
| |
| <issuer>login.yahoo.com</issuer>
| |
| <scope>mail-w</scope>
| |
| <authURL>https://api.login.yahoo.com/oauth2/request_auth</authURL>
| |
| <tokenURL>https://api.login.yahoo.com/oauth2/get_token</tokenURL>
| |
| </oAuth2>
| |
| </pre> | | </pre> |
|
| |
| Note that the `<oAuth2>` 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. |
|
| |
| 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.
| |
|
| |
|
| = TODO = | | = TODO = |