list the allowed attributes

[n***@nospam.nospam]

Hi,
Looking for some ideas and suggestions. I develop a software applicatio=
n =

that allows users to pull information from AD to be viewed from this app=
. =

We allow them to specify which User object and Group object attributes t=
o =

display. The problem is trying to make sure those attributes entered in=
=

are valid attributes. So I'd like to send a query or call a method to =

pull all valid/allowed attributes by their lDAPDisplayName. And then =

check the user values against that list. I'm just not sure the best and=
=

most efficient way to do this.

Couple avenues i've come across to accomplish this:
attributeDisplayNames attribute in =

CN=3Duser-Display,CN=3D409,CN=3DDisplaySpecifiers,CN=3DConfiguration,DC=3D=
unimax,DC=3Dcom

and

From a Kaplan post in 2004 using System.DirectoryServices:
entry.RefreshCache(new string[] {"allowedAttributes"});

Thanks for the input.

Nate

[Richard Mueller [MVP]]

Nate wrote:

Looking for some ideas and suggestions. I develop a software application
that allows users to pull information from AD to be viewed from this app.
We allow them to specify which User object and Group object attributes to
display. The problem is trying to make sure those attributes entered in
are valid attributes. So I'd like to send a query or call a method to
pull all valid/allowed attributes by their lDAPDisplayName. And then
check the user values against that list. I'm just not sure the best and
most efficient way to do this.

Couple avenues i've come across to accomplish this:
attributeDisplayNames attribute in
CN=user-Display,CN=409,CN=DisplaySpecifiers,CN=Configuration,DC=unimax,DC=com

and

From a Kaplan post in 2004 using System.DirectoryServices:
entry.RefreshCache(new string[] {"allowedAttributes"});

allowedAttributes are the lDAPDisplayNames permitted to be assigned to the
class of objects. You probably want to use allowedAttributesEffective, which
is the attributes that can be modified on the object. You can also use the
Schema method of the object and enumerate the MandatoryProperties and
OptionalProperties. I think this gives the same result. See this link:

http://www.microsoft.com/technet/scriptcenter/resources/qanda/jun05/hey0628.mspx

The attributeDisplayNames attribute seems to be mostly attributes that show
up in ADUC. Many attributes are missing.