On Tue, 16 Jul 2024, Sidsel Jensen via mailop wrote:
Hi Andreas
We have some documentation here:
https://documentation.open-xchange.com/8/middleware/mail/dovecot/oauth_2.0_with_postfix_and_dovecot.html
but a good HowTo sounds like a really good idea, to further the
adoption. If you need help let me know :)
To answer Scott in terms of the wider discussion, there are some
things in motion currently.
I know that
https://datatracker.ietf.org/doc/draft-jenkins-oauth-public/ is to
be discussed at the next IETF meeting in Canada.
There is also work ongoing regarding
https://datatracker.ietf.org/doc/draft-bucksch-autoconfig/
Am 10.07.24 um 04:07 schrieb Scott Q. via mailop:
What exactly is missing for broad acceptance ?
https://openid.net/specs/openid-connect-discovery-1_0.html defines
some pretty clear ways to autodiscover the endpoints.
MS & Google and Keycloak both offer this URL:
https://login.microsoftonline.com/domain.com/.well-known/openid-configuration
https://accounts.google.com/.well-known/openid-configuration
For someone new to all of these, but interested in how they might be
added to non-app linux clients such as alpine and fetchmail,
where do these offerings fit together, overlap, agree and disagree ?
If you can - please create feature requests for those clients - that
could be a good starting point to let the companies know that there
is in fact customer demand for this.
I will put in a request to the alpine mailing list, once I understand which
of these I should be asking for.
--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
