Secure transaction system
First Claim
1. A method comprising:
- receiving a request by a user for access to a first server;
receiving a token at the first server, the token indicating that the user has been authenticated and including a role assigned to the user; and
determining, based at least in part on the role identified in the token, whether the user is permitted to perform a particular transaction in connection with a specified file or application at the first server.
5 Assignments
0 Petitions
Accused Products
Abstract
Techniques for providing secure transactions can include receiving a request for access to a first server by a user. The request includes the user'"'"'s credentials such as biometric information, an electronic certificate, or other information. The user is authenticated based on the credentials, and a token is sent to the first server. The token indicates whether the user has been authenticated and includes criteria about the user. Based on the criteria in the token, the first server can determine whether the user is authorized to perform a particular transaction in connection with a specified file or application at the first server. The user can be re-authenticated prior to allowing the transaction to be completed. Each time the user is authenticated, a time-stamped record can be stored. Encryption can be used to enhance security.
-
Citations
34 Claims
-
1. A method comprising:
-
receiving a request by a user for access to a first server;
receiving a token at the first server, the token indicating that the user has been authenticated and including a role assigned to the user; and
determining, based at least in part on the role identified in the token, whether the user is permitted to perform a particular transaction in connection with a specified file or application at the first server. - View Dependent Claims (2, 3, 4, 5, 11)
-
-
6. A method comprising:
-
receiving a request for access to a first server by a user, the request including credentials of the user;
authenticating the user based on the credentials;
sending a token to the first server, the token indicating whether the user has been authenticated and including criteria about the user; and
determining, based on the criteria in the token, whether the user is permitted to perform a particular transaction in connection with a specified file or application at the first server. - View Dependent Claims (7, 8, 9, 10, 12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A method comprising:
-
receiving a request for access to a first server by a user, the request including biometric credentials of the user;
authenticating the user based on the biometric credentials;
sending a token to the first server, the token indicating whether the user has been authenticated and identifying a role assigned to the user;
determining, based on the role identified in the token, whether the user is authorized to perform a particular transaction in connection with the first server;
re-authenticating the user prior to allowing the transaction to be completed; and
storing time-stamped records of the authentication and re-authentication of the user. - View Dependent Claims (21, 22)
-
-
23. A system comprising:
-
a first server; and
an authentication server configured to;
receive a request for access to the first server by a user, the request including credentials of the user;
authenticate the user based on the credentials;
store a time-stamped record of the authentication; and
send a token to the first server, the token indicating whether the user has been authenticated and including criteria about the user; and
the first server configured to determine, based on the criteria in the token, whether the user is permitted to perform a particular transaction in connection with the first server. - View Dependent Claims (24, 25, 26, 27, 28)
-
-
29. A system comprising:
-
a secure server;
a database for storing a user profile and criteria about the user, the criteria being established by an administrator of the secure server; and
an authentication server configured to;
receive a request for access to the secure server by a user, the request including credentials of the user;
authenticate the user based on the credentials and the user profile stored in the database;
store a time-stamped record of authentication of the user in the database; and
send a token to the secure server, the token indicating whether the user has been authenticated and including the criteria about the user from the database, the secure server configured to use the criteria about the user in the token in conjunction with a business rule established by the administrator to determine whether the user is authorized to perform a particular transaction in connection with a specified file or application at the secure server. - View Dependent Claims (30, 31, 32, 33, 34)
-
Specification