Directory Programming .NET

Active Directory and ADAM programming support for .NET developers
Welcome to Directory Programming .NET Sign in | Join | Help
in Search

How to Capture and Represent generic X.500 Directory Tree Metadata

Last post 09-16-2010, 8:06 PM by dunnry. 1 replies.
Sort Posts: Previous Next
  •  09-01-2010, 12:11 PM 8531

    How to Capture and Represent generic X.500 Directory Tree Metadata

    I would like to be able to learn/capture information about a generic X.500 Directory Tree so that I can use it to optimize LDAP requests.  I cannot search the entire tree at once due to response size constraints. I need to identify the branches, the number of entries directly beneath each branch and the total number of entries beneath them in the tree. 

    Part of the problem is to determine how to:
    1) learn/capture the tree structure efficiently and in an automated fashion.
    2) determine a way to represent the metadata so that it can be used efficiently within the program (e.g., DSML XML, binary objects, B+Trees).

    It would also be nice if there was a way to ascertain what adds/deletions have occurred since a given date so that the metadata can be updated incrementally.

    Any ideas?

    Thanks .. John


  •  09-16-2010, 8:06 PM 8552 in reply to 8531

    Re: How to Capture and Represent generic X.500 Directory Tree Metadata

    You will have to search using OneLevel scoping and paging.  Depending on your preference, you can do this with the DirectoryEntry or the .Protocols equivalents.  Further, if you are only discovering the topology of the directory (as opposed to the objects it contains), you would simply filter for containers or organizationalUnits.  That should keep the size and resources required to execute such a search down.

    This is how a lot of tree view controls work (only search on expand, only the scope of the node).


    Ryan Dunn
    Extemporaneous Mumblings
    The .NET Developer's Guide to Directory Services Programming
View as RSS news feed in XML