Replies: 1 comment
|
Things I checked / Additional context: Without enrollment: Login to web UI fails with "not in LDAP sync groups" (see above) This creates a confusing and broken flow: If enrollment is required before LDAP login works → enrollment should NOT ask for a new password but use AD credentials instead Expected flow for LDAP users: Admin syncs users from AD via LDAP Is enrollment even required for LDAP users? |
Uh oh!
There was an error while loading. Please reload this page.
Environment:
Defguard version: 2.0.2
LDAP server: Synology Directory Server (Samba-based Active Directory)
Deployment: Docker on Synology NAS
Description:
LDAP authentication fails at login even though the user is a member of the configured sync group. The LDAP bind test succeeds but the group membership check fails.
Logs:
LDAP bind test for user CN=testuser,CN=Users,DC=lab,DC=local successful
User testuser is not in LDAP sync groups, not allowing to login through LDAP.
LDAP Config:
LDAP server is Active Directory: ✅
Username attribute: sAMAccountName
Member attribute: memberOf
Group member attribute: member
Limit sync to groups: Defguard
Verified:
member attribute of group contains correct DNs
memberOf on user object contains CN=Defguard,CN=Users,DC=lab,DC=local
LDAP bind succeeds
Group sync filter generates wrong query: (&(objectClass=group)(cn=DC=local)) instead of (&(objectClass=group)(cn=Defguard))
Suspected bug: Group name parsing issue - when full DN is entered it parses incorrectly, when only CN is entered the group membership check still fails at login.
Can anyone help me, with my problem?
All reactions