Important: If you are a Zammad Support or hosted customer and experience a technical issue, please refer to: support@zammad.com using your zammad-hostname / or company contract.
Used Zammad version: 2.9.x
Used Zammad installation source: package
Operating system: debian 9
Browser + version: Google Chome
Expected behavior:
Zammad is linked to our AD, some AD-Groups are also linked to Admin- and Agent-roles in Zammad.
AD sync updates Zammad users/agents/admins and metadata.
*
Actual behavior:
The AD sync occasionally kicks out users and -more annoyingly- agents for whatever reason.
Result is, that tickets are no longer assigned to the agents that got kicked out. As the sync starts regularly this is very annoying for those agents, especially when they update a ticket and cannot save at the end.
An hour later the sync “repairs” itself, otherwise a manual sync can do the same, but how to fix this?
*
Well, thanks for the hint. I don’t think this is the reason.
When I checked the history I found one strange behaviour. The user in question actually has two accounts in our AD - different names, but same meta-data (e.g. email, phone).
The log then says something like this:
vor 1 Tag 2 Stunden
aktualisierte Benutzer login von ‘user1’ bis ‘user2’
I don’t know how the user-lookup works below the curtain, but it seems as if the problem is there…
So - finally. It seems as if the problem was related to the mentioned two users having the same meta-data. Once that has been resolved, the problem disappeared.
However - I ran the script, but it generated roughly 150MB of logs…
Case can be closed (as far as I can see right now)