Used Zammad version: 2.9
Used Zammad installation source: apt package
Operating system: Ubuntu 18.04 LTS
Browser + version: Chrome
Hello,
iam using the LDAP Sync to assign Groups from our Active Directory to Roles. This works fine but now all our Departments should work with Zammad and now i got a lot of more AD Groups with a lot of more Users.
I created in our AD for Zammad Agent Groups and now i assigned our Department AD Groups to the Zammad Groups. So that a Group is Member of the Zammad Group.
But now the users won’t be assigned. Only if i assign Users directly to the Zammad Group the sync works.
Is it possible to assign a group to a group and the sync will work?
1 Like
dvnkln
April 18, 2019, 6:06am
2
Hey @anon43131755 ,
they probably need to “fix” the ldap integration for this.
Most basic ldap integrations use the syntax to look for direct memberships per default.
But there are multiple ways for nested groups to work via ldap.
I guess this should be a FR instead of technical assistance (since you’re basically doing nothing wrong on a technical level).
Totally IMHO btw - could be wrong.
cheers
2 Likes
Ok thank you very much for this Information!
Maybe a Mod can move this Topic to the FR Section
We currently don’t support nested groups and have a enhancement request on this:
opened 04:49PM - 19 Sep 18 UTC
enhancement
verified
prioritised by payment
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 2.6.x
* Installation method (source, package, ..): rpm
* Operating system: n/a
* Database + version: postgresql
* Elasticsearch version: elasticsearch 5.6.11
* Browser + version: n/a
* Ticket-ID: #1026024
### Expected behavior:
* When assigning roles to groups that contain sub groups for easier user administration, zammad shouldn't just sync those users, but also assign the depending role of its parent group.
### Actual behavior:
* Zammad ignores sub groups in groups while assigning roles to groups.
### Steps to reproduce the behavior:
! Following doesn't matter if it's an Active Directory or normal LDAP !
* On AD / LDAP, create a parent group
* Assign one or more sub groups to this group
* assign users to the sub group
* Add LDAP-Integration to Zammad and configure the parent group to assign the agent role (as example)
* wait for the synchronization to start & finish and check if the new users have agent rights (they will not)
Yes I'm sure this is a bug and no feature request or a general question.
**Important note for dev**
I have a running test system on my private servers. Write me and you'll get access to a running enviorement! You can test it until it breaks, doesn't matter. I'll gladly assist here!
2 Likes
Thank you for the information I will follow the progress on github!
1 Like
system
Closed
August 23, 2019, 4:28am
6
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.
Zammad 5.2 introduced Multi LDAP support.
See New Release: Zammad 5.2