AD nested groups not working

Mgr_Peter_Tuharsky_M 2019-07-02 13:11:53 UTC #1

Hi,
please, what is the status of nested groups now? I’ve seen an archive article from 2005-6 and it seemed that the problem has been solved long ago with 1.2 branch. But it does not seem to work for us with AD backend.

RalfBecker 2019-07-02 20:27:15 UTC #2

Hi Peter,

nested groups are not supported (and never were before).

I like the concept and might add it sometime, if I find the time.

Ralf

Mgr_Peter_Tuharsky_M 2019-07-03 05:46:26 UTC #3

Thank You, Ralf, for quick answer. It would help us to somehow cope with it.

For record and maybe Your better access to the material, this was the article and patch:

Mgr_Peter_Tuharsky_M 2019-07-03 06:04:32 UTC #4

Ralf, is there something that we could do to help apply the nested groups? My colegue has some PHP experience.
But I understand that group membership is a core functionality that has potential to break things, so You may need to plan a proper capacity to this and it is not probably a priority now…

RalfBecker 2019-07-03 06:53:20 UTC #5

@ngegw Does that patch still exists anywhere and is easy integrable in 19.1?

Ralf

Mgr_Peter_Tuharsky_M 2019-07-03 07:52:46 UTC #6

It seems from the old discussion that the patch was complex - as far as I can digest, it even added NG management options into UI.

That’s great, but for us (who don’t manage AD from EGw) it would be vastly sufficient if only EGw was able to correctly read user’s membership thru NGs, in order to get ACLs etc to proper shape. I hope this is simpler goal to reach, probably in scope of some functions change.

It is not critical for us either. We are implementing a workaround - script-generated technical groups specially for EGw, filled by original AD groups members. But I admit such a solution dosen’t look “nice” nor modern.