User authentication based on other applications
First Claim
1. A system for authenticating a user, the system comprising:
- a memory;
at least one hardware processor; and
a module stored in memory comprising computer instruction code executable by the at least one hardware processor, and structured to cause the at least one hardware processor to;
receive a first request to execute a first action associated with a first application;
determine that execution of the first action requires user authentication;
request one or more authentication credentials from the user;
receive a first authentication credential associated with the first action, wherein the first authentication credential is associated with a zero authentication, a soft authentication, or a hard authentication, wherein receiving the hard authentication comprises enabling the user to execute all actions associated with the first application, wherein receiving the soft authentication comprises enabling the user to execute to at least one action associated with the first application, wherein receiving zero authentication comprises denying the user access to at least one action associated with the first application;
validate the first authentication credential, thereby resulting in a successful validation of the received first authentication credential;
in response to the successful validation, execute the first action;
receive a second request to execute a second action associated with a second application, wherein the second request is associated with the execution of the first action;
determine that execution of the second action requires user authentication;
determine a digital footprint of the user based on at least the first action executed by the user, wherein the digital footprint of the user comprises one or more previous actions executed by the user, wherein the one or more actions executed by the user comprises the execution of the first action, wherein the digital footprint is used as a second authentication credential required to access the second application; and
validate the digital footprint indicating that the first action executed by the user is successfully authenticated;
in response to the successful validation of the digital footprint, execute the second action.
1 Assignment
0 Petitions
Accused Products
Abstract
The present invention includes a system for authenticating a second action based on a first action, wherein the system is configured to: receive a first request to execute a first action associated with a first application; determine that execution of the first action requires user authentication; request one or more authentication credentials from the user; receive a first authentication credential associated with the first action; validate the first authentication credential, thereby resulting in a successful validation of the received first authentication credential; in response to the successful validation, execute the first action; receive a second request to execute a second action associated with a second application; determine that execution of the second action requires user authentication; use the successful validation of the first authentication credential to validate a second authentication credential so that the second action may be executed.
-
Citations
15 Claims
-
1. A system for authenticating a user, the system comprising:
-
a memory; at least one hardware processor; and a module stored in memory comprising computer instruction code executable by the at least one hardware processor, and structured to cause the at least one hardware processor to; receive a first request to execute a first action associated with a first application; determine that execution of the first action requires user authentication; request one or more authentication credentials from the user; receive a first authentication credential associated with the first action, wherein the first authentication credential is associated with a zero authentication, a soft authentication, or a hard authentication, wherein receiving the hard authentication comprises enabling the user to execute all actions associated with the first application, wherein receiving the soft authentication comprises enabling the user to execute to at least one action associated with the first application, wherein receiving zero authentication comprises denying the user access to at least one action associated with the first application; validate the first authentication credential, thereby resulting in a successful validation of the received first authentication credential; in response to the successful validation, execute the first action; receive a second request to execute a second action associated with a second application, wherein the second request is associated with the execution of the first action; determine that execution of the second action requires user authentication; determine a digital footprint of the user based on at least the first action executed by the user, wherein the digital footprint of the user comprises one or more previous actions executed by the user, wherein the one or more actions executed by the user comprises the execution of the first action, wherein the digital footprint is used as a second authentication credential required to access the second application; and validate the digital footprint indicating that the first action executed by the user is successfully authenticated; in response to the successful validation of the digital footprint, execute the second action. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A method for authenticating a user, the method comprising:
-
receiving a first request to execute a first action associated with a first application; determining that execution of the first action requires user authentication; requesting one or more authentication credentials from the user; receiving a first authentication credential associated with the first action, wherein the first authentication credential is associated with a zero authentication, a soft authentication, or a hard authentication, wherein receiving the hard authentication comprises enabling the user to execute all actions associated with the first application, wherein receiving the soft authentication comprises enabling the user to execute to at least one action associated with the first application, wherein receiving zero authentication comprises denying the user access to at least one action associated with the first application; validating the first authentication credential, thereby resulting in a successful validation of the received first authentication credential; in response to the successful validation, executing the first action; receiving a second request to execute a second action associated with a second application, wherein the second request is associated with the execution of the first action; determining that execution of the second action requires user authentication; determining a digital footprint of the user based on at least the first action executed by the user, wherein the digital footprint of the user comprises one or more previous actions executed by the user, wherein the one or more actions executed by the user comprises the execution of the first action, wherein the digital footprint is used as a second authentication credential required to access the second application; and validating the digital footprint indicating that the first action executed by the user is successfully authenticated using the first authentication credential; in response to the successful validation of the digital footprint, executing the second action.
-
-
15. A computer program product for authenticating a user, the computer program product comprising a non-transitory computer-readable medium comprising code causing a computer to:
-
receive a first request to execute a first action associated with a first application; determine that execution of the first action requires user authentication; request one or more authentication credentials from the user; receive a first authentication credential associated with the first action, wherein the first authentication credential is associated with a zero authentication, a soft authentication, or a hard authentication, wherein receiving the hard authentication comprises enabling the user to execute all actions associated with the first application, wherein receiving the soft authentication comprises enabling the user to execute to at least one action associated with the first application, wherein receiving zero authentication comprises denying the user access to at least one action associated with the first application; validate the first authentication credential, thereby resulting in a successful validation of the received first authentication credential; in response to the successful validation, execute the first action; receive a second request to execute a second action associated with a second application, wherein the second request is associated with the execution of the first action; determine that execution of the second action requires user authentication; determine a digital footprint of the user based on at least the first action executed by the user, wherein the digital footprint of the user comprises one or more previous actions executed by the user, wherein the one or more actions executed by the user comprises the execution of the first action, wherein the digital footprint is used as a second authentication credential required to access the second application; and validate the digital footprint indicating that the first action executed by the user is successfully authenticated; in response to the successful validation of the digital footprint, execute the second action.
-
Specification