Patent US6260039B1 successfully refreshed from Google Patents.
US6260039B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Web interface and method for accessing directory information
Assignee: International Business Machines Corp
•
Filing: 1997-12-15
•
Granted: 2001-07-10
•
Expires: 2017-12-15
Abstract
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.
Inventors
- 👤 David H. Schneck
- 👤 Steve Cherry
- 👤 David Goodman
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-08 01:27
CPC Classifications
H; H04; H04L; H04L67/00; H04L67/01; H04L67/02; G; G06; G06F; G06F16/00; G06F16/90; G06F16/95; G06F16/958; G06F16/972; H04L61/00; H04L61/45; H04L61/4505; H04L61/4517; H04L61/4523; Y; Y10; Y10S; Y10S707/00; Y10S707/99931; Y10S707/99932; Y10S707/99933; Y10S707/99934; Y10S707/99939
Claims Analysis
Total Claims: 36
Claim 1
Independent Claim
90 words
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.
Claim 2
Dependent Claim
90 words
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.
Claim 3
Dependent Claim
62 words
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.
Claim 4
Dependent Claim
15 words
The web interface of claim 2 , wherein said directory request is a read request.
Claim 5
Dependent Claim
35 words
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.
Claim 6
Dependent Claim
15 words
The web interface of claim 2 , wherein said directory request is a list request.
Claim 7
Dependent Claim
39 words
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.
Claim 8
Dependent Claim
15 words
The web interface of claim 2 , wherein said directory request is a search request.
Claim 9
Dependent Claim
37 words
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.
Claim 10
Dependent Claim
24 words
The web interface of claim 1 , wherein said friendly name mapper correlates a directory attribute to a name corresponding to said directory attribute.
Claim 11
Dependent Claim
91 words
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.
Claim 12
Independent Claim
154 words
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.
Claim 13
Independent Claim
154 words
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.
Claim 14
Dependent Claim
20 words
The method of claim 11 , further comprising the step of creating a request response in accordance with said template.
Claim 15
Dependent Claim
13 words
The method of claim 12 , wherein said request is a read request.
Claim 16
Dependent Claim
22 words
The method of claim 13 , wherein said step of creating a request response comprises filling in a tag of said template.
Claim 17
Dependent Claim
13 words
The method of claim 12 , wherein said request is a list request.
Claim 18
Dependent Claim
22 words
The method of claim 15 , wherein said step of creating a request response comprises filling in a tag of said template.
Claim 19
Dependent Claim
13 words
The method of claim 12 , wherein said request is a search request.
Claim 20
Dependent Claim
27 words
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.
Claim 21
Dependent Claim
27 words
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.
Claim 22
Dependent Claim
21 words
The method of claim 1 , further comprising the step of providing an error message if said template is not found.
Claim 23
Dependent Claim
36 words
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.
Claim 24
Dependent Claim
86 words
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.
Claim 25
Dependent Claim
86 words
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.
Claim 26
Dependent Claim
57 words
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.
Claim 27
Dependent Claim
15 words
The web interface of claim 23 , wherein said directory request is a read request.
Claim 28
Dependent Claim
35 words
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.
Claim 29
Dependent Claim
15 words
The web interface of claim 23 , wherein said directory request is a list request.
Claim 30
Dependent Claim
39 words
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.
Claim 31
Dependent Claim
15 words
The web interface of claim 23 , wherein said directory request is a search request.
Claim 32
Dependent Claim
37 words
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.
Claim 33
Dependent Claim
26 words
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.
Claim 34
Dependent Claim
25 words
The web interface of claim 22 , wherein said friendly name mapper means correlates a country abbreviation to a name corresponding to said country abbreviation.
Claim 35
Dependent Claim
176 words
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.
Claim 36
Dependent Claim
176 words
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.
References Cited (Backward Citations)
US5241671A
Cited
US5241671C1
Cited
US5412774A
Cited
US5297249A
Cited
US5388255A
Cited
US5537546A
Cited
US5355497A
Cited
US5572724A
Cited
US5491817A
Cited
US5481666A
Cited
US5500929A
Cited
US5678045A
Cited
US5548723A
Cited
US5600831A
Cited
US5957695A
Cited
US5659616A
Cited
US5832275A
Cited
US5617568A
Cited
US5530852A
Cited
US5742762A
Cited
US5708825A
Cited
US5708780A
Cited
US5812776A
Cited
US5745683A
Cited
US5649186A
Cited
US5572643A
Cited
US5737533A
Cited
US5758343A
Cited
US5774552A
Cited
US5745574A
Cited
US5878219A
Cited
US5754772A
Cited
US5835712A
Cited
US5787450A
Cited
US5907846A
Cited
US5999972A
Cited
US5987245A
Cited
US5832225A
Cited
US5845067A
Cited
US5909679A
Cited
US5872915A
Cited
US5917807A
Cited
US5937406A
Cited
US5918010A
Cited
US5822074A
Cited
US5864850A
Cited
US5940834A
Cited
US5878415A
Cited
US5884035A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2004-07-09 | 2005-01-08 | 2005-07-10 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2008-07-09 | 2009-01-08 | 2009-07-10 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2012-07-09 | 2013-01-08 | 2013-07-10 | $7700.00 | Window Closed / Lapsed |