.Net and Active Directory - An OO solution to authority structure - Intro

The goal of .Net and Active Directory - An OO solution to authority structure is to create a Object Oriented manner of looking at an individual and their place within an organization employing AD.  The result will be an accessible object model which exposes pertinent information about the user in question, as well as those who are connected to the individual within the organization.  The practical application of such a structure is a baseline for attaching "ownership" to various resources within a given system.  This structure is serializable and thus can be stored in a database for association and reference when needed.

Part 1 will review the basics of using the .Net framework for accessing a user or DirectoryEntry by knowing either their UserName or by searching for them via a FirstName and/or LastName string.

Part 2 will access the attributes of the given DirectoryEntry and create an object we will call an Owner object.  This will make accessing the needed attributes more consumer friendly than the model provided by .Net.  It will also show how to use a simple code block to debug into and discover the attributes associated with your DirectoryEntry since you may need to expose different attributes than the ones used here.

Part 3 will introduce the User object and the Group object.  These represent DirectoryEntry objects in .Net like the Owner object does, however as the name implies they represent people and groups within Active Directory.

Part 4 will show how to group these new objects into Collections so we can iterate through them more easily and eventually attach them to our Owner object.

Part 5 will demonstrate how to populate these objects with the the Owner's direct reports (UsersCollection) and groups he manages (GroupCollection).

Part 6 iterates down the chain of command from our Owner, to his direct reports, and theirs and so on until we can get no further because the Users at this level have no one reporting to them.

Part 7 walks the other direction, to the Owner's manager, their manager and so on until we can get no higher in the chain of command.  These entities are represented as Manager objects and since each DirectoryEntry has one "Managed By", there is no collection of Manager objects.

Part 8 serializes the whole thing for storage and discusses practical solutions in it's use.

Part 9 Conclusions and Practical Applications of the solution.

What this series does not do is go into the setup and administration of Active Directory.  It assumes you have a working and populated instance of AD, a firm grasp of Class structure, inheritance and Object Orienting design and programming.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: AaronZalewski
Posted on: 1/20/2008 at 4:53 PM
Tags: , ,
Categories: Active Directory
Actions: E-mail | Kick it! | DZone it! | del.icio.us
Post Information: Permalink | Comments (0) | Post RSSRSS comment feed

Related posts

Comments are closed