Possibility for dynamic OUs in eDirectory? Not dynamic Groups !

Idea ID 2786158

Possibility for dynamic OUs in eDirectory? Not dynamic Groups !

Szenario:
Wir benutzen eDirectory in unserem Unternehmen. Unser Unternehmen hat viele Subunternehmen und zentrale Dienste. Jeder braucht seine eigene Ansicht auf Benutzeraccounts und Ressourcen im eDirectory. Im Moment hat jedes Subunternehmen seinen eigenen Subbaum im eDirectory. Dies verursacht aber hohen Entwicklungsaufwand bei neuen zentralen Diensten.

Meine Idee:

Wir haben eine OU mit allen Benutzern.
Wir haben eine OU mit allen Ressourcen.

Example:
- Dynamische OU mit Benutzern von Subunternehmen 1
- Dynamsiche OU mit Benutzern von Subunternehmen 2
...

Darüber könnte man die Sicht für die Subunternehmen steuern.

Für die zentralen Dienste wäre eine OU mit allen Benutzern einfacher zu implementieren. Der LDAP Filter wäre einfacher, weil viele Applikationen Extensible Matches nicht unterstützen.

Einfach nur eine Idee. Bitte um Feedback.

Michael
1 Comment
Micro Focus Expert
Micro Focus Expert

For those like myself who only understand English: (sorry 😉 )

Scenario:
We use eDirectory in our company. Our company has many subcontractors and
central services. Everyone needs their own view of user accounts and resources
in eDirectory. At the moment, each subcontractor has its own subtree in the
eDirectory. However, this causes high development expenditure for new central
services. My idea: We have an OU with all users. We have an OU with all resources. Example: - Dynamic OU with users of subcontractors 1 - Dynamic OU with users of subcontractors 2 ... This could be used to control the view for the subcontractors. For the central services, an OU with all users would be easier to implement.
The LDAP filter would be simpler because many applications do not support
extensible matches. Just an idea. Please leave feedback. Michael

 

Wondering if a number of Loopback drivers pointing at the Vault might be a flexible dynamic option in your situation. With all your users and resources in central contexts and the individual Loopback drivers scope from there based on subcontractor specific attributes to dynamically update the designated subcontractor contexts (OU).

If there are other drivers synchronizing users and resources, they could be scoped to work only with the central "common" context and ignore the subcontractor contexts.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.