METHOD AND SYSTEM FOR DETERMINING AUTHENTICATION LEVELS IN TRANSACTIONS

• US 20120323717A1
• Filed: 06/15/2012
• Published: 12/20/2012
• Est. Priority Date: 06/16/2011
• Status: Abandoned Application

• Current Assignee: OneID Inc.
• Original Assignee: OneID Inc.
• Inventors: KIRSCH, STEVEN TODD
• Application Number:
  US13/524,748
• Publication Number:
  US 20120323717A1
• Time in Patent Office: Days
• US Class Current: 705/26.1
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/384 using social networks
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 30/0609 Buyer or seller confidence or verification
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/205 involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved negotiation of communication capabilities H04L69/24

Abstract

According to an embodiment of the present invention, a method for determining a transaction authentication level includes receiving transaction information associated with a transaction between a user and a relying party, receiving relying party preferences, and determining a relying party authentication level based on the transaction information and the relying party preferences. The method also includes accessing user preferences, and determining a user authentication level based the transaction information and the user preferences. The method further includes determining the transaction authentication level using the user authentication level and the relying party authentication level.

Claims

1. A method for determining a transaction authentication level, the method comprising:

receiving transaction information associated with a transaction between a user and a relying party;

receiving relying party preferences;

determining a relying party authentication level based on the transaction information and the relying party preferences;

accessing user preferences;

determining a user authentication level based on the transaction information and the user preferences; and

determining the transaction authentication level using the user authentication level and the relying party authentication level.

2. The method of claim 1 wherein the transaction authentication level is determined based on which of the user authentication level and the relying party authentication level is most secure.

3. The method of claim 1 wherein at least one of the user preferences and the relying party preferences comprises a cost threshold for a single transaction.

4. The method of claim 1 wherein at least one of the user preferences and the relying party preferences comprises a cumulative cost threshold for a plurality of transactions.

5. The method of claim 1 wherein at least one of the user preferences and the relying party preferences comprises a time limit since a password was provided to a user device.

6. The method of claim 1 wherein at least one of the user preferences and the relying party preferences comprises a type of device, wherein using the type of device requires a first level of authentication.

7. The method of claim 1 wherein at least one of the user preferences and the relying party preferences comprises types of transactions that change user account information, wherein a first level of authentication is required.

8. The method of claim 1 wherein the transaction comprises verifying an identity of the user to the relying party.

9. The method of claim 1 wherein the transaction comprises a purchase made by the user from the relying party.

10. The method of claim 1 wherein using the transaction authentication level for the transaction is enforced by an identity repository that is remotely located.

11. A system for determining a transaction authentication level, the system comprising:

a user module operating on a user device, configured to;

receive, from a relying party;

transaction information associated with a transaction between a user and the relying party; and

relying party preferences; and

an identity repository configured to;

receive the transaction information and the relying party preferences from the user module;

access user preferences;

determine a user authentication level based on the transaction information and the user preferences;

determine a relying party authentication level based on the transaction information and the relying party preferences; and

determine the transaction authentication level using the user authentication level and the relying party authentication level.

12. The system of claim 11 wherein the user module comprises code running in a web browser.

13. The system of claim 11 wherein the user module comprises an app operating on a mobile device.

14. The system of claim 11 wherein the transaction authentication level comprises requiring an indication that the transaction is approved to be received, by the user module, from a user.

15. The system of claim 11 wherein the transaction authentication level comprises requiring a password to be received by the user module.

16. The system of claim 11 wherein the transaction authentication level comprises requiring an indication that the transaction is approved to be received by a second user module.

17. The system of claim 16 wherein the second user module operates on a second user device.

18. The system of claim 16 wherein the transaction authentication level further comprises requiring a PIN to be received by the second user module.

19. An authentication level determination system comprising:

an identity repository coupled to a network and including a data processor and a non-transitory computer-readable storage medium comprising a plurality of computer-readable instructions tangibly embodied on the computer-readable storage medium, which, when executed by a data processor, provide authentication level determination, the plurality of instructions comprising;

instructions that cause the data processor to receive transaction information associated with a transaction between a user and a relying party;

instructions that cause the data processor to receive relying party preferences;

instructions that cause the data processor to determine a relying party authentication level based on the transaction information and the relying party preferences;

instructions that cause the data processor to access user preferences;

instructions that cause the data processor to determine a user authentication level based the transaction information and the user preferences; and

instructions that cause the data processor to determine the transaction authentication level using the user authentication level and the relying party authentication level.

20. The system of claim 19 wherein the transaction authentication level is determined based on which of the user authentication level and the relying party authentication level is most secure.