OTRS 5: LDAP Auth behaves strange after Update from version 4

[fwtag]

Hi there,

after updating to OTRS 5.0.1 (coming from one of the latest versions 4), the LDAP auth behaves strange and inconsistently: Randomly, the Agent-Group association, which is provided by our LDAP and which worked just fine in version 4, gets lost and re-appears. In other words: When a user logs into the system, he might be associated to no group anymore and hence, does not see or is allowed to access any Queue. When logging out and re-login, the association might be restored. The one like the other effect does occur very often, but there seems not to be a pattern (like odd logins: lost; even logins: re-established).

The setup follows this guide:
https://otrs.github.io/doc/manual/admin ... kends.html

Additionally, the AuthSync module is set up and configured with LDAP-/OTRS group mapping.

The whole setup is identical to the one which worked well with OTRS 4.

Interestingly, the problems seem to appear not in combination with RO group access ... but this might be a coincidence.

Maybe, I missed some update stuff ..?

I appreciate your help ... thanks!


Frank

[uoladm]

Hi,
we upgraded OTRS to version 5.0.1 last week as well and it behaves the same way as Frank described in previous post.
Very frequently, users and groups, provided by our LDAP, can't access any Queue. Re-logging helps, sometimes, but on next login, queues mostly disappears again.
It's very annoying and we have no clue if it's problem on our side or not.

Thanks for your help,
Andrew

[crythias]

This subforum is not for support, btw. If you think feel this is a bug, please report it on the official bug tracker.