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 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/4da5e042-4ba2-4233-b2ad-65f45469ab0cn%40googlegroups.com.
