Method and apparatus for enabling database privileges

• US 7,503,062 B2
• Filed: 06/20/2003
• Issued: 03/10/2009
• Est. Priority Date: 06/29/1999
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lei, Chon H., Wong, Daniel M.
• Primary Examiner(s): Zand; Kambiz
• Assistant Examiner(s): Jackson; Jenise E
• Application Number:
  US10/600,388
• Publication Number:
  US 20040054933A1
• Time in Patent Office: 2,090 Days
• Field of Search: 726/2, 707/9, 713/164, 713/167
• US Class Current: 726/2
• CPC Class Codes: G06F 21/577 Assessing vulnerabilities and evaluating computer system security
• 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: G06F 2221/2149 Restricted operating environment

Abstract

Methods for enabling database privileges are provided. The methods eliminate strict dependency on tradition password, or “secret” based security systems. Instead, database privileges are enabled based on verifying information stored in one or more frames of a call stack corresponds to trusted security logic. In another embodiment, database privileges are enabled based on policies identified in the trusted security logic. The methods and techniques described herein provide a flexible and extensible mechanisms for verifying that trusted security logic has been executed prior to enabling database privileges.

Claims

1. A method for enabling privileges comprising:

establishing a session on behalf of a user;

receiving a request to enable database privileges for the user;

upon receipt of the request to enable database privileges, verifying trusted security logic has previously been executed, wherein the act of verifying the trusted security logic comprises verifying a proxy user and checking a call stack; and

enabling database privileges for the user if the trusted security logic has previously been executed and is contained in one or more frames of the call stack.

2. The method of claim 1 further comprising:

storing call information in one or more frames of the call stack; and

wherein

the act of verifying further comprises determining whether the one or more frames of the call stack corresponds to the trusted security logic.

3. The method of claim 1, wherein the act of verifying the trusted security logic further comprises verifying an application name.

4. The method of claim 3, wherein the act of verifying the trusted security logic further includes verifying a security function name.

5. The method of claim 1, wherein the act of verifying trusted security logic further comprises verifying a module name.

6. The method of claim 1, further comprising:

collecting one or more session parameters;

comparing the one or more session parameters against a set of trusted security parameters defined in a security function; and

returning a result indicating whether the one or more session parameters matches the set of trusted security parameters.

7. The method of claim 1, further comprising:

receiving in formation identifying the user;

prompting the user for a password;

authenticating the user based on information stored in an application program; and

associating the user with a role.

8. A system for enabling privileges, wherein the system is implemented at least in part with a processor, the system comprising:

means for establishing a session on behalf of a user;

means for receiving a request to enable database privileges for the user;

means for upon receipt of the request to enable database privileges, verifying trusted security logic has previously been executed, wherein means for verifying the trusted security logic comprises means for verifying a proxy user and checking a call stack; and

means for enabling database privileges for the user if the trusted security logic has previously been executed and is contained in one or more frames of the call stack.

9. The system of claim 8, further comprising:

means for storing call information in one or more frames of the call stack; and

wherein

means for verifying further comprises means for determining whether the one or more frames of the call stack corresponds to the trusted security logic.

10. The system of claim 8, wherein means for verifying the trusted security logic further comprises means for verifying an application name.

11. The system of claim 10, wherein means for verifying the trusted security logic further comprises means for verifying a security function name.

12. The system of claim 8, wherein means for verifying trusted security logic further comprises means for verifying a module name.

13. The system of claim 8, further comprising:

means for collecting one or more session parameters;

means for comparing the one or more session parameters against a set of trusted security parameters defined in a security function; and

means for returning a result indicating whether the one or more session parameters matches the set of trusted security parameters.

14. The system of claim 8, further comprising:

means for receiving information identifying the user;

means for prompting the user for a password;

means for authenticating the user based on information stored in an application program; and

means for associating the user with a role

15. A client-server computer system comprising:

a computer including;

a processor,

a main memory communicatively coupled to the processor; and

a disk storage communicatively coupled to the processor;

a database running on the computer from the main memory, the database further comprising;

one or more data structures stored in the disk storage, and

a call slack stored in the main memory;

an application program coupled to the database and configured to support a user; and

a metadata repository embodied in the one or more data structures stored in the disk storage, the metadata repository comprising trusted security logic;

wherein

the application program is configured to initiate a call to enable database privileges, the call causing information to be stored in one or more frames of the call stack and one or more security functions to be executed; and

wherein

the database is configured to;

verify the call stack comprises one or more frames corresponding to the trusted security logic;

test a proxy user; and

enable database privileges for the user if the trusted security logic is contained in the one or more frames of the call stack.

16. The client-server computer system of claim 15, wherein the application program resides with the database in the computer.

17. The client-server computer system of claim 15, wherein the application program resides on a separate computer communicatively coupled to the database.

18. The client-server computer system of claim 15, wherein the trusted security logic includes a schema name and a security package name.

19. A computer-readable medium that comprises a non-volatile medium or a volatile medium, having stored therein one or more sequences of instruction for enabling privileges, the one or more sequences of instructions causing one or more processors to perform a number of acts, said acts comprising:

establishing a session on behalf of a user;

receiving a request to enable database privileges for the user;

upon receipt of the request to enable database privileges, verifying trusted security logic has previously been executed, wherein the act of verifying the trusted security logic comprises verifying a proxy user and checking a call stack; and

enabling database privileges for the user if the trusted security logic has previously been executed and is contained in one or more frames of the call stack.

20. The computer-readable medium of claim 19, further comprising:

storing call information in one or more frames of the call stack; and

wherein

the act of verifying further comprises determining whether the one or more frames of the call stack corresponds to the trusted security logic.

21. The computer-readable medium of claim 19, wherein the act of verifying the trusted security logic further comprises verifying an application name.

22. The computer-readable medium of claim 21, wherein the act of verifying the trusted security logic further includes verifying a security function name.

23. The computer-readable medium of claim 19, wherein the act of verifying trusted security logic further comprises verifying a module name.

24. The computer-readable medium of claim 19, further comprising:

collecting one or more session parameters;

comparing the one or more session parameters against a set of trusted security parameters defined in a security function; and

returning a result indicating whether the one or more session parameters matches the set of trusted security parameters.

25. The computer-readable medium of claim 19, further comprising:

receiving information identifying the user;

prompting the user for a password;

authenticating the user based on information stored in an application program; and

associating the user with a role.