System, process and article for conducting authenticated transactions

• US 20040139028A1
• Filed: 11/26/2003
• Published: 07/15/2004
• Est. Priority Date: 03/23/2001
• Status: Abandoned Application

• Current Assignee: Powerfish Incorporated
• Original Assignee: Powerfish Incorporated
• Inventors: Fishman, Jayme Matthew, Rigney, Patrick Heinrich
• Application Number:
  US10/723,657
• Publication Number:
  US 20040139028A1
• Time in Patent Office: Days
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/346 Cards serving only as information carrier of service
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0838 using one-time-passwords
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32

Abstract

A system, process and articles for authentication of a party in transaction using authentication information embedded in a physical medium in the possession of the party plus a password or other personal code of party that are compared against corresponding information in a data base by an authentication server through comparison of one-use tokens generated in parallel from said embedded and personal codes.

Claims

1. A system for authentication of a party comprising:

an authentication server associating a unique set of information with said party, said unique set including at least a unique ordered set of information randomly generated;

responsive to receipt of identifying information of said party to determine by random generation values of one or more prescribed parameters to define an ordered subset of said ordered set, to transmit said values, to generate a first token from said ordered subset, to compare said first token to a second token received in response to said transmission, and upon a match, to authenticate said party; and

a separate processor operated by said party adapted to read locally a storage medium containing a copy of said unique set of information associated by said server with said party, to transmit to said server said identifying information, to receive said values from said server, to apply said values to define an ordered subset of said copy, and to transmit said second token generated from said ordered subset of said copy.

2. The system of claim 1 wherein said first token includes personal code known to said party and stored and associated with said party at said server and said second token identically includes said personal code entered by said party at said separate processor.

3. The system of claim 1 wherein said server further comprises means for, upon said match, generating and storing a transaction token and transmitting to said processor said transaction token;

said system further comprising an authentication-seeking entity adapted to receive from said processor said transaction token, to transmit said transaction token to said server, and to receive from said server authentication upon match by said server of said stored transaction token with said transmitted transaction token.

4. The system of claim 1 further comprising an authentication-seeking entity adapted to receive from said processor said second token, to transmit said second token to said server, and to receive from said server authentication upon match by said server of said first token.

5. An authentication server associating a unique set of information with a party to be authenticated, said unique set including at least a unique ordered set of information randomly generated;

said server responsive to receipt of identifying information of said party to determine by random generation values of one or more prescribed parameters to define an ordered subset of said ordered set, to transmit said values, to generate a first token from said ordered subset, to compare said first token to a second token received in response to said transmission, and upon a match, to authenticate said party.

6. The authentication server of claim 5 wherein said first token includes personal code known to said party and stored and associated at said server with said party.

7. A processor operated by a party to be authenticated, said processor adapted to read locally a storage medium containing a copy of a unique set of information associated by a separate authentication server with said party, to transmit to said server information identifying said party, to receive from said server values of one or more prescribed parameters to define an ordered subset of said copy, and to transmit to said server a token generated from said ordered subset of said copy.

8. The processor of claim 7 wherein said token includes personal code known to said party and stored and associated with said party at said server, said processor further comprising means for receiving entry by said party of said personal code.

9. A computer program product for server-side authentication of a party, said computer program product residing on a computer-readable medium comprising instructions for causing a computer:

to associate a unique set of information with a party to be authenticated, said unique set including at least a unique ordered set of information randomly generated;

to receive identifying information of said party;

to determine in response to such receipt by random generation values of one or more prescribed parameters to define an ordered subset of said ordered set;

to transmit said values;

to generate a first token from said ordered subset;

to receive a second token;

to compare said first token to a second token received in response to said transmission; and

, upon a match, to authenticate said party.

10. The computer program product of claim 9 wherein said unique set of information associated with said party further comprises personal code known to said party and said instructions further comprise instructions to generate said first token from both said ordered subset and said personal code.

11. A computer program product for client-side authentication of a party, said computer program product residing on a computer-readable medium comprising instructions for causing a computer:

to read locally a storage medium containing a copy of a unique set of information associated by a separate authentication server with said party;

to transmit to said server information identifying said party;

to receive from said server values of one or more prescribed parameters to define an ordered subset of said copy;

to generate a token from said ordered subset of said copy; and

to transmit to said server said token.

12. The computer program product of claim 11 further comprising instructions:

to receive entry by said party of personal code stored and associated with said party at said server; and

to generate said token from both said ordered subset and said entered personal information.

13. A process for authenticating a party comprising selection at a central location of a randomly selected portion of random information uniquely associated with said party, parallel selection at a party location separate from said central location an identical portion of a putatively identical copy of said information issued to and possessed by said party, and comparison at said central location of a first token uniquely generated from said randomly selected portion with a second token uniquely generated from said identically selected portion.

14. The process of claim 13 wherein said first token includes personal code known to said party and stored and associated with said party at said central location and said second token identically includes said personal code entered by said party at said separate location.

15. A process for authenticating a party comprising the steps of:

(a) accessing by said party through a client computer of an authentication server that has stored random information uniquely associated with said party, a copy of which was previously provided to said party and accessible at the client side;

(b) generating by said server or said client at least one random value for an authentication session of a parameter for selecting an ordered subset of said stored random information;

(c) transmitting by said server or client respectively to said client or server said generated value;

(d) applying by said client said generated value or values to select an ordered subset of said copy information;

(e) generating by said client from said ordered subset of copy information a client-side party-authenticating token;

(f) applying by said server of said generated value or values to select an ordered subset of said stored information;

(g) generating by said server from said ordered subset of stored information a server-side party-authenticating token;

