Currently the directory connect using filters (for example user filters) will overwrite each other, which in my opinion cant be intended.
What i mean is, if i set an “includeGroup” filter for the “User Filter” and configure it to a specific group, i would expect and “exclude” or and “excludeGroup” filter to be applied on top of that “includeGroup” filter, but thats not the case. The “excludeGroup” filter will basically overwrite the “includeGroup” filter and will include all users EXCEPT for the ones in the specified group. This then continues with more filters, where one overwrites the other.
In my opinion this should be changed so an exclude will not overwrite an include but will work on top of it or there should be some logic (either a toggle or some syntax in the filter input field) to properly manage how those filters are applied
Perhaps it has to do with this axiom: “A bug is something that does not work as the developer intended; a feature request is something that does not work as the user intended”.
You are talking about the level of groups here only, right?
I must say, I’m not familiar with Directory Connector myself, but let’s say we have groups A-Z:
When you include groups A-C, then that already and automatically excludes groups D-Z.
When you exclude groups A-C, then that already and automatically includes groups D-Z.
Right?
In both approaches, you are effectively doing the same thing, just either defining what you include (and what therefore automatically is excluded) or what you exclude (and therefore what automatically is included).
I think I don’t really understand – logically – what you would even accomplish with an additional exclude or include rule? (I hope you don’t want to include and exclude any group at the same time?!?)
PS: From similar contexts: it’s usually only the question which of the two is easier to define – what you want to include or what you want to exclude. Therefore the two options. But if you see it, please explain the benefit of using both options at the same time.