PAGELETS IN ADAPTIVE TAGS IN NON-PORTAL REVERSE PROXY

• US 20080077981A1
• Filed: 06/19/2007
• Published: 03/27/2008
• Est. Priority Date: 09/22/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Pandrangi, Phani, Hayler, Don L., McDermott, Adrian Peter, Stanko, Joseph A., Meyer, David
• Granted Patent: US 7,861,289 B2
• 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

A reverse proxy server can receive user requests for web applications. Web application code can be obtained for a first web application. A tag in the first web application can be interpreted to indicate a pagelet web application. The pagelet web application code can be obtained from the pagelet web application and a combined presentation produced.

Claims

1. A reverse proxy server adapted to:

receive user requests for web application;

obtain web application code for a first web application;

interpret a tag in the first web application to indicate a pagelet web application;

obtain pagelet web application code from the pagelet web application; and

produce a combined presentation.

2. The reverse proxy server of claim 1, wherein a reverse proxy system combines the first and second pagelet web applications.

3. The reverse proxy server of claim 1, wherein a central role repository is maintained for the web applications.

4. The reverse proxy server of claim 3, wherein the user role is sent to the web applications in an HTTP header so that the web application need not do an independent mapping of the user to a role.

5. The reverse proxy server of claim 1, wherein the tag includes a namespace.

6. The reverse proxy server of claim 1, wherein the tag includes an ID.

7. A reverse proxy server proxy server adapted to:

receive user requests for web application;

obtain web application code for a first web application;

interpret a tag in the first web application to indicate a non pagelet web application;

obtain non pagelet web application code from the non pagelet web application and produce a combined presentation.

8. The reverse proxy server of claim 7, wherein a reverse proxy system combines the first and second pagelet web applications.

9. The reverse proxy server of claim 7, wherein a central role repository is maintained for the web applications.

10. The reverse proxy server of claim 9, wherein the user role is sent to the web applications in an HTTP header so that the web application need not do an independent mapping of the user to a role.

11. The reverse proxy server of claim 7, wherein the tag includes a namespace.

12. The reverse proxy server of claim 7, wherein the tag includes an ID.

13. A reverse proxy server adapted to:

receive user requests for web application;

obtain web application code for a first web application;

interpret a tag in the first web application to indicate a pagelet web application;

obtain pagelet web application code from the pagelet web application;

and produce a combined presentation;

wherein the reverse proxy server provides HTML of the combination presentation to a user browser.

14. The reverse proxy server of claim 13, wherein a reverse proxy system combines the first and second pagelet web applications.

15. The reverse proxy server of claim 13, wherein a central role repository is maintained for the web applications.

16. The reverse proxy server of claim 15, wherein the user role is sent to the web applications in an HTTP header so that the web application need not do an independent mapping of the user to a role.

17. The reverse proxy server of claim 13, wherein the tag includes a namespace.

18. The reverse proxy server of claim 13, wherein the tag includes an ID.