Dynamic authentication and authorization mechanisms
A computing system architecture includes a token generator communicable with a client token agent. The client token agent is communicable with a client database access agent. A database management system is communicable with the token agent. The database management system is communicable with the client database access agent. A client authorization management system is communicable with the database management system. The client authorization management system stores a list of authorized operations for a client. The list of authorized operations is configured to be changeable during a client login session.
1. A computing system architecture, comprising:
a token generator that generates a token upon receiving a request from a token agent on a client device and returns the token to the token agent;
a database management system in communication with the token generator and receiving the token from the token generator, the database management system using the token to authenticate a user on the client device during a login session for access to the database management system; and
a client authorization system in communication with the token generator and database management system and receiving the token from the token generator, the client authorization system using the token to allow authorization to operations on the database management system by the user, the client authorization system being configured to change allowed authorization to operations on the database management system during the login session without ending the login session;
wherein the token is used both for authenticating the user and for authorizing operations by the user once authenticated during the login session;
wherein the token includes a first portion generated based on an IP address, a second portion based on a time, a third portion based on a random text string, a fourth portion generated based on a random number, and fifth portion generated based on a database access agent.
2. The computing system architecture according to claim 1 , wherein the token is associated with a list of authorized operations stored on the client authorization system and accessible by the database management system.
3. The computing system architecture according to claim 2 , wherein the database management system confirms whether the client is authorized to perform each and every requested operation requested during a single client login session by using the list of authorized operations.
4. The computing system architecture according to claim 1 , wherein the token is generated based on, at least partially, an IP address, a time, a random text string, a random number, and a database access agent.
5. The computing system according to claim 1 , wherein the database management system has a processor, the processor performs:
receiving a request from a client for a service;
providing the startup page of the service;
receiving a user ID and password for a login; and
authenticating the login using the token, if the user ID and the password match a record.
6. The computing system according to claim 5 , wherein the processor receives an operation request with the token.
7. The computing; system according to claim 6 , wherein the processor determines whether the operation is authorized by checking the list of authorized operations and grants the operation request if the operation is authorized.