Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
LDAP - User Password #1169
I have successfully set up the LDAP connection. Everything works fine - great job!
Why is there the function "Password", if actually the passwords are administered via the LDAP connection?
Currently Zammad checks multiple authentication backends including the local DB and LDAP if configured. The first check is the local DB so if the user changes or sets a local password it will work. If the entered password is wrong the LDAP will get checked, too.
If I get you right you wan't to disable the possibility to set a local PW in Zammad completely for LDAP users?
PS: Nice avatar
+1 for disabling the local password when a user is synced via LDAP! :-)
But: If a user drops out of the LDAP database there should be a "way back" to local auth. I.e. I'm using Zammad for a sports club - the trainers etc. are agents and maintained via LDAP, because they can write articles on the website, have access to a cloud service and Zammad. But if a guy drops the job he returns to a normal member and is not in LDAP anymore, so in this scenario he'll drop back to a customer in Zammad and should be able to use the local auth again.
Hey. We would also like to have the option to disable password changes completely. For now we use a hacky workaround which disables the 3 password fields in the profile via CSS (not really disabled when someone knows how to reenable them, but good enough for us):
Not a nice workaround though, but it helps until a real disable function is implemented.