Web interface and method for accessing directory information

• US 6,260,039 B1
• Filed: 12/15/1997
• Issued: 07/10/2001
• Est. Priority Date: 12/15/1997
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Goodman, David, Cherry, Steve, Schneck, David H.
• Primary Examiner(s): Alam, Hosain T.
• Assistant Examiner(s): Corrielus, Jean M.
• Application Number:
  US08/990,765
• Time in Patent Office: 1,303 Days
• Field of Search: 707/10, 707/103, 707/3, 707/9, 707/1, 707/2, 707/4, 707/505, 707/506, 707/507, 709/217, 709/218, 709/219, 713/200, 713/201, 713/202
• US Class Current: 1/1
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/4517 using open systems interconnection [OSI] directories, e.g. X.500
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

A Web Interface and Method for Accessing Directory Information is disclosed. A Web Interface for Accessing Directory Information comprises a request mapper that links directory data to a template file in response to a directory request, and a friendly name mapper that correlates an abbreviated name to a non-abbreviated name. The abbreviated name refers to at least one entry of said directory data. A method for accessing directory information in accordance with the invention comprises the following steps: (1) receiving a request for directory data; (2) determining whether the request is a distinguished name request, wherein the distinguished name request is a request for a distinguished name; (3) in response to a determination that the request is not a distinguished name request, retrieving a directory resource corresponding to the request; (4) in response to a determination that the request is a distinguished name request, determining whether the distinguished name is mapped; (5) in response to a determination that the distinguished name is not mapped, retrieving an object class of the distinguished name and finding a template using the object class; and (6) in response to a determination that the distinguished name is mapped, finding a template using the distinguished name.

Claims

1. A web interface for accessing directory information comprising:

a server, said server receiving a request, in a HTTP protocol, to retrieve directory data, said directory data comprising a X-500 protocol;

a request mapper, said request mapper linking said directory data in said X-500 protocol to a template file in response to said request to retrieve directory data; and

a friendly name mapper, said friendly name mapper correlating an abbreviated name to an unabbreviated name, wherein said abbreviated name refers to an entry of said directory data in said X-500 protocol.

2. The web interface of claim 1, wherein said request mapper further comprises:

a distinguished name mapper, said distinguished name mapper correlating a distinguished name to said template file in response to a distinguished name request; and

an object class mapper, said object class mapper correlating a plurality of distinguished names to said template file in response to an object class request.

3. The web interface of claim 2, wherein said directory request is a read request.

4. The web interface of claim 3, wherein said directory data is mapped to a read request template file, said read request template file comprising a template for an object class of requested directory data.

5. The web interface of claim 2, wherein said directory request is a list request.

6. The web interface of claim 5, wherein said directory data is mapped to a list request template file, said list request template file comprising a template for an object class of requested directory data and subordinate object classes.

7. The web interface of claim 2, wherein said directory request is a search request.

8. The web interface of claim 7, wherein said directory data is mapped to a search request template file, said search request template file comprising a template for at least one object class of requested directory data.

9. The web interface of claim 1, wherein said friendly name mapper correlates a directory attribute to a name corresponding to said directory attribute.

10. The web interface of claim 1, wherein said friendly name mapper correlates a country abbreviation to a name corresponding to said country abbreviation.

in response to a determination that said request is a distinguished name request, determining whether said distinguished name is mapped;

in response to a determination that said distinguished name is not mapped, retrieving an object class of said distinguished name and finding a template using said object class; and

in response to a determination that said distinguished name is mapped, finding a template using said distinguished name.

20. The method of claim 1, further comprising the step of providing an error message if said template is not found.

11. A method for accessing directory information comprising:

receiving at a server, in an HTTP protocol, a request for directory data, wherein said directory data comprises an X-500 protocol;

determining whether said request is a distinguished name request, wherein said distinguished name request is a request for a distinguished name;

in response to a determination that said request is not a distinguished name request, retrieving said directory data corresponding to said request wherein said directory data comprises a X-500 protocol;

in response to a determination that said request is a distinguished name request, determining whether said distinguished name is mapped;

in response to a determination that said distinguished name is not mapped, retrieving an object class of said distinguished name and finding a template using said object class, wherein said object class comprises said X-500 protocol; and

in response to a determination that said distinguished name is mapped, finding a template using said distinguished name.

12. The method of claim 11, further comprising the step of creating a request response in accordance with said template.

13. The method of claim 12, wherein said request is a read request.

14. The method of claim 13, wherein said step of creating a request response comprises filling in a tag of said template.

15. The method of claim 12, wherein said request is a list request.

16. The method of claim 15, wherein said step of creating a request response comprises filling in a tag of said template.

17. The method of claim 12, wherein said request is a search request.

18. The method of claim 17, wherein said step of creating a request response comprises creating a search filter and filling in a tag of said template.

19. The method of claim 11, wherein said step of retrieving an object class further comprises providing an error message if said object class is not mapped.

21. The method of claim 11, further comprising the steps of:

replacing a directory attribute with a name corresponding to said directory attribute; and

replacing a country abbreviation with a name corresponding to said country abbreviation.

22. A web interface for accessing directory information comprising:

server means, said server means receiving a request, in a HTTP protocol, to retrieve directory data, said directory data comprising a X-500 protocol;

request mapper means for linking said directory data in said X-500 protocol to a template file in response to said request to retrieve directory data; and

friendly name mapper means for correlating an abbreviated name to an unabbreviated name, wherein said abbreviated name refers to an entry of said directory data in said X-500 protocol.

23. The web interface of claim 22, wherein said request mapper means further comprises:

distinguished name mapper means for correlating a distinguished name to said template file in response to a distinguished name request; and

object class mapper means for correlating a plurality of distinguished names to said template file in response to an object class request.

24. The web interface of claim 23, wherein said directory request is a read request.

25. The web interface of claim 24, wherein said directory data is mapped to a read request template file, said read request template file comprising template means for an object class of requested directory data.

26. The web interface of claim 23, wherein said directory request is a list request.

27. The web interface of claim 26, wherein said directory data is mapped to a list request template file, said list request template file comprising template means for an object class of requested directory data and subordinate object classes.

28. The web interface of claim 23, wherein said directory request is a search request.

29. The web interface of claim 28, wherein said directory data is mapped to a search request template file, said search request template file comprising template means for at least one object class of requested directory data.

30. The web interface of claim 22, wherein said friendly name mapper means correlates to a directory attribute to a name corresponding to said directory attribute.

31. The web interface of claim 22, wherein said friendly name mapper means correlates a country abbreviation to a name corresponding to said country abbreviation.

32. An electronic storage medium having code embodied thereon for causing a processor to access directory information, the medium comprising:

receiving code that enables a server to receive a request, in a HTTP protocol, for directory data, said directory data comprising an X-500 protocol;

distinguished name determining code that determines whether the request for directory data is a distinguished name request;

resource retrieving code that, in response to a determination that the request for directory data is not a distinguished name request, retrieves said directory data corresponding to the request for directory data, wherein said directory data comprises a X-500 protocol;

mapping determining code that determines whether the distinguished name request is mapped;

object class retrieving code that, in response to a determination that the distinguished name is not mapped, retrieves an object class of the distinguished name and finds a template using the object class, wherein said object class comprises said X-500 protocol; and

template finding code that, in response to a determination that the distinguished name is mapped, finds a template using the distinguished name.