LDAP connector not functioning after upgrade — no logs, users can't authenticate

[FASupportBot]

After upgrading FusionAuth to 1.69.2, the LDAP connector and reconcile lambda stopped working entirely. Users cannot authenticate unless they have a local FusionAuth account, and no LDAP-related activity appears in the event log — no reconcile attempts, no communication with the LDAP server.

Debug mode is enabled for both the connector and the lambda, but still no log entries are generated when users attempt to log in. It appears FusionAuth is not honoring or applying the connector configuration at all.

The issue was temporarily resolved by deleting and recreating the LDAP connector, but the root cause was unclear at the time.

[FASupportBot]

This issue was caused by a bug that existed prior to version 1.68.0. In earlier versions, there was a problem where LDAP connectors scoped to specific domains could incorrectly be called (or not called) for users outside those domains. This could result in the connector appearing to stop functioning entirely after an upgrade.

Solution:

Recreate the LDAP connector configuration. When doing so, verify the Domains field:

• If you need the connector to apply to all users, use a wildcard (*) for the domains.
• If you need domain-specific scoping, explicitly configure the same domains you had previously.

This bug was fixed in FusionAuth 1.68.0. See the release notes for details:

Fixed an issue where Connectors configured for a specific domain in a Tenant could be called for users outside of that domain.

If you encounter this issue after upgrading to 1.68.0 or later and recreating the connector does not resolve it, verify:

1. Debug mode is enabled for both the connector and the reconcile lambda.
2. The LDAP server is reachable from the FusionAuth instance.
3. Event log and system log (fusionauth-app.log) for any connection or authentication errors.