Granted Patent B1

US 7,926,095 · App. 11/800,152 · Granted Apr 12, 2011

Abstract

Claims (76)

1. An efficient authentication method for providing a user access to a primary server and at least one secondary server, said primary server and said at least one secondary server being in a communicative relationship, said method comprising:

(a) entering a username into a client device;

(b) providing said username and a hash key to at least one secondary server;

(c) authenticating said user to said primary server based on said username and a password;

(d) performing a primary hash algorithm on said username and said hash key to produce a primary hashed output code;

(e) performing a secondary hash algorithm on said username and said hash key to produce a secondary hashed output code;

(f) providing said primary hashed output code to the client device;

(g) providing said primary hashed output code from the client device to said at least one secondary server;

(h) comparing said primary hashed output code and said secondary hashed output code at said at least one secondary server; and

(i) authenticating said user to said at least one secondary server based on the results thereof.

2. The method of claim 1 , further comprising providing said primary hashed output code to said at least one secondary server from said primary server.

3. The method of claim 1 , further comprising periodically updating said hash key.

4. The method of claim 1 , wherein performing said primary hash algorithm is performed on said primary server.

5. The method of claim 1 , wherein performing said secondary hash algorithm is performed on said at least one secondary server.

6. The method of claim 1 , further comprising performing a system check.

7. The method of claim 1 being encoded on a non-transitory computer readable medium.

8. An efficient authentication system for primary and secondary servers for providing secure access to a user, said user providing a username and a password, said system comprising:

(a) entering a username and password into a client device;

(b) a primary server having a primary hash algorithm module and an authentication module, the authentication module being operable to receive the username and the password entered into the client device and to authenticate the user at the primary server based on said username and said password;

(c) a secondary server having a secondary hash algorithm module and a hashed output compare module;

(d) said secondary server being configured to receive a hash key and said username;

(e) said primary hash algorithm module having a hash function for generating a primary hashed output code of said username utilizing said hash key, wherein said primary server is operable to provide said primary hashed output code to said client device and said client device being operable to provide said primary hashed output code to said secondary server;

(f) said secondary hash algorithm module having said hash function for generating a secondary hashed output code of said username utilizing said hash key; and

(g) said hashed output compare module being operable to compare said primary hashed output code and said secondary hashed output code whereby said user is authenticated at said secondary server based on the results thereof.

9. The system of claim 8 , said primary server being operable to provide said primary hashed output code to said secondary server.

10. The system of claim 8 , said secondary server being operable to receive ephemeral datum.

11. The system of claim 8 , said secondary server being operable to receive optional parameters.

12. The system of claim 8 , further comprising:

(a) said secondary server being operable to receive ephemeral datum;

(b) said primary hash algorithm module for performing said hash function on said username, said hash key, and said ephemeral datum to produce said primary hashed output code; and

(c) said secondary hash algorithm module for performing said hash function on said username, said hash key, and said ephemeral datum to produce said secondary hashed output code.

13. The system of claim 8 , further comprising:

(a) said secondary server being operable to receive optional parameters;

(b) said primary hash algorithm module for performing said hash function on said username, said hash key, and said optional parameters to produce said primary hashed output code; and

(c) said secondary hash algorithm module for performing said hash function on said username, said hash key, and said optional parameters to produce said secondary hashed output code.

14. The system of claim 8 , further comprising a system check module.

15. The system of claim 8 , further comprising:

(a) a system check module;

(b) said secondary server being operable to receive primary ephemeral datum from said primary server;

(c) said secondary server having secondary ephemeral datum; and

(d) said system check module being operable to compare said primary ephemeral datum to said secondary ephemeral datum.

16. The system of claim 15 , said secondary server being operable to receive said primary ephemeral datum indirectly from said primary server via a client device.

17. The system of claim 8 , further comprising:

(a) a plurality of secondary servers;

(b) each of said plurality of secondary servers being operable to receive said hash key;

(c) each of said plurality of secondary servers being operable to receive said username and said primary hashed output code; and

(d) each of said plurality of secondary servers including:

i. a secondary hash algorithm module having a hash function for generating a secondary hashed output code of said username utilizing said hash key; and

ii. a hashed output compare module being operable to compare said primary hashed output code and said secondary hashed output code whereby said user is authenticated at said secondary server based on the results thereof.

18. The system of claim 8 , further comprising:

(a) a plurality of secondary servers which include said secondary server;

(b) each of said plurality of secondary servers being operable to receive a unique hash key;

(c) said primary hash algorithm module for performing a hash function on one or more usernames which include said username and each said unique hash key to produce a unique primary hashed output code for each unique hash key;

(d) each of said plurality of secondary servers being operable to receive a respective username of said one or more usernames and said unique primary hashed output code corresponding to the received unique hash key; and

(e) each of said plurality of secondary servers including:

i. a respective secondary hash algorithm module having a respective hash function for generating a unique secondary hashed output code of said respective username utilizing said unique hash key; and

ii. a respective hashed output compare module being operable to compare said unique primary hashed output code and said unique secondary hashed output code whereby said user is authenticated on at least one of the secondary servers based on the results thereof.

19. An efficient authentication method for providing access to a secondary server in response to authenticating a user at a remote primary server, comprising:

(a) receiving from the remote primary server, a username for authenticating the user at the remote primary server;

(b) receiving a primary hashed output code from a client device configured for entering the username wherein the client device received the primary hashed output code from the remote primary server;

(c) providing the secondary server with a hash key;

(d) performing a hash algorithm at the secondary server on the username using the hash key to produce a secondary hashed output code;

(e) comparing the primary hashed output code and the secondary hashed output code to generate a result based on the comparison; and

(f) providing access to the secondary server based on the result.

20. The method of claim 19 , wherein the primary hashed output code is generated by performing the hash algorithm on the username using the hash key.

21. The method of claim 20 , wherein the primary hashed output code is generated by the remote primary server, wherein providing the secondary server with the hash key further comprises receiving the hash key from the remote primary server.

22. The method of claim 19 , further comprising periodically updating the hash key at the secondary server.

23. The method of claim 19 , further comprising:

(a) receiving ephemeral data from the primary server at the secondary server; and

(b) wherein performing the hash algorithm at the secondary server on the username using the hash key to produce a secondary hashed output code further comprises utilizing the ephemeral data to perform the hash algorithm.

24. A secondary server operable to provide access to a user in response to authenticating the user at a remote primary server, the secondary server comprising:

(a) a link for a communicative relationship with the remote primary server, the link being operable to receive a username for authenticating the user at the remote primary server and a primary hashed output code of the username, wherein the link is operable to receive the primary hashed output code from a client device configured for entering the username and the client device received the primary hashed output code from the remote primary server;

(b) a hash algorithm module for performing a hash algorithm on the username utilizing the hash key to generate a secondary hashed output code; and

(c) a hashed output compare module for comparing the primary hashed output code and the secondary hashed output code to determine whether to provide the user access to the secondary server.

25. The method of claim 24 , wherein the primary hashed output code is generated by performing the hash algorithm on the username using the hash key.

26. The method of claim 1 , further comprising receiving a username, a password, and a hash key at said primary server.

Assignments (20)