Granted Patent B2

US 12,425,383 · App. 18/548,436 · Granted Sep 23, 2025

Inventors: Ivan Bjerre Damgard (Abyhoj, DK); Thomas Pelle Jakobsen (Marslet, DK); Jakob Illeborg Pagter (Aarhus V, DK); Torben Lauritzen (Aarhus C, DK)

Assignee: BLOCKDAEMON APS

H04L63/08

Abstract

Claims (63)

1. A method for authentication of a user towards a multi-node party, the multi-node party comprising at least two nodes, the method comprising the steps of:

the user contacting each of the nodes of the multi-node party, via a user application,

each of the nodes of the multi-node party generating a nonce and returning the nonce to the user application,

the user application requesting authentication from an Identity Provider, based on the nonces received from each of the nodes of the multi-node party and on a unique identity of the user,

the Identity Provider generating a message, based on the request for authentication and on the nonces generated by each of the nodes, and providing the message to the user application,

the user application providing the message in a secret form to each of the nodes of the multi-node party,

the nodes of the multi-node party verifying the message, based on the received secret form of the message and by means of secure multi-party computation performed by the at least two nodes in cooperation, and

authenticating the user based on the secure multi-party computation.

2. The method according to claim 1 , further comprising the step of the Identity Provider encrypting the message, and providing the encrypted message to the user application, and

wherein the step of the user application providing the message in a secret form comprises providing the encrypted message to the nodes of the multi-node party.

3. The method according to claim 2 , further comprising the step of the nodes of the multi-node party generating a shared encryption key, and

wherein at least the step of encrypting the message is performed by means of the shared encryption key.

4. The method according to claim 2 , further comprising the step of decrypting the received message at the multi-node party, by means of secure multi-party decryption.

5. The method according to claim 1 , wherein the step of the user application providing the message in a secret form to each of the nodes of the multi-node party comprises the user application generating a sharing of the message, and providing at least one share of the message to each of the nodes of the multi-node party, and

wherein the step of the nodes of the multi-node party verifying the message is performed based on the received shares.

6. The method according to claim 1 , further comprising the step of storing at least part of the message at the multi-node party, in the form of a secret sharing of at least part of the message.

7. The method according to claim 1 , further comprising the steps of:

each node of the multi-node party generating a session ID and returning the session ID to the user application along with the nonce,

for each of the nodes of the multi-node party, the user application providing the session ID generated by a given node of the multi-node party along with the share(s) of the message provided to that node, and

each node verifying the received session ID.

8. The method according to claim 1 , further comprising the step of granting or denying access for the user to an object stored at a storage location which is accessible to the multi-node party, based on the authentication of the user and based on a set of access rights.

9. The method according to claim 1 , further comprising the steps of:

deriving a sharing of a unique ID of the user from the message, and storing shares of the unique ID of the user at the nodes of the multi-node party and by means of a multi-party storing operation, and

each node logging activities of the user and storing the logged activities along with the respective share(s) of the unique user ID.

10. The method according to claim 9 , further comprising the steps of:

an auditor retrieving activity information from the nodes of the multi-node party by means of a multi-party operation, and

the auditor performs audit of activities performed at the multi-node party, based on the retrieved information.

11. The method according to claim 9 , further comprising the steps of:

generating a pseudonym user ID and storing the pseudonym user ID at the multi-node party and by means of a multi-party storing operation,

logging activities of the user and associating the activities and the pseudonym user ID to each other, and

each node providing information regarding node ID, pseudonym user ID and associated activities to a log.

12. The method according to claim 1 , wherein the step of the user application requesting authentication from an Identity Provider comprises the steps of:

the user application requesting authentication of the user from a first Identity Provider, based on the nonces received from the nodes of the multi-node party and on a unique identity of the user,

the first Identity Provider generating a first message, based on the request for authentication and providing the first message to the user application,

the user application requesting authentication of the user from a second Identity Provider, based on the first message received from the first Identity Provider and on a unique identity of the user, and

the second Identity Provider generating a second message, based on the request for authentication and providing the second message to the user application.

13. The method according to claim 12 , wherein the step of the user application requesting authentication from an Identity Provider further comprises the user application requesting authentication of the user from at least a third Identity Provider, based on the second message and on a unique identity of the user, thereby creating a chain of messages.

14. The method according to claim 1 , wherein the step of the user application requesting authentication from an Identity Provider comprises the steps of:

the user application requesting authentication of a first user from the Identity Provider, based on the nonces received from the nodes of the multi-node party and on a unique identity of the first user,

the Identity Provider generating a first message, based on the request for authentication of the first user and providing the first message to the user application,

the user application requesting authentication of a second user from the Identity Provider, based on the first message received from the Identity Provider and on a unique identity of the second user, and

the Identity Provider generating a second message, based on the request for authentication of the second user and providing the second message to the user application.

15. The method according to claim 14 , wherein the step of the user application requesting authentication from an Identity Provider further comprises the user application requesting authentication of at least a third user from the Identity Provider, based on the second message and on a unique identity of the third user, thereby creating a chain of messages.

16. A method for authentication of a user towards a multi-node party, the multi-node party comprising at least two nodes, the method comprising the steps of:

the user contacting each of the nodes of the multi-node party, via a user application,

each of the nodes of the multi-node party generating a nonce and returning the nonce to the user application,

the user application generating a combined nonce, based on the nonces received from each of the nodes of the multi-node party, and requesting authentication from an Identity Provider based on the combined nonce and on a unique identity of the user,

the Identity Provider generating a message, based on the request for authentication and on the combined nonce, and providing the message to the user application,

the user application providing the message to each of the nodes of the multi-node party,

the nodes of the multi-node party verifying the message, based on the received message and by means of a verifying operation, and

authenticating the user based on the verifying operation.

17. The method according to claim 16 , wherein the step of the user application requesting authentication from an Identity Provider comprises the steps of:

the user application requesting authentication of the user from a first Identity Provider, based on the combined nonce and on a unique identity of the user,

the first Identity Provider generating a first message, based on the request for authentication and providing the first message to the user application,

the user application requesting authentication of the user from a second Identity Provider, based on the first message received from the first Identity Provider and on a unique identity of the user, and

the second Identity Provider generating a second message, based on the request for authentication and providing the second message to the user application.

18. The method according to claim 17 , wherein the step of the user application requesting authentication from an Identity Provider further comprises the user application requesting authentication of the user from at least a third Identity Provider, based on the second message and on a unique identity of the user, thereby creating a chain of messages.

19. The method according to claim 16 , wherein the step of the user application requesting authentication from an Identity Provider comprises the steps of:

the user application requesting authentication of a first user from the Identity Provider, based on the combined nonce and on a unique identity of the first user,

the Identity Provider generating a first message, based on the request for authentication of the first user and providing the first message to the user application,

the user application requesting authentication of a second user from the Identity Provider, based on the first message received from the Identity Provider and on a unique identity of the second user, and

the Identity Provider generating a second message, based on the request for authentication of the second user and providing the second message to the user application.

20. The method according to claim 19 , wherein the step of the user application requesting authentication from an Identity Provider further comprises the user application requesting authentication of at least a third user from the Identity Provider, based on the second message and on a unique identity of the third user, thereby creating a chain of messages.

Assignments (2)

Priority Claims (1)

Continuity (2)

References Cited (9)