[
https://issues.apache.org/jira/browse/EMAIL-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895919#comment-17895919
]
Manuel K edited comment on EMAIL-163 at 11/6/24 9:58 AM:
---------------------------------------------------------
[~sgoeschl] Yeah definitely! We have access to a M365 tenant where we can use
the SMTP server to test. Authenticating to Microsoft and retrieving the access
token is something the user of the library/we would have to implement though,
is that correct (not a problem, just asking for better understanding). Thank
you very much in advance!
was (Author: JIRAUSER299045):
[~sgoeschl] Yeah definitely! We have access to a M365 tenant where we can use
the SMTP server to test. Authenticating to Microsoft and retrieving the access
token is something the user of the library/we would have to implement though,
is that correct (not a problem, just asking for better understanding).
> Support for OAuth2 authentication
> ---------------------------------
>
> Key: EMAIL-163
> URL: https://issues.apache.org/jira/browse/EMAIL-163
> Project: Commons Email
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Guillaume Grossetie
> Assignee: Siegfried Goeschl
> Priority: Major
> Labels: OAuth2
>
> {quote}
> Starting with JavaMail 1.5.5, support for OAuth2 authentication is built-in
> and no longer requires SASL (although the SASL OAuth2 support continues to
> work).
> {quote}
> https://java.net/projects/javamail/pages/OAuth2
> It would be great if commons email could provide an API to support OAuth2
> authentification.
> The following code should be integrated in {{Email.getMailSession}}:
> {code}
> if (isOAuth2Authentication()) {
> props.put("mail.smtp.auth.mechanisms", "XOAUTH2");
> }
> {code}
> Or a generic solution:
> {code}
> if (this.authMechanisms != null) {
> props.put("mail.smtp.auth.mechanisms", this.authMechanisms);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
