[#47657] - [6.1] Backport SMTP OAuth2 mailer support in Global Configuration
- Closed
- 7 Aug 2026
- Medium
- Build: 6.1-dev
- # 47657
- Diff
- dawe78:feature/oauth2-mail-6.1
User tests: Successful: Unsuccessful:
Backport request
This is a backport of #47656 #47669 to 6.1-dev.
Why backport
SMTP OAuth2 support is needed in production environments where basic auth is disabled.
Backporting allows earlier adoption without waiting for the next minor stream.
Scope
Same functional scope as #47656 #47669:
smtpoauth2mailer option- OAuth2 token flow in Global Configuration
- Microsoft/Google/Custom provider handling
- Microsoft tenant mode (common vs specific tenant)
- SMTP XOAUTH2 integration in MailerFactory
Risk/compatibility
- Changes are additive around mail transport configuration.
- Existing non-OAuth mailer paths (
mail,sendmail,smtp) remain intact.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_config Language & Strings Libraries |
As far as I see it, we could remove the refrence to a specific provider and still keep the functionality. We try to keep the cms out of a vendor relation. Do you think that would be an option?
For sure we could; I just wanted to keep config as simple as it could be, so I pre-configured google and microsoft for an easy implementation. Should I remove it or can we keep it to make config more easy?
| Labels |
Added:
Language Change
PR-6.1-dev
|
||
We have decided as a team not to include this PR as a backport in 6.1.
Thank you very much for your commitment.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-08-07 13:10:22 |
| Closed_By | ⇒ | tecpromotion |
Looks good to me. Just one thing because I know this will be a discussion. As far as I see it, we could remove the refrence to a specific provider and still keep the functionality. We try to keep the cms out of a vendor relation. Do you think that would be an option?