-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 7.4.15
-
Component/s: None
-
None
-
Environment:Zabbix 7.4.10 and 7.4.15
Debian 12 Bookworm
Apache 2.4
MariaDB
Issue reproduced on two independent environments:
- production server
- isolated lab server
Microsoft Entra ID application configured for SMTP OAuth.
Authorization succeeds and Microsoft returns an authorization code.
The callback reaches Zabbix successfully.Zabbix 7.4.10 and 7.4.15 Debian 12 Bookworm Apache 2.4 MariaDB Issue reproduced on two independent environments: - production server - isolated lab server Microsoft Entra ID application configured for SMTP OAuth. Authorization succeeds and Microsoft returns an authorization code. The callback reaches Zabbix successfully.
Steps to reproduce:
- 1. Create a Microsoft Entra ID application.
2. Configure SMTP OAuth media type in Zabbix.
3. Configure redirect URI:
https://<host>/oauth.authorize
4. Click "Get access token".
5. Authenticate successfully on Microsoft login page.
6. Microsoft redirects back to Zabbix.
Result:
Zabbix displays:
Cannot get authentication tokens
Invalid request
No OAuth token is stored.
Table media_type_oauth remains empty.
The callback URL is received correctly:
zabbix.php?action=oauth.authorize&code=...
Expected:
Zabbix should exchange the authorization code for access and refresh tokens and store them in media_type_oauth.
Additionnal information:
The problem is reproducible on:
- Zabbix 7.4.10
- Zabbix 7.4.15
The same Microsoft Entra configuration was tested on separate systems.
Microsoft authentication succeeds.
Authorization code is returned.The failure occurs during Zabbix token acquisition.
