User role mapping in web applications
Roles and policies are used to provide display and access to data in a flexible manner. Users and/or web applications can be mapped to user roles that dictate which displays or other application resources are available to the user or application. Roles are assigned to web applications individually, allowing for user roles to be used without requiring an independent mapping of users to roles. In some cases, application roles can be centrally managed, so that presentation systems also avoid the need for an independent mapping of user or application roles.
1. A method comprising:
receiving, by a computer system, a user request for a first web application;
retrieving, by the computer system, markup data for the first web application;
converting, by the computer system, the retrieved markup data into markup fragments containing application markup and at least a first adaptive tag;
interpreting, by the computer system, the first adaptive tag to indicate a pagelet web application;
obtaining, by the computer system, code from the pagelet web application specific to the requesting user;
based upon the obtained pagelet web application code, assembling, by the computer system, a page of the first application from at least data for the pagelet web application and the application markup obtained from the retrieved markup data; and
providing, by the computer system, the page of the first application to the requesting user.
2. The method of claim 1 , wherein a reverse proxy system retrieves the markup data for the first web application.
3. The method of claim 1 , wherein a central role repository is maintained for a plurality of web applications including the first web application.
4. The method 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 method of claim 1 , wherein the adaptive tag includes a namespace.
6. The method of claim 1 , wherein the adaptive tag includes an identifier.
7. A non-transitory machine-readable medium for a computer system, the non-transitory machine-readable medium having stored thereon a series of instructions executable by a processor, the series of instructions comprising:
instructions that cause the processor to receive a user request for a first web application;
instructions that cause the processor to retrieve markup data for the first web application;
instructions that cause the processor to convert the retrieved markup data into markup fragments containing application markup and at least a first adaptive tag;
instructions that cause the processor to interpret the first adaptive tag to indicate a pagelet web application;
instructions that cause the processor to obtain code from the pagelet web application specific to the requesting user;
instructions that cause the processor to, based upon the obtained pagelet web application code, assemble a page of the first application from at least data for the pagelet web application and the application markup obtained from the retrieved markup data; and
instructions that cause the processor to provide the page of the first application to the requesting user.
8. The machine-readable medium of claim 7 , wherein a reverse proxy system retrieves the markup data for the first web application.
9. The machine-readable medium of claim 7 , wherein a central role repository is maintained for a plurality of web applications including the first web application.
10. The machine-readable medium 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 machine-readable medium of claim 7 , wherein the adaptive tag includes a namespace.
12. The machine-readable medium of claim 7 , wherein the adaptive tag includes an identifier.
13. A system comprising:
a processor configured to:
receive a user request for a first web application;
retrieve markup data for the first web application;
convert the retrieved markup data into markup fragments containing application markup and at least a first adaptive tag;
interpret the first adaptive tag to indicate a pagelet web application;
obtain code from the pagelet web application specific to the requesting user;
based upon the obtained pagelet web application code, assemble a page of the first application from at least data for the pagelet web application and the application markup obtained from the retrieved markup data; and
provide the page of the first application to the requesting user.
14. The system of claim 13 , wherein the system retrieves the markup data for the first web application.
15. The system of claim 13 , wherein a central role repository is maintained for a plurality of web applications including the first web application.
16. The system 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 system of claim 13 , wherein the adaptive tag includes a namespace.
18. The system of claim 13 , wherein the adaptive tag includes an identifier.
19. The system of claim 13 , wherein the system further comprises a reverse proxy server.