(h) transmitting by said client to said server said client-side token or by said server to said client said server-side token; and

(i) comparing by said server said client-side token with said server-side token or by said client said server-side token with said client-side token.

16. The process of claim 15 wherein step (b) comprises the steps of generating random values for an offset, a length and a shift;

and steps (e) and (g) each comprise the step of applying a specified one-way hashing algorithm to generate respectively said client-side and server-side party-authenticating tokens.

17. The process of claim 15 wherein a copy of personal code known to said party is stored and associated with said party at said server and wherein

step (e) further comprises the steps of (I) concatenating said ordered subset of copy information and said personal code entered by said party and (II) applying a specified one-way hashing algorithm to generate said client-side party-authenticating token;

and

step (g) further comprises the steps of (I) concatenating said ordered subset of stored random information and said personal code copy and (II) applying said specified one-way hashing algorithm to generate said server-side party-authenticating token.

18. The process of claim 17 wherein step (b) comprises the steps of generating random values for an offset, a length and a shift.

19. The process of claim 18 wherein step (b) further comprises selection of a one-way hash algorithm.

20. The process of claim 15 wherein a copy of personal code known to said party is stored and associated with said party at said server and wherein

step (e) further comprises the steps of (I) dividing said ordered subset of copy information into first and second portions;

(II) concatenating each of said first and second portions with said personal code entered by said party;

(III) applying a specified one-way hashing algorithm to said concatenation of said first portion to generate said client-side party-authenticating token; and

(IV) applying said specified one-way hashing algorithm to said concatenation of said second portion to generate a second client-side party-authenticating token;

step (g) further comprises the steps of (I) dividing said ordered subset of stored random information into first and second portions corresponding to said first and second portions of step (b);

(II) concatenating each of said first and second portions of this step with said personal code copy;

(III) applying said specified one-way hashing algorithm to said concatenation of said first portion to generate said server-side party-authenticating token; and

(IV) applying said specified one-way hashing algorithm to said concatenation of said second portion to generate a second server-side party-authenticating token;

step (h) is performed by said client;

step (i) is performed by said server; and

, wherein, if step (i) results in a match, said process further comprises the steps of

(j) transmitting by said server to said client said second server-side token; and

(k) comparing by said client of said server-side token with said client-side token.

21. The process of claim 20 wherein step (b) comprises the steps of generating random values for an offset, a length and a shift.

22. The process of claim 21 wherein step (b) further comprises selection of a one-way hash algorithm.

23. The process of claim 15 applied to authenticating said party to an authentication-seeking entity in a transaction wherein, if step (i) results in a match, said process further comprises the steps of

(j) generating by said server a transaction token;

(k) storing at said server a copy of said transaction token associated with said party;

(l) transmitting by said server to said client said transaction token;

(m) transmitting by said client to said authentication-seeking entity said transaction token received from said server;

(n) transmitting by said authentication-seeking entity to said server said transaction token received from said client;

(o) comparing by said server of said transaction token received from said authentication-seeking entity with said copy of said transaction token associated with said party.

24. The process of claim 15 applied to authenticating said party to an authentication-seeking entity in a transaction wherein, if step (i) results in a match, said process further comprises the steps of

(j) generating by said server a server-side transaction authentication token from information associated with said party and stored at said server;

(k) transmitting by said server to said client information to specify parallel generation by said client of a client-side transaction authentication token from corresponding information made available at said client;

(l) generating by said client said client-side transaction token from said corresponding information;

(m) transmitting by said client to said authentication-seeking entity said client-side transaction token;

(n) transmitting by said authentication-seeking entity to said server said client-side transaction token received from said client;

(o) comparing by said server of said client-side transaction token received from said authentication-seeking entity with said server-side transaction token associated with said party.

25. The process of claim 15 applied to authenticating work product that said party creates or modifies using said client computer wherein, if step (i) results in a match, said process further comprises the steps of

(j) generating by said server a work-product-authentication token;

(k) storing at said server a copy of said work-product-authentication token associated with said party;

(l) attaching to said work product said work-product-authentication token to create a data object stored and movable as authenticated work product;

(m) storing said authenticated work product;

(n) extracting from said authenticated work product a putative work-product authentication token; and

(o) comparing at said server said stored work-product-authentication token with said putative work-product-authentication token.

26. The process of claim 15 applied to authenticating work product that said party creates or modifies using said client computer wherein, if step (i) results in a match, said process further comprises the steps of

(j) generating by said server a server-side work-product-authentication token from information associated with said party and stored at said server;

(k) transmitting by said server to said client information to specify parallel generation by said client of a client-side work-product-authentication token from corresponding information made available at said client;

(l) generating by said client said client-side work-product-authentication token from said corresponding information;

(m) attaching to said work product said client-side work-product-authentication token to create a data object stored and movable as authenticated work product;

(n) storing said authenticated work product;

(o) extracting from said authenticated work product said client-side work-product authentication token; and

(p) comparing at said server said serve-side work-product-authentication token with said client-side work-product-authentication token.

27. The process of claim 15 applied to authenticating said party for access to a restricted resource wherein, if step (i) results in a match, said process further comprises the step of

(j) transmitting by said server authorization to permit said access.

28. The process of claim 15 applied to authenticating said party for access at said client to a restricted resource wherein

step (h) is performed by said server;

step (i) is performed by said client; and

if step (i) results in a match, said process further comprises the step of

(j) permitting by said client of access to said resource.

29. The process of claim 15 applied to authenticating said party for continuing access to a restricted resource wherein said copy is normally separate from and inaccessible by said client except when connected through action of said party and steps (b) through (i) are repeated periodically until step (i) fails to result in a match a predetermined number of times.