NON-INVASIVE INSERTION OF PAGELETS

• US 20080077983A1
• 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, Quigley, Thomas
• Granted Patent: US 7,861,290 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. The reverse proxy server can be configured to recognize a specific proxied web application page to indicate a pagelet web application. The pagelet web application code can be obtained from the pagelet web application and a combined presentation produced by inserting the pagelet web application into a specified location in the first web application. This embodiment allows a pagelet web application code to be inserted into a first web application where the first web application code has not been modified prior to the first web application being proxied.

Claims

1. A method comprising:

receiving a user request for a web application at a reverse proxy;

obtaining web application code for a first application;

checking data at the reverse proxy to determine whether to insert a pagelet web application into the first application; and

if there is a match, producing a combined web application including the first web application and the pagelet application.

2. The method of claim 1, wherein the data is in a table at the reverse proxy server.

3. The method of claim 2, wherein the table includes an indication of the web application code and an indication of a pagelet to insert.

4. The method of claim 3, wherein the indication of the web application code is a title of a web page.

5. The method of claim 3, wherein the indication of the web application code is a pattern matching indication.

6. The method of claim 3, wherein the table further includes location information.

7. The method of claim 6, wherein the pagelet is inserted as indicated by the location information.

8. The method of claim 3, wherein the table further includes wrapper code.

9. The method of claim 3, wherein the table further indicates attribute information that can be obtained from the web application code to provide to the pagelet.

10. A reverse proxy to:

receive a user request for a web application at a reverse proxy;

obtain web application code for a first application;

check data at the reverse proxy to determine whether to insert a pagelet web application into the first application; and

if there is a match, produce a combined web application including the first web application and the pagelet application.

11. The reverse proxy of claim 10, wherein the data is in a table at the reverse proxy server.

12. The reverse proxy of claim 11, wherein the table includes indication of the web application code and an indication of a pagelet to insert.

13. The reverse proxy of claim 12, wherein the indication of the web application code is a title of the web application code.

14. The reverse proxy of claim 12, wherein the indication of the web application code is a pattern matching indication.

15. The reverse proxy of claim 12, wherein the table further includes location information.

16. The reverse proxy of claim 15, wherein the pagelet is inserted as indicated by the location information.

17. The reverse proxy of claim 12, wherein the table further includes a wrapper code.

18. The reverse proxy of claim 12, wherein the table further indicates attribute information that can be obtained from the web application code to provide to the pagelet.

19. A reverse proxy server to:

receive user requests for web application;

obtain web application code for a first web application;

determine whether or not the page in the first web application is configured to have a pagelet web application inserted into it;

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

produce a combined presentation.

20. The reverse proxy server of claim 19, wherein a reverse proxy system combines the first web application and second pagelet web application.

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

22. The reverse proxy server of claim 21, 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.

23. The reverse proxy server of claim 19, wherein there is a configuration for a specific proxied web application page specifying that the page should have a pagelet web application inserted.

24. The reverse proxy server of claim 19, wherein there is a configuration for a specific location in the proxied web application page where the pagelet web application should be inserted.

25. The reverse proxy server of claim 19, wherein the reverse proxy server provides HTML of the combination presentation to a user browser.