Unique credentials verification

Patent metadata

Field	Value
Publication number	US-9300643-B1
Application number	US-201213534850-A
Country	US
Kind code	B1
Filing date	Jun 27, 2012
Priority date	Jun 27, 2012
Publication date	Mar 29, 2016
Grant date	Mar 29, 2016

Abstract

Systems and methods for verifying the uniqueness of requested authentication credentials among one or more entities may include one or more verification credential servers configured to receive information associated with the requested authentication credentials and determine if the requested authentication credentials are unique.

First claim

That which is claimed:

1. A system, comprising:
at least one memory that stores computer-executable instructions;
at least one computer processor configured to access the at least one memory, wherein the at least one computer processor is configured to execute the computer-executable instructions to:
receive an authentication credential verification request comprising a first hash of a requested authentication credential associated with a first domain and a user, wherein the authentication credential verification request does not include an identity of the user or the requested authentication credentials in plain text;
generate a second hash associated with the requested authentication credential using the first hash;
access a database storing one or more stored hashes associated with corresponding respective authentication credentials associated with one or more second domains;
compare the second hash to the one or more stored hashes on the database to determine that the second hash does not match the one or more stored hashes;
determine based at least in part on the comparing that the requested authentication credential is not being used by the user as an authentication credential at the one or more second domains;
transmit a message indicating that the requested authentication credential is not being used; and
update, based at least in part on the determination that the requested authentication credential is not being used, the database with the second hash associated with the requested authentication credential.

2. The system of claim 1 , wherein receiving the authentication credential verification request is responsive to the user requesting the requested authentication credential from the first domain.

3. The system of claim 1 , wherein the requested authentication credential comprises at least one of: (i) one or more logins; (ii) one or more passwords; (iii) one or more images; (iv) one or more sounds; (v) one or more personal information; or (vi) one or more biometric information.

4. The system of claim 1 , wherein the first hash associated with the requested authentication credential comprises at least one of: (i) an encryption of the requested authentication credential; (ii) an encryption of a portion of the requested authentication credential; (iii) a hash of the requested authentication credential; (iv) a hash of a portion of the requested authentication credential; (v) a one-way hash of the requested authentication credential; (vi) a one-way hash of a portion of the requested authentication credential.

5. The system of claim 1 , wherein comparing the second hash to the one or more stored hashes on the database comprises extracting the first hash associated with the requested authentication credential from the authentication credential verification request.

6. The system of claim 1 , wherein determining that the authentication credential is not being used by the user as an authentication credential at the one or more second domains comprises determining that the second hash associated with the requested authentication credential does not match the hashes stored on the database.

7. The system of claim 1 , wherein the at least one processor is further configured to randomly generate and transmit a message to expire the requested authentication credential.

8. A method, comprising:
receiving, by one or more credential verification servers comprising at least one computer processor, an authentication credential verification request comprising a first hash associated with a first entity, wherein the authentication credential verification request does not include an identity of a user associated with the authentication credential verification request or requested authentication credentials associated with the authentication credential verification request in plain text;
generating a second hash using the first hash;
comparing, by the one or more credential verification servers, the second hash to one or more stored hashes associated with one or more second entities to determine that the second hash does not match the one or more stored hashes;
determining, by the one or more credential verification servers, based at least in part on the comparing, that the requested authentication credential is not unique among authentication credentials associated with the one or more stored hashes; and
transmitting, by the one or more credential verification servers, a message indicating that the requested authentication credential is not unique.

9. The method of claim 8 , wherein the authentication credential verification request further comprises at least one contact information associated with a user, wherein the contact information comprises at least one of: (i) an electronic mail address, (ii) a mobile phone number; (iii) a text message number; (iv) a phone number; (v) a mailing address; or (vi) a facsimile number.

10. The method of claim 9 , further comprising sending, by the one or more credential verification servers, a second message using the contact information to the user indicating that the requested authentication credentials are not in compliance with a compliance policy.

11. The method of claim 8 , wherein the first hash associated with a requested authentication credential is a one-way hash.

12. The method of claim 8 , wherein the second hash associated with a requested authentication credential is a one-way hash of the first hash associated with the requested authentication credential.

13. The method of claim 8 , further comprising determining, by the one or more credential verification servers, that a query rate associated with the first entity is less than a predetermined threshold.

14. The method of claim 13 , wherein determining the query rate comprises determining, by the one or more credential verification servers, a number of queries associated with the first entity over a predetermined time period.

15. The method of claim 8 , wherein the requested authentication credential comprises at least one of: (i) one or more logins; (ii) one or more passwords; (iii) one or more images; (iv) one or more sounds; (v) one or more personal information; or (vi) one or more biometric information.

16. The method of claim 8 , wherein the message indicating that the requested authentication credential is not unique comprises a message to expire the requested authentication credentials.

17. The method of claim 8 , wherein determining that that the requested authentication credential is not unique comprises determining that the second hash associated with the requested authentication credentials matches at least one of the one or more stored hashes associated with one or more second entities.

18. The method of claim 17 , further comprising transmitting a message to expire authentication credentials associated with the at least one of the one or more stored hashes matching the second hash.

19. At least one non-transitory computer-readable medium comprising computer-executable instructions that, when executed by one or more processors, executes a method comprising:
receiving an authentication credential verification request associated with a first entity comprising a first hash associated with a requested authentication credential and contact information associated with a user, wherein the authentication credential verification request does not include an identity of the user or the requested authentication credentials in plain text;
determining a second hash using the first hash;
comparing the second hash to one or more stored hashes ass

Assignees

• Doane Andrew J
• Amazon Tech Inc

Inventors

• Doane Andrew J

Classifications

• H04L63/08 Primary

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• H04L63/0861

  using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231) · CPC title

• H04L63/0853

  using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234) · CPC title