| CPC H04L 63/102 (2013.01) [G06F 9/451 (2018.02); H04L 63/08 (2013.01); H04L 63/108 (2013.01)] | 19 Claims |

|
1. A method performed by a system, wherein the system comprises a server for providing an application to a user, an access permission database accessible by the server for storing permanent access permissions for the user, and a memory accessible by the server and storing temporary access permissions for the user while the application is executing, the method comprising:
retrieving the permanent access permissions for the user from the access permission database;
determining the temporary access permissions for the user based on the permanent access permissions and an authentication of the user, wherein the temporary access permissions is an attribute-based authorization based on one or more policies created to determine a non-role-based authorization the user has within the application and the one or more policies fit into a pattern for the application;
storing the temporary access permissions in the memory;
providing a user interface including only actions that are permitted for the user corresponding to the temporary access permissions;
receiving an event, the event comprising one selected from a group consisting of a change in the user's permanent access permissions, a change to a scope limitation of the user, a change to a time duration limitation of the user;
dynamically modifying at least one of the temporary access permissions for the user based on the event, wherein an event handler applies to the user at least one selected from a group of a scope limited access control permission and a temporally limited access control permission;
providing an authorization process that determines whether a request from the user interface is authorized before processing the request from an administrator, using the temporary access permissions, wherein the determination is based on the pattern, and the attribute-based authorization provides a level of authority that is tied to the one or more policies associated with the application and is independent of the user roles within the organization's hierarchy or application; and
modifying the actions displayed on the user interface based on processing the request wherein the application comprises an administration application configured to expand, create, or limit role-based access permissions without having to add new roles or updates to a front end application, which allows configurable permutations of roles per user and per component as the application evolves over time.
|