Attribute signature schema and method of use in a directory service

• US 6,564,370 B1
• Filed: 05/06/1999
• Issued: 05/13/2003
• Est. Priority Date: 05/06/1999
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hunt, Gary Thomas
• Primary Examiner(s): Morse, Gregory
• Assistant Examiner(s): Vo, Ted T.
• Application Number:
  US09/306,191
• Time in Patent Office: 1,468 Days
• Field of Search: 717/170-171, 717/120-122, 707/3, 707/102, 707/103, 707/203, 707/6
• US Class Current: 717/122
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99936 Pattern matching access

Abstract

A directory schema for directory applications or platforms that store common attributes in a distributed directory. According to the schema, a given attribute is stored in a directory together with a signature that identifies given information, e.g., the purpose and version of the attribute. Thus, when an attribute is migrated to a new value, e.g., upon the release of a new application version, the directory schema need not be extended. Rather, the attribute may be maintained in the schema is the same location as was used with an earlier application version.

Claims

1. A method for managing information in a directory, comprising the steps of:

for an attribute shared by a plurality of applications, storing the attribute in the directory together with a signature identifying a then-current version of the attribute;

in response to a query, using the signature to determine whether an application that generates the query expects to receive an earlier version of the attribute;

if the application expects to receive an earlier version of the attribute, initiating a query to the directory for the then-current version of the attribute; and

returning the earlier version of the attribute to the application.

2. The method as described in claim 1 wherein the directory returns the then-current version of the attribute in response to the query generated by the application.

3. The method as described in claim 2 further including the step of modifying the then-current version of the attribute to generate the earlier version of the attribute that is returned to the application.

4. The method as described in claim 1 wherein the signature also identifies an application that generated the signature.

5. The method as described in claim 1 wherein, if the application does not expects to receive an earlier version of the attribute:

initiating the query to the directory for the then-current version of the attribute; and

returning the then-current version of the attribute to the application.

6. The method as described in claim 1 wherein the directory is a Lightweight Directory Access Protocol (LDAP) directory service.

7. A method for storing information in a directory, comprising the steps of:

for each attribute used by a plurality of applications, storing the attribute in a respective common part of the directory;

signing each attribute with a respective signature that indicates a current version of the attribute;

returning to one of the plurality of applications a proper version of the attribute by referring to the signature.

8. The method as described in claim 7 wherein a respective signature also includes an identification of an application that generated the signature.

9. The method as described in claim 7 wherein the proper version of the attribute is a superset of the attribute.

10. The method as described in claim 7 wherein the proper version of the attribute is subset of the attribute.

11. A distributed directory for storing information, comprising:

a set of common attributes shared by a plurality of 10 applications, wherein each of the common attributes includes a signature that indicates an owning application and a current version of the attribute; and

means responsive to a client request and the signature for returning to one of the plurality of a proper version of the attribute.

12. The distributed directory as described in claim 11 wherein the proper version of the attribute is a superset of the attribute.

13. The distributed directory as described in claim 11 wherein the proper version of the attribute is subset of the attribute.

14. The distributed directory as described in claim 11 wherein the directory is compliant with the Lightweight Directory Access Protocol (LDAP).

15. An application for use with a directory in which an attribute shared by a plurality of applications is stored together with a signature identifying a then-current version of the attribute, comprising:

directory client code; and

attribute leveling code (a) for using the signature to determine whether the application, in response to a query generated by the directory client code, expects to receive an earlier version of the attribute, (b) for initiating a query to the directory for the then-current version of the attribute if the application expects to receive an earlier version of the attribute, and (c) for returning the earlier version of the attribute to the application.

16. In a client directory application for use with a distributed directory in which an attribute shared by a plurality of applications is stored together with a signature identifying a then-current version of the attribute, the improvement comprising:

means for using the signature to determine whether the application, in response to a query generated, expects to receive an earlier version of the attribute;

means for initiating a query to the directory for the then-current version of the attribute if the application expects to receive an earlier version of the attribute; and

means for returning the earlier version of the attribute to the application.

17. A proxy for use in combination with a distributed directory in which attributes shared by a plurality of applications are stored together with signatures, wherein a given signature identifies a then-current version of the attribute, comprising:

means responsive to a query from one of the applications for using the signature to determine whether the application expects to receive an earlier version of the attribute;

means for initiating a query to the directory for the then-current version of the attribute if the application expects to receive an earlier version of the attribute; and

means for returning the earlier version of the attribute to the application.

18. The proxy as described in claim 17 further including:

means for initiating a query to the directory for the then-current version of the attribute if the application does not expect to receive the earlier version of the attribute; and

means for returning the then-current version of the attribute to the application.

19. A computer program product in a computer-readable medium for use in combination with a distributed directory in which attributes shared by a plurality of applications are stored together with signatures, wherein a given signature identifies a then-current version of the attribute, comprising:

means responsive to a query from one of the applications for using the signature to determine whether the application expects to receive an earlier version of the attribute;

means for initiating a query to the directory for the then-current version of the attribute whether or not the application expects to receive an earlier version of the attribute;

means for returning the earlier version of the attribute to the application if the application expects to receive an earlier version of the attribute; and

means for returning the then-current version of the attribute to the application if the application expects to receive the then-current version of the attribute.