Thunderbird:Autoconfiguration:ConfigFileFormat: Difference between revisions

Jump to navigation Jump to search
→‎OAuth2: OAuth2Providers.jsm -> OAuth2Providers.sys.mjs
(remove never supported addressbook, calendar, filelink specific fields. RFC 6764 should be used instead)
(→‎OAuth2: OAuth2Providers.jsm -> OAuth2Providers.sys.mjs)
Line 233: Line 233:
= OAuth2 =
= OAuth2 =


Due to a defficiency in the OAuth2 spec, the client is usually required to send a client credential key, which in turn requires the client to be registered and approved by the email provider. Unfortunately, this not only allows email providers to block specific email clients (which is contrary to the idea of Open-Source), but also makes it impossible to support arbitrary OAuth2 servers. That's why Thunderbird is forced to hardcode the servers that it supports and the respecive client keys. That means that you cannot use OAuth2 for your own server. Only the servers listed on [https://searchfox.org/comm-central/source/mailnews/base/src/OAuth2Providers.jsm OAuth2Providers.jsm] will work.
Due to a deficiency in the OAuth2 spec, the client is usually required to send a client credential key, which in turn requires the client to be registered and approved by the email provider. Unfortunately, this not only allows email providers to block specific email clients (which is contrary to the idea of Open-Source), but also makes it impossible to support arbitrary OAuth2 servers. That's why Thunderbird is forced to hardcode the servers that it supports and the respective client keys. That means that you cannot use OAuth2 for your own server. Only the servers listed on [https://searchfox.org/comm-central/source/mailnews/base/src/OAuth2Providers.sys.mjs OAuth2Providers.sys.mjs] will work.


A server using OAuth2 auth looks this:
A server using OAuth2 auth looks this:
137

edits

Navigation menu