CREDENTIAL VAULT ENCRYPTION

• US 20080077982A1
• Filed: 06/19/2007
• Published: 03/27/2008
• Est. Priority Date: 09/22/2006
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Vu, Daniel, Hayler, Don L.
• Application Number:
  US11/765,389
• Publication Number:
  US 20080077982A1
• Time in Patent Office: Days
• US Class Current: 726/12
• CPC Class Codes: G06F 12/1466 Key-lock mechanism
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

Application role mappings can be maintained at a reverse proxy server. When a request for a web application is received at the reverse proxy servers, the proper user role for the web application can be determined at the reverse proxy server. The proper user role can be sent as part of a HTTP header to the web application. The web application can use the user role without doing an independent mapping of the user to a role.

Claims

1. A method comprising:

maintaining application role mappings at a reverse proxy server;

receiving a request for a web application at the reverse proxy server;

determining the proper user role for the web application at the reverse proxy server;

sending the proper user role as part of a HTTP header to the web application;

wherein the web application uses the user role without doing an independent mapping of the user to a role.

2. The method of claim 1, wherein the reverse proxy server interrogates the web application to determine the possible roles.

3. The method of claim 1, wherein administrators can specify which roles the web application supports in the admin UI.

4. The method of claim 1, wherein the reverse proxy server implements policies to determine the web application user roles.

5. The method of claim 1, wherein code for the web application can include a tag to cause the reverse proxy system to insert a second web application into the displayed page.

6. The method of claim 4, wherein the second web application uses independent user roles.

7. The method of claim 5, wherein one of the independent user roles is sent in an HTTP header to the second web application.

8. A computer readable medium including code to:

maintaining application role mapping at a reverse proxy server;

receiving a request for a web application at the reverse proxy server; and

determining the proper user role for the web application at the reverse proxy server;

sending the proper user role as part of a HTTP header to the web application;

wherein the web application uses the user role without doing an independent mapping of the user to a role.

9. The computer readable medium of claim 8, wherein the reverse proxy server interrogates the web application to determine the possible roles.

10. The computer readable medium of claim 8, wherein the reverse proxy server implements policies to determine the web application user roles.

11. The computer readable medium of claim 8, wherein code for the web application can include a tag to cause the reverse proxy system to insert a second web application into the displayed page.

12. The computer readable medium of claim 11, wherein the second web application uses independent user roles.

13. The method of claim 12, wherein one of the independent user roles is sent in an HTTP header to the second web application.

14. A method comprising:

maintaining application role mapping at a reverse proxy server;

receiving a request for a web application at the reverse proxy server;

determining the proper user role for the web application at the reverse proxy server;

sending the proper user role as part of a HTTP header to the web application;

wherein the web application uses the role in a presentation to the user without doing an independent mapping of the user to a role;

wherein the request comes from another web application as a result of an active tag in the other web application.

15. The method of claim 14, wherein the reverse proxy server interrogates the web application to determine the possible roles.

16. The method of claim 14, wherein the reverse proxy server implements policies to determine the web application user roles.

17. The method of claim 15, wherein the second web application uses independent user roles.

18. A method comprising:

maintaining of application role mapping at a reverse proxy server;

receiving a request for a web application at the reverse proxy server the reverse proxy server;

determining the proper user role for the web application; and

sending the proper user role as part of a HTTP header to the web application;

wherein the web application uses the role in a presentation to the user without doing an independent mapping of the user to a role;

wherein the reverse proxy server looks up roles for multiple web application that are combined into a single presentation to the user.

19. The method of claim 18, wherein the reverse proxy server interprets the web application to determine the possible roles.

20. The method of claim 18, wherein the reverse proxy server implements policies to determine the web application user roles.

21. The method of claim 18, wherein the multiple web application have independent user roles.