Description | This article describes the reason why FortiAuthenticator is not syncing with the LDAP server. |
Scope | FortiAuthenticator. |
Solution |
This issue is from the LDAP server as the bind response asks for an integrity check from the LDAP server.
Logs from FortiAuthenticator:
Failed to sync (rule: Forti_Auth_User_SYNC) with example.noc : Unable to query remote LDAP server example.noc (10.x.x.x) for users to sync (ru le Forti_Auth_User_SYNC): Idap_simple_bind_s faile d: Strong(er) authentication required 00002028: Lda pErr: DSID-0C09032F, comment: The server requires s binds to turn on integrity checking if SSL TLS are not already active on the connection, data 0, v4563
From the Packet captures on FortiAuthenticator.
Bind request:
Bind response:
Cause: A non-default security setting on the LDAP server that enforces all LDAP authentication to be secured with SSL.
If this policy is configured on the domain controller in a Windows Domain, a non-secure LDAP authentication will fail. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.