SCIM API Integration with Azure AD – Error 500

[yotsawin]

I am currently configuring SCIM user provisioning for Zabbix version 7.2, following the official documentation

https://www.zabbix.com/documentation/current/en/manual/appendix/install/azure_ad

After completing the configuration and testing the Test Connection from Azure AD, I encountered the following error:






The requested endpoint is not supported. (HTTP 400 Internal Server Error)

• Configured Azure AD SCIM provisioning as per Zabbix documentation.
• Enabled SCIM API in Zabbix UI (Administration → Authentication).
• Generated a SCIM API Token with Super Admin privileges.
• Configured Nginx to allow api_scim.php.
• Checked file permissions for /usr/share/zabbix/ui/api_scim.php

Manually tested SCIM API endpoints

curl -X GET "https://domain/api_scim.php/ServiceProviderConfig" \ -H "Authorization: Bearer <API_TOKEN>" \ -H "Accept: application/json"
Result: 500 Internal Server Error

{"schemas":["urn:ietfarams:scim:api:messages:2.0:Error"],"detail":"The requested endpoint is not supported.","status":500}

Could you please provide insights into:

1. Is SCIM API fully supported in Zabbix 7.2?
2. Are there additional requirements or patches needed for SCIM provisioning?
3. How to debug SCIM API further to identify why it fails with HTTP 500?
4. Are there specific PHP or database requirements that might affect SCIM API functionality?

Any guidance on resolving this issue would be greatly appreciated.
Question

• Is there an official way to test whether api_scim.php is properly enabled?
• Are there specific API endpoints that should return a valid response when tested via cURL or Postman?
• Are there additional configurations required for api_scim.php to function correctly?

Any guidance on how to verify that SCIM API is active and working would be greatly appreciated.

[gablesm]

I too ran into this issue. check your log files (/var/log/nginx/zabbix_access.log and grep for scim). My instance was throwing a 400 error when called from Entra, yet 500 when you call it from a web browser to test.

I was able to fix it by modifying the standard zabbix_ssl.conf file and adding the following:

 fastcgi_param   PATH_INFO       $fastcgi_path_info;