Non-invasive insertion of pagelets

• US 7,861,290 B2
• Filed: 06/19/2007
• Issued: 12/28/2010
• Est. Priority Date: 09/22/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Quigley, Thomas, Amend, Michael Ryan, Pandrangi, Phani, Hayler, Don L., McDermott, Adrian Peter, Stanko, Joseph A., Meyer, David
• Primary Examiner(s): CHEN, SHIN HON
• Application Number:
  US11/765,394
• Publication Number:
  US 20080077983A1
• Time in Patent Office: 1,288 Days
• Field of Search: 726/12, 715/741
• 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, the obtained code not including any pagelet tags;

determining, based on data at the reverse proxy, that a pagelet web application should be inserted into the first application;

based upon the data at the reverse proxy, the obtained code, or a combination thereof, determining a location in the obtained code to insert the pagelet web application;

inserting the pagelet web application at the determined location of the obtained code; and

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. The method of claim 1, further comprising maintaining a central role repository for the web applications.

11. The method of claim 10, further comprising sending the user role 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.

12. The method of claim 1, wherein there is a configuration for a specific proxied web application page specifying that the page should have a pagelet web application inserted.

13. The method of claim 1, wherein there is a configuration for a specific location in the proxied web application page where the pagelet web application should be inserted.

14. The method of claim 1, wherein the reverse proxy provides HTML of the combination presentation to a user browser.

15. A reverse proxy to:

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

obtain web application code for a first application, the obtained code not including any pagelet tags;

determine, based on data at the reverse proxy, that a pagelet web application should be inserted into the first application;

based upon the data at the reverse proxy, the obtained code, or a combination thereof, determine a location in the obtained code to insert the pagelet web application;

insert the pagelet web application at the determined location of the obtained code; and

produce a combined web application including the first web application and the pagelet application.

16. The reverse proxy of claim 15, wherein the data is in a table at the reverse proxy.

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

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

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

20. The reverse proxy of claim 17, wherein the table further includes location information.

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

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

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

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

25. The reverse proxy of claim 24, 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.

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

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

28. The reverse proxy of claim 15, wherein the reverse proxy provides HTML of the combination presentation to a user browser.

29. A non-transitory computer-readable medium storing instructions that cause a processor to:

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

obtain web application code for a first application, the obtained code not including any pagelet tags;

determine, based on data at the reverse proxy, that a pagelet web application should be inserted into the first application;

based upon the data at the reverse proxy, the obtained code, or a combination thereof, determine a location in the obtained code to insert the pagelet web application;

insert the pagelet web application at the determined location of the obtained code; and

produce a combined web application including the first web application and the pagelet application.

30. The non-transitory computer-readable medium of claim 29, wherein the data is in a table at the reverse proxy.

31. The non-transitory computer-readable medium of claim 30, wherein the table includes indication of the web application code and an indication of a pagelet to insert.

32. The non-transitory computer-readable medium of claim 31, wherein the indication of the web application code is a title of the web application code.

33. The non-transitory computer-readable medium of claim 31, wherein the indication of the web application code is a pattern matching indication.

34. The non-transitory computer-readable medium of claim 31, wherein the table further includes location information.

35. The non-transitory computer-readable medium of claim 34, wherein the pagelet is inserted as indicated by the location information.

36. The non-transitory computer-readable medium of claim 31, wherein the table further includes a wrapper code.

37. The non-transitory computer-readable medium of claim 31, wherein the table further indicates attribute information that can be obtained from the web application code to provide to the pagelet.

38. The non-transitory computer-readable medium of claim 29, wherein a central role repository is maintained for the web applications.

39. The non-transitory computer-readable medium of claim 38, 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.

40. The non-transitory computer-readable medium of claim 29, wherein there is a configuration for a specific proxied web application page specifying that the page should have a pagelet web application inserted.

41. The non-transitory computer-readable medium of claim 29, wherein there is a configuration for a specific location in the proxied web application page where the pagelet web application should be inserted.

42. The non-transitory computer-readable medium of claim 29, wherein the reverse proxy provides HTML of the combination presentation to a user browser.