Method and system for configuring a supplemental directory

• US 8,321,486 B2
• Filed: 11/09/2005
• Issued: 11/27/2012
• Est. Priority Date: 11/09/2005
• Status: Expired due to Fees

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Harvey, Richard H., Groenveld, Damon N., McDonald, Justin J.
• Primary Examiner(s): Vital, Pierre
• Assistant Examiner(s): Mitiku, Berhanu
• Application Number:
  US11/270,794
• Publication Number:
  US 20070112790A1
• Time in Patent Office: 2,575 Days
• Field of Search: None
• US Class Current: 707/831
• CPC Class Codes: G06F 16/9027 Trees

Abstract

According to one embodiment of the invention a method of updating schema in a directory system having a reference layer adapted to provide directory functionality and an intermediate layer adapted to provide supplemental directory functionality is provided. The intermediate layer is provided between the reference layer and the client is provided. The method includes determining that a new attribute type is not defined in a schema associated with the system, and in response, registering the new attribute type in the schema.

Claims

1. A method of updating schema in a directory system, the method comprising:

providing the directory system having a reference layer adapted to provide directory functionality for a first data store and an intermediate layer adapted to provide supplemental directory functionality for a second data store, wherein the intermediate layer is provided between the reference layer and a client, and wherein;

the reference layer comprises a first directory having a fixed directory information tree associated with the first data store and a first schema that is not extensible; and

the intermediate layer comprises a second directory having an extensible directory information tree associated with the second data store and a second schema that is extensible;

determining that a new attribute type is not defined in the first schema;

registering the new attribute type in the second schema in response to said determining, the supplemental directory functionality of the intermediate layer using the second schema to make the first schema associated with the first directory appear extensible; and

providing a client view of the directory system that presents the first directory as having information stored in the first directory and the second directory even though at least a value associated with the new attribute type is stored in the second directory but not in the first directory.

2. The method of claim 1, wherein the attribute type is included within an operation received by the directory system.

3. The method of claim 2, wherein the operation is an add-entry, modify-entry, or a modify-DN operation.

4. The method of claim 3, wherein a value associated with the operation is stored in the directory system.

5. The method of claim 4, wherein the value is stored in the directory system where the attribute type is registered.

6. The method of claim 1, wherein the directory is adapted to operate in accordance with one or more of the standards selected from the group consisting of X.500, Lightweight Directory Access Protocol (LDAP), and Directory Service Markup Language (DSML).

19. The method of claim 1, wherein:

the reference layer provides directory functionality for the first directory storing a first set of attributes;

the intermediate layer provides supplemental directory functionality for the second directory storing a second set of attributes.

20. The method of claim 19, wherein the intermediate layer presents a client view allowing the client to view the first directory as having the first set of attributes supplemented by the second directory having the second set of attributes.

21. The method of claim 19, wherein the second set of attributes includes first set of attributes and at least one extra attributes.

28. The method of claim 1, wherein registering the new attribute type comprises using a template to create an attribute definition for the new attribute type.

29. The method of claim 28, wherein the attribute definition indicates that the attribute definition for the new attribute within the second schema has been automatically generated.

35. The method of claim 1, wherein the new attribute type is not supported by the first schema.

7. A directory system comprising:

a reference layer adapted to provide directory functionality for a first data store, the reference layer comprising a first directory having a fixed directory information tree associated with the first data store and a first schema that is not extensible;

an intermediate layer adapted to provide supplemental directory functionality for a second data store, wherein the intermediate layer is operatively provided between the reference layer and the client, the intermediate layer comprises a second directory having an extensible directory information tree associated with the second data store and a second schema that is extensible;

a processor; and

a computer-readable medium accessible by the processor, the computer-readable medium storing encoded logic operable when executed by the processor to determine that a new attribute type is not defined in the first schema, and in response to determining that the new attribute is not defined, register the new attribute type in the second schema, the supplemental directory functionality of the intermediate layer using the second schema to make the first schema associated with the first directory appear extensible, and

wherein the computer readable medium further storing encoded logic operable when executed to provide a client view of the directory system that presents the first directory as having information stored in the first directory and the second directory even though at least a value associated with the new attribute type is stored in the second directory but not in the first directory.

8. The directory system of claim 7, wherein the attribute type is included within an operation received by the directory system.

9. The directory system of claim 8, wherein the operation is an add-entry, modified-entry, or a modified-DN operation.

10. The directory system of claim 9, wherein a value associated with the operation is stored in the directory system.

11. The directory system of claim 10, wherein the value is stored in the directory system where the attribute type is registered.

12. The directory system of claim 7, wherein the directory is adapted to operate in accordance with one or more of the standards selected from the group consisting of X.500, Lightweight Directory Access Protocol (LDAP), and Directory Service Markup Language (DSML).

