Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Unique X500 Object ID?
- Thread starter zeveck
- Start date
There is a Microsoft Technet Article titled
"Step-by-Step guide to Using Active Directory Schema and Display Specifiers"
Object identifiers (OIDs) are issued via the ISO body and from Microsoft Certified for Windows Web site.
There used to be available in the Windows 2000 Resource Kit a file called oidgen.exe that would generate valids OIDs, but I've never used this. I do system administration and have only extended the schema using pre-existing attributes.
Hope this helps
"Step-by-Step guide to Using Active Directory Schema and Display Specifiers"
Object identifiers (OIDs) are issued via the ISO body and from Microsoft Certified for Windows Web site.
There used to be available in the Windows 2000 Resource Kit a file called oidgen.exe that would generate valids OIDs, but I've never used this. I do system administration and have only extended the schema using pre-existing attributes.
Hope this helps
- Thread starter
- #3
So...I just had it explained to me that the only purpose in OIDs was to be internally unique...
That for the product we are shipping we do not specify the OID, and assume that if clients want to do the AD integration they will make up their own OID for the schema attributes necessary for the integration.
Does this make any sense? It sounds like nonsense to me.
My understanding was that a company, say BigFoo Co., registers a prefix with Microsoft and then creates a OID for a given schema attribute and then supplies that OID along with the product to anybody wishing to integrate the product with AD. Doesn't that make a lot more sense?
Does anybody know the details of this enough to give me some links I could use to argue the point?
That for the product we are shipping we do not specify the OID, and assume that if clients want to do the AD integration they will make up their own OID for the schema attributes necessary for the integration.
Does this make any sense? It sounds like nonsense to me.
My understanding was that a company, say BigFoo Co., registers a prefix with Microsoft and then creates a OID for a given schema attribute and then supplies that OID along with the product to anybody wishing to integrate the product with AD. Doesn't that make a lot more sense?
Does anybody know the details of this enough to give me some links I could use to argue the point?
- Status
Similar threads
- Locked
- Question