UGN Security
Posted By: Spyrios Active Directory - 01/18/06 01:36 AM
Can someone put into laymans terms (newb speak) how Active Directory class types work?

I am reading and I quote "Structural Classes are the only classes that can have an instance of an object instatiated from them." huh.

Oh and this: "Abstract classes are used as templates for Structural classes and other Abstract classes. Objects in the directory cannot be instantiated directly from an Abstract class-they can only be instantiated from a Structural Class that inherits from the Abstract Class"

And that leads to Auxiliary classes, and WTF is up there?

Anyone have any experience with this?
Posted By: HighLander Re: Active Directory - 01/18/06 10:31 PM
I have an intermediate understanding of Active Directory, which i apperantly not enough to be able to answer that question in its entirety, but I have lots of AD material, books and such, I'll take a look see what I can come up with.
Posted By: jonconley Re: Active Directory - 01/19/06 01:02 AM
A class is a label for a group of common attributes of an object. Some examples would be "Users" or "Computers" objects. That is their class, and username/name or computername/MAC are examples of the attributes. They all contain the same possible attributes and that is their class.

Now that you have the basic idea of what a class is, it is simple to see what the types entail.

ABSTRACT - These are template classes that exist solely to have other classes created from it. They would have attributes that all the classes created from would also have. An example would be "name" or "location". Everything would have a name to be associated with an a set location if not at least the location of origin. These don't contain any objects.

STRUCTURAL - These classes are derived from abstract classes or other structural classes and contain the basic attributes from their abstract classes. As used above, there is the "Users" class in Active Directory. These would contain the "name" and "location" attributes. However, the uncommon attributes for the "Computer" class would be "MAC address" or "SwitchPort" as an example. From there, you could create another class from the "Computer" class that would be perhaps "LAPTOP" and would include additional location and security attributes that are specific to laptops.

As for the instantiated, that IMO would be creating an object such as say Joe Smith User. Now you cannot create an object from an abstract. Only from a structural, which would inherit attributes from an abstract.

This is more so from studying various Active Directory things, and no real world experience frown . Maybe someday...

That does mean I could be off the mark on this, and hopefully someone corrects me.
Posted By: HighLander Re: Active Directory - 01/19/06 11:20 PM
From what I have been reading you pretty much hit it on the head jon
Posted By: jonconley Re: Active Directory - 01/20/06 12:00 AM
You understand anything about Auxiliary classes? It seems they are specialized templates used as extensions. But not exactly sure what that means or how it sets them apart?
Posted By: Spyrios Re: Active Directory - 01/20/06 11:52 PM
Your original reply helped out alot and I have an email into my instructor about Auxillary classes, I will post his response when I get it.
Posted By: sinetific Re: Active Directory - 01/23/06 04:06 AM
Active Directory is [censored]. Learn LDAP. It's far more scalable and flexible and many more applications support LDAP than support active directory.
© UGN Security Forum