Using a module for opening multiple databases

• US 9,882,718 B2
• Filed: 03/28/2016
• Issued: 01/30/2018
• Est. Priority Date: 11/30/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Relyea, Robert
• Primary Examiner(s): CERVETTI, DAVID GARCIA
• Application Number:
  US15/082,577
• Publication Number:
  US 20160211975A1
• Time in Patent Office: 673 Days
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 63/062 for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy

Abstract

A processing device is to determine that a module, executed from a memory by the processing device, is an initialized module in view of the module previously opening a first database. The processing device is to create a slot to open a second database using the initialized module.

Claims

1. A method comprising:

determining that a module, executed from a memory by a processing device, is an initialized module in view of the module previously opening a first database; and

causing, by the processing device, the initialized module to create a slot to open a second database for access by an application.

2. The method of claim 1, further comprising identifying the second database from a request from the application to access data that is stored in the second database.

3. The method of claim 2, wherein identifying the second database comprises:

receiving load data that identifies the second database, the load data being based on user-configurable policy information.

4. The method of claim 3, wherein the user-configurable policy information is stored in a lightweight directory access protocol (LDAP)-based database.

5. The method of claim 3, wherein the user-configurable policy information identifies the second database to be opened in view of at least one of:

a server type, an application type, an application name, or user type.

6. The method of claim 3, wherein receiving the load data comprises:

receiving an initialization request to access security data stored in a database;

opening a system database in response to receiving the initialization request, wherein the system database identifies a module database interface;

accessing, via the module database interface, user-configurable policy information stored in an LDAP-based database; and

obtaining the load data for opening the second database.

7. The method of claim 1, wherein determining that the module is an initialized module comprises:

attempting to initialize the initialized module; and

receiving an error code indicating that the initialized module is initialized.

8. The method of claim 1, wherein the initialized module comprises at least one of a soft-token module for opening a database storing security data or a Privacy Enhanced Mail (PEM) module for opening a database storing a PEM file.

9. The method of claim 1, wherein the data comprises at least one of a key, a certificate, or a Privacy Enhanced Mail (PEM) file.

10. A system comprising:

a memory; and

a processing device operatively coupled to the memory, the processing device to;

determine that a module, executed from the memory by the processing device, is an initialized module in view of the module previously opening a first database; and

cause the initialized module to create a slot to open a second database for access by an application.

11. The system of claim 10, the processing device to identify the second database from a request from the application to access data that is stored in the second database.

12. The system of claim 10, the processing device to receive load data that identifies the second database, the load data being based on user-configurable policy information.

13. The system of claim 12, wherein the user-configurable policy information identifies the second database in view of at least one of:

a server type, an application type, an application name, or a user type.

14. The system of claim 12, the processing device to:

receive an initialization request to access security data stored in a database;

open a system database in response to receiving the initialization request, wherein the system database identifies a module database interface;

access, via the module database interface, user-configurable policy information stored in an LDAP-based database; and

obtain the load data for opening the second database.

15. The system of claim 10, the processing device to:

attempt to initialize the initialized module; and

receive an error code indicating that the initialized module is initialized.

16. The system of claim 10, wherein the data comprises at least one of a key, a certificate, or a Privacy Enhanced Mail (PEM) file.

17. A non-transitory computer-readable medium having instructions encoded thereon which, when executed by a processing device, cause the processing device to:

determine that a module, executed from the memory by the processing device, is an initialized module in view of the module previously opening a first database; and

cause, by the processing device, the initialized module to create a slot to open a second database for access by an application.

18. The non-transitory computer-readable medium of claim 17, the processing device to:

receive load data that identifies the second database, the load data being based on user-configurable policy information.

19. The non-transitory computer-readable medium of claim 18, the processing device to:

receive an initialization request to access security data stored in a database;

open a system database in response to receiving the initialization request, wherein the system database identifies a module database interface;

access, via the module database interface, user-configurable policy information stored in an LDAP-based database; and

obtain the load data for opening the second database.

20. The non-transitory computer-readable medium of claim 17, the processing device to:

attempt to initialize the initialized module; and

receive an error code indicating that the initialized module is initialized.