Data interoperability between open standard directory service and proprietary database

• US 7,184,995 B2
• Filed: 02/26/2003
• Issued: 02/27/2007
• Est. Priority Date: 02/26/2003
• Status: Expired due to Fees

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: America Online Inc. (Warner Bros. Discovery, Inc.)
• Inventors: Smith, Mark Christopher, Kaw, Bindu Kaul
• Primary Examiner(s): Alam, Shahid
• Assistant Examiner(s): Ehichioya, Fred I.
• Application Number:
  US10/375,803
• Publication Number:
  US 20040167866A1
• Time in Patent Office: 1,462 Days
• Field of Search: 707/1, 707/6, 707/10, 707/100, 707/102, 707/4, 707/103.R, 707/3, 707/8, 707/103, 707/104.1, 719/315, 705/39, 709/203, 709/217, 709/219, 709/220, 709/202, 709/225, 709/227, 709/228, 709/236
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• 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/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A method of providing interoperability between an open standard directory service and a proprietary database. The directory is represented as a mapping tree, consistent with directory service protocols such as X.500 or LDAP. The mapping tree node associated with the proprietary database is configured as a null suffix mapping tree entry, so that database mapping tree node replaces root of the mapping tree and the proprietary database the default backend of the directory service. The core server of the directory service is configured to recognize the null suffix mapping tree entry. All directory service operations are routed to a pre-operation plug-in that handles operations in the proprietary database, and remaining operations are redirected to the core server, preserving default functionality of the directory service. Normal data constraints are suspended for operations performed in the proprietary database.

Claims

1. A computer-implemented method of providing interoperability between a LDAP (lightweight directory access protocol) directory service and a proprietary database comprising the steps of:

configuring a node representing said proprietary database in a mapping tree for said LDAP directory service to replace root of said mapping tree and to replace default backend of said LDAP directory service with said proprietary database;

configuring a core server of said LDAP directory service to recognize said mapping tree node representing said proprietary database as root of said mapping tree;

routing all LDAP directory service operations to an object that handles operations in said proprietary database;

recognizing naming contexts reserved for exclusive use of said core server by said object; and

redirecting operations in these naming contexts to said corn server;

wherein operations directed to said proprietary database by means of said LDAP directory service are acted on by said object and a result returned.

2. The method of claim 1, wherein said step of configuring said node representing said proprietary database comprises configuring said node as a null suffix mapping tree entry.

3. The method of claim 2, wherein said step of configuring said core server comprises configuring said core server to recognize said null suffix mapping tree entry.

4. The method of claim 1, further comprising the step of:

suspending at least one data model constraint imposed by said LDAP for operations in said proprietary database, so that operations in said proprietary data base can be performed even if said proprietary database does not conform to said data model constraint.

5. The method of claim 4, wherein said at least one constraint comprises the requirement of a well-formed tree.

6. The method of claim 4, wherein said step of suspending at least one data model constraint imposed by said LDAP for operations in said proprietary database comprises invoking said plug-in before said constraints are applied by said core server.

7. The method of claim 1, further comprising the step of suspending access control checking far actions handled by said object.

8. The method of claim 7, said step of suspending access control checking comprising the steps of:

providing a flag in a data structure of an operation to be handled by said object, wherein setting said flag disables access control; and

setting said flag by said object.

9. The method of claim 1, wherein said object that handles operations in said proprietary database comprises a pre-operation plug-in.

10. A computer program product comprising computer readable code embodied on a tangible medium, said code including code means for performing the steps of a method of providing interoperability between a LDAP (lightweight directory access protocol) directory service and a proprietary database, the method comprising the steps of:

configuring a node representing said proprietary database in a mapping tree for said LDAP directory service to replace root of said mapping tree and to replace default backend of said LDAP directory service with said proprietary database;

configuring a core server of said LDAP directory service to recognize said mapping tree node representing said proprietary database as root of said mapping tree;

routing all LDAP directory service operations to an object that handles operations in said proprietary database;

recognizing naming contexts reserved for exclusive use of said core server by said object; and

redirecting operations in these naming contexts to said core server

wherein operations directed to said proprietary database by means of said LDAP directory service are acted on by said object and a result returned.

11. The method of claim 10, wherein said step of configuring said node representing said proprietary database comprises configuring said node as a null suffix mapping tree entry.

12. The method of claim 11, wherein said step of configuring said core server comprises configuring said core server to recognize said null suffix mapping tree entry.

13. The method of claim 10, further comprising the step of:

suspending at least one data model constraint imposed by said LDAP for operations in said proprietary database, so that operations in said proprietary data base can be performed even if said proprietary database does not conform to said data model constraint.

14. The method of claim 13, wherein said at least one constraint comprises the requirement of a well-formed tree.

15. The method of claim 13, wherein said step of suspending at least one data model constraint imposed by said LDAP for operations in said proprietary database comprises invoking said object before said constraints are applied by said core server.

16. The method of claim 10, further comprising the step of suspending access control checking for actions handled by said object.

17. The method of claim 16, said step of suspending access control checking comprising the steps of:

providing a flag in a data structure of an operation to be handled by said object, wherein setting said flag disables access control; and

setting said flag by said object.

18. The method of claim 10, wherein said object that handles operations in said proprietary database comprises a pre-operation plug-in.