Difficult without debugging and any error in the console.
So the situation is that you can select some roles, but it’s not present in the request or? Did you already test if it’s the same inside a private session, to avoid client caching problems?
Maybe you can show some screenshots when this is possible?
@cgarling please give our colleagues time. This is a free community without and guarantees. If you require urgent support, consider having a support contract.
I understand that this is a free community and that we are not entitled to support.
However, it is also the case that we are currently evaluating the replacement of our existing OTRS and Zammad is basically very interesting for this. But we also want to know exactly whether the product is suitable for us before we spend money on it. Unfortunately, the current problems are preventing these tests.
Maybe in the meanwhile one additional question. Did you already test it with another LDAP server? Is it the same problem? Or also with an new installation of Zammad?
we use our central ActiveDirectory for the LDAP connection. We therefore do not have another comparable system at our disposal. However, we run a whole range of applications which all work together with it without any problems.
We had already tried a new installation, but with the same result.
Hi there
Same issue here, although running another Zammad version (5.4.1).
I found a workaround for this. You can define the mappings in the Zammad Rails Console like this:
Open console with zammad run rails c
# First get a list of role id/name
Role.order(:id).pluck(:id, :name)
Adjust the LDAP configuration with
# Load config
l = LdapSource.first
# List current group role mapping (should be empty now)
l.preferences["group_role_map"]
# Configure the mapping (adjust group dn and role id to your needs)
l.preferences["group_role_map"] = { "cn=groupname,ou=groups,dc=..." => ["3"] }
# Save configuration
l.save
You can define as many group <> role maps as you need.
Hope this helps until the editing in the GUI is fixed.
