Using a directory service for a user registry

• US 7,653,750 B2
• Filed: 05/22/2007
• Issued: 01/26/2010
• Est. Priority Date: 03/06/2001
• Status: Expired due to Term

• Current Assignee: X Corp. (f/k/a Twitter, Inc.) (X Holdings Corp.)
• Original Assignee: International Business Machines Corporation
• Inventors: Fleming, Patrick Jerome
• Primary Examiner(s): Srivastava; Vivek
• Assistant Examiner(s): Duong; Thomas
• Application Number:
  US11/751,703
• Publication Number:
  US 20070220015A1
• Time in Patent Office: 980 Days
• Field of Search: 709217-219, 709/230, 709/246
• US Class Current: 709/246
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

An apparatus and method provide an architected way for a web server to access a user registry in a directory service such as LDAP. In the preferred embodiments, the logic for presenting and processing a web page is encapsulated from the logic that interacts with the directory service, making it easy for a programmer to make changes to the a user registration form without having to have a detailed knowledge of the directory service and its interfaces.

Claims

1. An apparatus comprising:

at least one processor;

a memory coupled to the at least one processor;

a user registration web page residing in the memory;

a page server mechanism residing in the memory and executed by the at least one processor that renders the user registration web page to a user;

a user registration servlet residing within a web server application in the memory and executed by the at least one processor that receives user registration data from the user registration web page when the user submits the user registration web page and that formats the user registration data into an Extensible Markup Language (XML) document;

a user registry Java bean residing in the memory and executed by the at least one processor that receives the XML document with the user registration data and that generates therefrom a Directory Service Markup Language (DSML) document according to information in an Extensible Stylesheet Language (XSL) stylesheet;

a Lightweight Directory Access Protocol (LDAP) server residing in the memory and executed by the at least one processor that accesses an LDAP directory that has a plurality of entries, the plurality of entries including at least one entry that contains user registry information; and

an LDAP Java bean residing in the memory and executed by the at least one processor that receives the DSML document and generates therefrom at least one command to the LDAP server to access the user registry information in the LDAP directory, wherein the user registry Java bean translates the XML document to the DSML document to encapsulate presentation logic of the web server application from business logic in the LDAP Java bean to access the LDAP server.

2. The apparatus of claim 1, wherein the user registration data comprises one or more attributes chosen from the group consisting of:

a first name, a last name, a user identifier, a password, an eMail address, and a telephone number.

3. A method for accessing a user registry stored in an LDAP directory, the method comprising the steps of:

(A) displaying a HTML form to a user;

(B) receiving data in the HTML form from the user;

(C) extracting the data from the HTML form;

(D) formatting the extracted data into an Extensible Markup Language (XML) document in a web server application;

(E) processing the XML document with a user registry java bean using information in an Extensible Stylesheet Language (XSL) stylesheet to generate a Directory Service Markup Language (DSML) document;

(F) processing the DSML document in a LDAP Java bean, and generating therefrom at least one command to access the user registry in the LDAP directory, wherein the user registry java bean translates the XML document to the DSML document to encapsulate presentation logic of the web server application from business logic in the LDAP Java bean to access the LDAP server.

4. The method of claim 3, wherein the data comprises one or more attributes chosen from the group consisting of:

a first name, a last name, a user identifier, a password, an eMail address, and a telephone number.

5. The method of claim 4, wherein the data comprises the user security information.

6. The method of claim 5, further comprising using the user security information to selectively allow access to a web site.

7. The method of claim 6, further comprising customizing the presentation of at least one web page according to the extracted data.

8. The method of claim 7, wherein the at least one command to access the user registry in the LDAP directory comprises Java Naming and Directory Interface (JNDI) commands.

9. The method of claim 3, farther comprising the steps of:

adding a field in the HTML form that is presented to the user;

adding a corresponding new line in a XML document type definition (DTD) that defines the XML document, and

adding a line to the XSL stylesheet to account for the newly added field in the HTML form.

10. A program product comprising:

(A) a user registration page that includes a user registration web page;

(B) a page server mechanism that renders the user registration web page to a user;

(C) a user registration servlet that receives data from the user registration web page and that formats the data into an Extensible Markup Language (XML) document;

(D) a user registry Java bean residing within a web server application that receives the XML document and that generates therefrom a Directory Service Markup Language (DSML) document according to information in an Extensible Stylesheet Language (XSL) stylesheet;

(E) a Lightweight Directory Access Protocol (LDAP) server that accesses an LDAP directory that has a plurality of entries, the plurality of entries including at least one entry that contains user registry information;

(F) an LDAP Java bean that receives the DSML document and generates therefrom at least one command to the LDAP server to access the user registry information in the LDAP directory, wherein the user registry Java bean translates the XML document to the DSML document to encapsulate presentation logic of the web server application from business logic in the LDAP Java bean to access the LDAP server; and

(G) tangible, computer-recordable media bearing (A), (B), (C), (D), (E) and (F).