Jenkins email notifications using Outlook SMTP with OAuth

As major email service providers, including Microsoft Outlook, transition away from legacy username/password authentication in favor of more secure protocols, existing CI/CD notification workflows must adapt to maintain functionality. This project proposes enhancing the Jenkins Email Extension (email-ext) plugin by implementing OAuth authentication support for Outlook SMTP, specifically leveraging the client credentials flow.

The implementation will focus on the secure storage and management of OAuth tokens within the Jenkins credential store, alongside the development of intuitive UI configuration options to streamline the setup process for administrators. By moving beyond traditional SMTP AUTH, this project ensures reliable, future-proofed email delivery that aligns with modern security standards. Key deliverables include a robust authentication backend, comprehensive integration testing to guarantee delivery reliability, and detailed documentation to guide the community through the transition to OAuth-based notifications.

The transition from legacy Basic Authentication (username/password) to OAuth-based flows is no longer a luxury—it is a security mandate. As major providers like Microsoft Outlook enforce the deprecation of SMTP AUTH, the Jenkins email-ext plugin risks becoming obsolete for a significant portion of its user base. This project is essential to ensure that critical CI/CD feedback loops remain functional and secure. By implementing OAuth support, we not only future-proof Jenkins email notifications but also enhance security by eliminating the need for storing sensitive credentials. This project will empower Jenkins users to maintain seamless communication with their teams while adhering to modern authentication standards, ultimately contributing to the resilience and longevity of the Jenkins ecosystem.

Medium - 175 hours over 12 weeks