Credential mapping of WebLogic and database user ids

• US 20060156023A1
• Filed: 04/18/2005
• Published: 07/13/2006
• Est. Priority Date: 01/13/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Luo, Fei, Srivastava, Rahul
• Granted Patent: US 7,788,497 B2
• Time in Patent Office: Days
• US Class Current: 713/182
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

A connection pool can use a credential mapper to map credentials for an application server into a credential to use with the database management system. This can allow objects such as an Enterprise Java Bean to access the database with more specific credentials than the anonymous connection pool connection user name/password.

Claims

1. An application server comprising:

a connection pool operably connected to a database, wherein at least some connections using the connection pool to connect to the database use a credential mapper; and

the credential mapper adapted to map at least one credential for the application server into at least one credential for the database.

2. The application server of claim 1, wherein the at least one credential for the database indicates a user to a greater specificity than an anonymous connection pool connection.

3. The application server of claim 1, wherein threads on the application server include a security context.

4. The application server of claim 3, wherein the security context of a thread includes the at least one credential for the application server.

5. The application server of claim 1, wherein the connection pool is a JDBC connection pool.

6. The application server of claim 1, wherein some credentials for the database obtained from the credential mapper allow greater access to elements of the database than other credentials for the database obtained from the credential mapper.

7. The application server of claim 1, wherein the at least one credential for the application server includes a user name and password.

8. The application server of claim 1, wherein the at least one credential for the database includes a user name and password.

9. The application server of claim 1, wherein an EJB access the database through connection pool using the at least one credential for the database obtained from the credential mapper.

10. The application server of claim 1, wherein a thread for the EJB has a security context having the at least one credential for the application server that is mapped to at least one credential for the database using the credential mapper.

14. The application server of claim 1, wherein the at least one credential for the application server includes a user name and password.

11. An application server comprising:

threads with an associated security context, at least some of the threads accessing a database using at least one credential for the database from a credential mapper; and

the credential mapper adapted to map at least one credential from the security context into the at least one credential for the database.

12. The application server of claim 11, wherein threads use a connection pool to connect to the database.

13. The application server of claim 11, wherein some credentials for the database obtained from the credential mapper allow greater access to elements of the database than other credentials for the database obtained from the credential mapper.

15. A connection pool operably connected to a database, wherein at least some connections using the connection pool to connect to the database map at least one credential for an application server into at least one credential for the database.

16. The connection pool of claim 15, wherein the mapping is done by a credential mapper.

17. The connection pool of claim 15, wherein the at least one credential for the database indicates a user to a greater specificity than an anonymous connection pool connection.

18. The connection pool of claim 15, wherein threads on the application server include a security context.

19. The connection pool of claim 18, wherein the security context of a thread includes the at least one credential for the application server.

20. The connection pool of claim 15, wherein the connection pool is a JDBC connection pool.