OAUTH2 (EntraAD) and Security
-
In addition to the well-known 422 error, which is expected to be resolved in the coming weeks, I have another concern regarding the security of our Microsoft tenant.
By September 2025, we are required to disable or modify SMTP authentication on our web servers and transition to using OAuth2. However, I foresee potential issues with our tenant’s security because the API permissions appear to be excessively broad. Specifically, the “Mail.Send – Send mail as any user” permission must be granted, even though the plugin is only intended to send emails from a single address.
Additionally, this plugin (as well as WP Mail SMTP) requests read permissions for all mailboxes, which I find unacceptable as it poses a significant security risk.
How are you addressing this issue?
The API permissions in EntraID (formerly Azure AD) are not sufficiently granular, making them less effective for adequately protecting the tenant.
- You must be logged in to reply to this topic.