Introducing Outh suppport for jenkins-email-ext - Request for feedback

[Mohammed Faheem]

Hey everyone,

I'm Mohammed Faheem and as part of GSOC 2026, I’ll be working on adding OAuth2 SMTP authentication support to the email-ext plugin.

Currently, email-ext only supports username/password-based SMTP authentication, which is being deprecated by providers such as Microsoft and Google. The project aims to add OAuth2/XOAUTH2-based SMTP authentication support while maintaining backward compatibility.

The current plan is to integrate with the oauth-credentials framework, allowing email-ext to remain provider-agnostic and support providers such as Outlook, Gmail, and other SMTP services supporting XOAUTH2. email-ext will simply handle using the token obtained to authenticate a mail session, while separate plugins handle communicating with the providers backend and handling token acquisition/refresh flows.

I thought I'd start this discussion to gather feedback on the implementation and potential issues i might run into. particularly, I'm looking for feedback on:

-Potential edge cases or provider compatibility concerns
-Existing users who may already have workarounds for OAuth2, and possible migration strategies

If interested, I can share my proposal which dives deeper into the project and the current implementation plan.
Looking forward to working with the community on this project.

Best regards,
Mohammed Faheem

[Jesse Glick]

On Tue, May 12, 2026 at 7:04 AM Mohammed Faheem <mohdfah...@gmail.com> wrote:

The current plan is to integrate with the oauth-credentials framework

I am not familiar with the details but would suggest aligning any authentication mechanisms with those of the more basic `mailer` plugin, and looking at https://github.com/jenkinsci/mailer-plugin/pull/619 in particular.

(For greenfield setups I see no reason to run `email-ext` at all, since Pipeline logic can be used with the plain `mail` step for any desired type of templating, but it is fairly widely used in existing installations.)

CONFIDENTIALITY NOTICE: This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email.