Network-based device authentication system
An authentication system may receive a request signature corresponding to a user request to view secure user information on a user device and generate a server-side signature matching the request signature to authenticate the user device to receive the secure user information without authenticating the user. The request signature may include a device identifier corresponding to the device, a token code generated by the authentication system and stored by the user device, a timestamp corresponding to the transmission time of the request signature, and a version of the device identifier, the token code, and the timestamp encrypted using a signature key provided to the user device by the authentication system. The authentication system may generate the server-side signature using the timestamp and stored copies of the device identifier, the token code, and the signature key.
1. A system comprising:
a processor; and
a memory comprising instructions that are executable by the processor for causing the processor to:
receive user authentication information from a user device;
authenticate the user device using the user authentication information;
based on authenticating the user device:
generate a token code,
determine a signature key,
transmit the token code and the signature key to the user device, and
associate a device identifier with the token code and the signature key in a database, wherein the device identifier corresponds to the user device;
subsequent to transmitting the signature key to the user device, receive a request for secure information from the user device, wherein the request includes:
the token code,
the device identifier corresponding to the user device,
and
an encrypted signature including a version of the device identifier and the token code encrypted by the user device using the signature key; and
subsequent to receiving the request:
generate a server-side signature that includes a version of the device identifier and the token code encrypted using a stored signature key retrieved from the database or another database;
compare the server-side signature to the encrypted signature in the request to determine a signature match; and
based on determining the signature match, authenticate the user device to access the secure information.
2. The system of claim 1 , wherein the memory further comprises instructions that are executable by the processor for causing the processor to:
retrieve a stored token code from the database based on a correlation between the device identifier and the stored token code in the database, wherein the server-side signature is generated based at least in part on the stored token code.
3. The system of claim 1 , wherein the memory further comprises instructions that are executable by the processor for causing the processor to:
determine a user identifier associated with the device identifier in the database, the user identifier corresponding to a user of the user device; and
retrieve the secure information from the database based on a correlation between the user identifier and the secure information in the database.
4. The system of claim 1 , wherein the memory further comprises instructions that are executable by the processor for causing the processor to generate the server-side signature by calculating a keyed-hash message authentication code (“HMAC”) using the device identifier and the token code in combination with the stored signature key.
5. The system of claim 1 , wherein the memory further comprises instructions that are executable by the processor for causing the processor to, subsequent to authenticating the user device to access the secure information:
determine an information type identifier associated with the device identifier in the database, wherein the information type identifier indicates a specific type of data to transmit to the user device in response to the request; and
transmit the specific type of data to the user device as at least a portion of the secure information.
6. A method comprising:
receiving, by a processor, user authentication information from a user device;
authenticating, by the processor, the user device using the user authentication information;
based on authenticating the user device:
generating, by the processor, a token code,
determining, by the processor, a signature key,
transmitting, by the processor, the token code and the signature key to the user device, and
associating, by the processor, a device identifier with the token code and the signature key in a database, wherein the device identifier corresponds to the user device;
subsequent to transmitting the signature key to the user device, receiving, by the processor, a request for secure information from the user device, wherein the request includes:
the token code,
the device identifier corresponding to the user device,
and
an encrypted signature generated by the user device by encrypting the device identifier and the token code using the signature key; and
subsequent to receiving the request:
generating, by the processor, a server-side signature by encrypting the device identifier and the token code using a stored signature key retrieved from the database or another database;
comparing, by the processor, the server-side signature to the encrypted signature in the request to determine a signature match; and
based on determining the signature match, authenticating, by the processor, the user device to access the secure information.
7. The method of claim 6 , further comprising retrieving a stored token code from the database based on a correlation between the device identifier and the stored token code in the database, wherein the server-side signature is generated based at least in part on the stored token code.
8. The method of claim 6 , further comprising:
determining a user identifier associated with the device identifier in the database, the user identifier corresponding to a user of the user device; and
retrieving the secure information from the database based on a correlation between the user identifier and the secure information in the database.
9. The method of claim 6 , further comprising generating the server-side signature by calculating a keyed-hash message authentication code (“HMAC”) using the device identifier and the token code in combination with the stored signature key.
10. The method of claim 6 , further comprising, subsequent to authenticating the user device to access the secure information:
determining an information type identifier associated with the device identifier in the database, wherein the information type identifier indicates a specific type of data to transmit to the user device in response to the request; and
transmitting the specific type of data to the user device as at least a portion of the secure information.
11. A non-transitory computer-readable medium comprising program code that is executable by a processor for causing the processor to:
receive user authentication information from a user device;
authenticate the user device using the user authentication information;
based on authenticating the user device:
generate a token code,
determine a signature key,
transmit the token code and the signature key to the user device, and
associate a device identifier with the token code and the signature key in a database, wherein the device identifier corresponds to the user device;
subsequent to transmitting the signature key to the user device, receive a request for secure information from the user device, wherein the request includes:
the token code,
the device identifier corresponding to the user device,
and
an encrypted signature generated by the user device encrypting the device identifier and the token code using the signature key; and
subsequent to receiving the request:
generate a server-side signature by encrypting the device identifier and the token code using a stored signature key retrieved from the database or another database;
compare the server-side signature to the encrypted signature in the request to determine a signature match; and
based on determining the signature match, authenticate the user device to access the secure information.
12. The non-transitory computer-readable medium of claim 11 , further comprising program code that is executable by the processor for causing the processor to retrieve a stored token code from the database based on a correlation between the device identifier and the stored token code in the database, wherein the server-side signature is generated based at least in part on the stored token code.
13. The non-transitory computer-readable medium of claim 11 , further comprising program code that is executable by the processor for causing the processor to:
determine a user identifier associated with the device identifier in the database, the user identifier corresponding to a user of the user device; and
retrieve the secure information from the database based on a correlation between the user identifier and the secure information in the database.
14. The non-transitory computer-readable medium of claim 11 , further comprising program code that is executable by the processor for causing the processor to generate the server-side signature by calculating a keyed-hash message authentication code (“HMAC”) using the device identifier and the token code in combination with the stored signature key.