Pagelets in adaptive tags in non-portal reverse proxy

• US 7,861,289 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: Meyer, David, Pandrangi, Phani, Hayler, Don L., McDermott, Adrian Peter, Stanko, Joseph A.
• Primary Examiner(s): CHEN, SHIN HON
• Application Number:
  US11/765,380
• Publication Number:
  US 20080077981A1
• 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. 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 a user request for a web application;

responsive to the user request, obtain web application code for a first web application;

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

obtain a set of roles used by the pagelet web application;

based on the roles used by the pagelet web application, determine that the requesting user is authorized to access the pagelet application;

obtain pagelet web application code from the pagelet web application;

produce a combined presentation of the first web application and the pagelet web application; and

provide the combined presentation of the first web application and the pagelet web application to the requesting user.

2. The reverse proxy server of claim 1, further adapted to combine the first web application and a second pagelet web application.

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 1, further adapted to send a user role of the requesting user 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. The reverse proxy server of claim 1, further adapted to:

receive a user request for a second web application;

obtain web application code for the second web application;

interpret a tag in the second 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 of the second web application and the non pagelet web application; and

provide the combined presentation of the second web application and the non pagelet web application to the requesting user.

8. The reverse proxy server of claim 7, further adapted to combine the first web application and a second pagelet web applications application.

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

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

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

12. The reverse proxy server of claim 1, wherein the reverse proxy server provides HTML of the combined presentation to a user browser.

13. The method of claim 1, further comprising the step of providing HTML of the combined presentation to a user browser.

14. A method comprising:

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

responsive to the user request, obtaining web application code for a first web application;

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

obtaining a set of rules used by the pagelet web application;

based on the roles used by the pagelet web application, determining that the requesting user is authorized to access the pagelet application;

obtaining pagelet web application code from the pagelet web application;

producing a combined presentation of the first web application and the pagelet web application; and

providing the combined presentation of the first web application and the pagelet web application to the requesting user.

15. The method of claim 14, further comprising:

receiving a user request for a second web application;

obtaining web application code for the second web application;

interpreting a tag in the second web application to indicate a non pagelet web application;

obtaining non pagelet web application code from the non pagelet web application;

producing a combined presentation of the second web application and the non pagelet web application; and

providing the combined presentation of the second web application and the non pagelet web application to the requesting user.

16. The method of claim 15, further comprising combining the first web application and a second pagelet web application.

17. The method 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.

18. The method of claim 15, wherein the tag includes a namespace.

19. The method of claim 15, wherein the tag includes an ID.

20. The method of claim 14, further comprising:

sending a user role of the requesting user 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.

21. The method server of claim 14, further comprising combining the first web application and a second pagelet web application.

22. The method of claim 14, further comprising maintaining a central role repository for the web applications.

23. The method of claim 14, wherein the tag includes a namespace.

24. The method of claim 14, wherein the tag includes an ID.

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

receive a user request for web application;

responsive to the user request, obtain web application code for a first web application;

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

obtain a set of rules used by the pagelet web application;

based on the roles used by the pagelet web application, determine that the requesting user is authorized to access the pagelet application;

obtain pagelet web application code from the pagelet web application;

produce a combined presentation of the first web application and the pagelet web application; and

provide the combined presentation of the first web application and the pagelet web application to the requesting user.

26. The computer readable medium of claim 25, said instructions further causing the processor to:

receive a user request for a second web application;

obtain web application code for the second web application;

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

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

produce a combined presentation of the second web application and the non pagelet web application; and

provide the combined presentation of the second web application and the non pagelet web application to the requesting user.

27. The computer readable medium of claim 26, said instructions further causing the processor to combine the first web application and a second pagelet web application.

28. The computer readable medium of claim 26, 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.

29. The computer readable medium of claim 26, wherein the tag includes a namespace.

30. The computer readable medium of claim 26, wherein the tag includes an ID.

31. The computer readable medium of claim 25, said instructions further causing the processor to send a user role of the requesting user 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.

32. The computer readable medium of claim 25, said instructions further causing the processor to combine the first web application and a second pagelet web application.

33. The computer readable medium of claim 25, said instructions further causing the processor to maintain a central role repository for the web applications.

34. The computer readable medium of claim 25, wherein the tag includes a namespace.

35. The computer readable medium of claim 25, wherein the tag includes an ID.

36. The computer readable medium of claim 25, said instructions further causing the processor to provide HTML of the combined presentation to a user browser.