22. The directory system of claim 7, wherein:

the reference layer provides directory functionality for the first directory storing a first set of attributes;

the intermediate layer provides supplemental directory functionality for the second directory storing a second set of attributes.

23. The directory system of claim 22, wherein the intermediate layer presents a client view allowing the client to view the first directory as having the first set of attributes supplemented by the second directory having the second set of attributes.

24. The directory system of claim 22, wherein the second set of attributes includes first set of attributes and at least one extra attributes.

30. The directory system of claim 7, wherein when registering the new attribute type the logic is operable when executed to use a template to create an attribute definition for the new attribute type.

31. The directory system of claim 30, wherein the attribute definition indicates that the attribute definition for the new attribute within the second schema has been automatically generated.

36. The directory system of claim 7, wherein the logic is further operable when executed by the processor to provide a client view of the directory system that presents the first directory as having information stored in the first directory and the second directory even though at least a value associated with the new attribute type is stored in the second directory but not in the first directory.

37. The directory system of claim 7, wherein the new attribute type is not supported by the first schema.

13. A computer-readable storage medium comprising a memory, the computer-readable storage medium encoded with software operable when executed by a processor to:

provide a directory system having a reference layer adapted to provide directory functionality for a first data store and an intermediate layer adapted to provide supplemental directory functionality, for a second data store wherein the intermediate layer is operatively provided between the reference layer and the client, and wherein;

the reference layer comprises a first directory having a fixed directory information tree associated with the first data store and a first schema that is not extensible; and

the intermediate layer comprises a second directory having an extensible directory information tree associated with the second data store and a second schema that is extensible;

determine that a new attribute type is not defined in the first schema; and

register the new attribute type in the second schema in response to said determining, the supplemental directory functionality of the intermediate layer using the second schema to make the first schema associated with the first directory appear extensible; and

provide a client view of the directory system that presents the first directory as having information stored in the first directory and the second directory even though at least a value associated with the new attribute type is stored in the second directory but not in the first directory.

14. The computer-readable storage medium of claim 13, wherein the attribute type is included within an operation received by the directory system.

15. The computer-readable storage medium of claim 14, wherein the operation is an add-entry, modified-entry, or a modified-DN operation.

16. The computer-readable storage medium of claim 15, wherein a value associated with the operation is stored in the directory system.

17. The computer-readable storage medium of claim 16, wherein the value is stored in the directory system where the attribute type is registered.

18. The computer-readable storage medium of claim 13, wherein the directory is adapted to operate in accordance with one or more of the standards selected from the group consisting of X.500, Lightweight Directory Access Protocol (LDAP), and Directory Service Markup Language (DSML).

25. The computer-readable storage medium of claim 13, wherein:

the reference layer provides directory functionality for the first directory storing a first set of attributes;

the intermediate layer provides supplemental directory functionality for the second directory storing a second set of attributes.

26. The computer-readable storage medium of claim 25, wherein the intermediate layer presents a client view allowing the client to view the first directory as having the first set of attributes supplemented by the second directory having the second set of attributes.

27. The computer-readable storage medium of claim 25, wherein the second set of attributes includes first set of attributes and at least one extra attributes.

32. The computer-readable storage medium of claim 13, wherein registering the new attribute type comprises using a template to create an attribute definition for the new attribute type.

33. The computer-readable storage medium of claim 32, wherein the attribute definition indicates that the attribute definition for the new attribute within the second schema has been automatically generated.

38. The computer-readable storage medium of claim 13, the software is further operable when executed by the processor to provide a client view of the directory system that presents the first directory as having information stored in the first directory and the second directory even though at least a value associated with the new attribute type is stored in the second directory but not in the first directory.

39. The computer-readable storage medium of claim 13, wherein the new attribute type is not supported by the first schema.

34. A method of updating schema in a directory system, the method comprising:

providing the directory system having a reference layer adapted to provide directory functionality and an intermediate layer adapted to provide supplemental directory functionality, wherein the intermediate layer is provided between the reference layer and a client, and wherein;

the reference layer comprises a first directory having a fixed directory information tree and a first schema that is not extensible; and

the intermediate layer comprises a second directory having an extensible directory information tree and a second schema that is extensible;

determining that a new attribute type is not defined in the first schema;

registering the new attribute type in the second schema in response to said determining, the supplemental directory functionality of the intermediate layer using the second schema to make the first schema associated with the first directory appear extensible; and

providing a client view of the directory system that presents the first directory as having information stored in the first directory and the second directory even though at least a value associated with the new attribute type is stored in the second directory but not in the first directory; and

providing a client view of the directory system that presents the first directory as having information stored in the first directory and the second directory even though at least a value associated with the new attribute type is stored in the second directory but not in the first directory.