|
Did you consider using SQL to store all the metadata for the groups? That’s
what I’m doing now, or planning to, but I’d be interested to hear if
you debated this what the final reasoning was. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED] We do the vast majority of our group
management via a custom web interface. The system is self-service and
requires no approval process for creating a group. We do enforce some
semantics and business rules though. For example, we enforce specific
naming conventions, require a sponsor to be named (manager+ level internally),
2+ owners (can be valid users or other security groups) and a valid
description. We allow users to create security groups, mail-enabled
distro groups or mail-enabled security groups. Owners can modify or delete the
group. Name changes are not allowed after creation. We also support email change notifications
for different types of events, an expiration process where groups have to be
renewed periodically and a background process that ensures that groups maintain
the business rules enforced by the UI in the event that sponsors and owners leave
the organization or owner groups are deleted. This app manages about 60K groups in a
single domain with about 110K users. It works really well for us.
The original web app took about 2 months for 2 guys to build and is 100%
ASP.NET. Note that all of the security in the app is
“application-managed”, in that a super user account makes all of
the modifications and enforces the security policy in the business rules.
We chose this approach to prevent people from using AD U&C to modify groups
or any other LDAP code. We also use custom schema for representing all of
the security attributes instead of DACLs as DACLs are a PITA to program and
can’t be queried effectively (which groups do I own or sponsor? etc.). Joe K. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
This
message is for the designated recipient only and may contain privileged,
proprietary, or otherwise private information. If you have received it in
error, please notify the sender immediately and delete the original. Any other
use of the email by you is prohibited. |
- [ActiveDir] Group Management Raymond . Balaian
- RE: [ActiveDir] Group Management Brian Desmond
- RE: [ActiveDir] Group Management joe
- RE: [ActiveDir] Group Management joseph.e.kaplan
- RE: [ActiveDir] Group Management Brian Desmond
- RE: [ActiveDir] Group Management Ken Cornetet
- RE: [ActiveDir] Group Management Ken Cornetet
- RE: [ActiveDir] Group Management joseph.e.kaplan
- RE: [ActiveDir] Group Management joseph.e.kaplan
- RE: [ActiveDir] Group Management joseph.e.kaplan
- RE: [ActiveDir] Group Management joseph.e.kaplan
