NON INVASIVE CONTEXTUAL AND RULE DRIVEN INJECTION PROXY

• US 20090083726A1
• Filed: 09/09/2008
• Published: 03/26/2009
• Est. Priority Date: 09/20/2007
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Pandrangi, Phani, Lin, Stanley Hsinheng, Quigley, Thomas Doyle, Hayler, Don L., McDermott, Adrian Peter, Meyer, David P., Stanko, Joseph A., Amend, Michael Ryan
• Granted Patent: US 9,548,985 B2
• Time in Patent Office: Days
• US Class Current: 717/171
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers

Abstract

User requests for a web application can be received at a reverse proxy. Web application code for a first application can be obtained. Data can be checked at the reverse proxy to determine whether to insert an element into the first application. If there is a match, a combined web application can be produced, including the first web application and the element.

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 an element into the first application;

wherein the web application code is checked to find an insertion point for the element;

wherein a policy is also checked before the element is inserted in the first application, the policy including checking a role of a user; and

if there is a match of the application code and the policy condition is fulfilled, producing a combined web application including the first web application and the element.

2. The method of claim 1, wherein the element is a pagelet application.

3. The method of claim 1, wherein the element is static HTML.

4. The method of claim 1, wherein the element is a web application.

5. The method of claim 1, wherein a DOM-TREE is used to determine where to insert the element.

6. The method of claim 1, wherein the reveres proxy is further adapted to use roles to determine whether to insert the element.

7. The method of claim 1, wherein the reverse proxy is further adapted to use policies to determine whether to insert the element.

8. The method of claim 1, wherein the reverse proxy is adapted to use user preferences to determine whether to insert the element.

9. The method of claim 1, wherein the data includes an indication of the web application code and an indication of a pagelet to insert.

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

11. 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 element into the first application;

wherein the web application code is checked to find an insertion point for the element;

wherein a policy is also checked before the element is inserted in the first application, the policy including checking a role of a user; and

if there is a match of the application code and the policy condition is fulfilled, produce a combined web application including the first web application and the element.

12. The reverse proxy of claim 11, wherein the element is a pagelet application.

13. The reverse proxy of claim 11, wherein the element is static HTML.

14. The reverse proxy of claim 11, wherein the element is a web application.

15. A reverse proxy to:

receive a user request for a web application;

obtain web application code for a first application;

check data at the reverse proxy to determine whether to insert a element into the first application;

wherein the web application code is checked to find an insertion point for the element

wherein a policy is also checked before the element is inserted in the first application, the policy including checking a role of a user and

if there is a match of the application code and the policy condition is fulfilled, produce a combined web application including the first web application and the element;

wherein a DOM-TREE is used to determine where to insert the element.

16. The reverse proxy of claim 15, wherein the element is a pagelet application.

17. The reverse proxy of claim 15, wherein the element is static HTML.

18. The reverse proxy of claim 15, wherein the element is a web application.

19. 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 element into the first application;

wherein the web application code is checked to find an insertion point for the element

wherein a policy is also checked before the element is inserted in the first application, the policy including checking a role of a user and

if there is a match of the application code and the policy condition is fulfilled, produce a combined web application including the first web application and the element;

wherein the reveres proxy is further adapted to use roles to determine whether to insert the element.

20. The reverse proxy of claim 19, wherein the element is a pagelet application.

21. The reverse proxy of claim 19, wherein the element is static HTML.

22. The reverse proxy of claim 19, wherein the element is a web application.

23. 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 element into the first application;

wherein the web application code is checked to find an insertion point for the element;

wherein a policy is also checked before the element is inserted in the first application, the policy including checking a role of a user; and

if there is a match of the application code and the policy condition is fulfilled, produce a combined web application including the first web application and the element;

wherein the reverse proxy is further adapted to use policies to determine whether to insert the element.