System and method for blockchain-based cross-entity authentication

1. A computer-implemented method, comprising:

obtaining, at a first computing system from a first entity, an authentication request for authenticating a user, wherein the authentication request comprises a decentralized identifier (DID) of the user;

generating, at the first computing system, a digital signature on the obtained authentication request based on a private key of the first entity;

generating, at the first computing system, an authorization encrypted with a private key of the user indicating a permission for the first entity to access an authentication result of the user endorsed by a second entity, wherein the encrypted authorization comprises the digital signature and the DID of the user;

adding, to a blockchain, a blockchain transaction for obtaining the authentication result endorsed by the second entity, wherein the authentication result indicates whether the DID in the authentication request is registered with the second entity, and the blockchain transaction comprises the encrypted authorization;

obtaining, at the first computing system from the blockchain, the authentication result endorsed by the second entity; and

transmitting the obtained authentication result to the first entity for the first entity to authenticate the user based on the obtained authentication result.

2. The method of claim 1 , after adding, to the blockchain, the blockchain transaction and before obtaining, at the first computing system from the blockchain, the authentication result, further comprising:

obtaining, at a second computing system from the blockchain, the blockchain transaction for obtaining the authentication result;

obtaining, at the second computing system, the authentication result by searching in a data store for a certification endorsed by the second entity that the DID is registered with the second entity;

generating, at the second computing system, a different blockchain transaction comprising the authentication result; and

adding the different blockchain transaction to the blockchain.

3. The method of claim 1 , wherein the authentication result comprises a verifiable claim (VC) indicating that the DID in the authentication request is registered with the second entity.

4. The method of claim 3 , wherein the VC comprises a permission for the first entity to authenticate users based on the VC.

5. The method of claim 3 , wherein:

the VC is stored in a data store in association with the DID; and

the data store is accessible by the second entity.

6. The method of claim 3 , wherein a hash value of the VC is stored in the blockchain in association with the DID.

7. The method of claim 1 , wherein:

the authentication result indicates that the DID is registered with the second entity; and

transmitting the obtained authentication result to the first entity for the first entity to authenticate the user based on the obtained authentication result comprises transmitting the obtained authentication result to the first entity for granting the user access to the first entity.

8. The method of claim 1 , wherein:

the authentication result indicates that the DID is not registered with the second entity; and

transmitting the obtained authentication result to the first entity for the first entity to authenticate the user based on the obtained authentication result comprises transmitting the obtained authentication result to the first entity for denying the user access to the first entity.

9. The method of claim 1 , before adding, to the blockchain, the blockchain transaction, further comprising:

obtaining, at the first computing system, a public key of the user from the blockchain based on the DID; and

verifying, at the first computing system, that the user owns the DID based at least on the obtained public key of the user.

10. The method of claim 1 , wherein:

the DID comprises a secondary DID that is limited by an expiring time, limited by an expiring number of use, or limited for accessing only the first entity.

11. The method of claim 10 , wherein:

the user corresponds to a primary DID and the secondary DID both known by the second entity; and

the primary DID corresponds to privacy information of the user that is untraceable based on the secondary DID.

12. A non-transitory computer-readable storage medium storing instructions executable by one or more processors, wherein execution of the instructions causes the one or more processors to perform operations comprising:

obtaining, at a first computing system from a first entity, an authentication request for authenticating a user, wherein the authentication request comprises a decentralized identifier (DID) of the user;

generating, at the first computing system, a digital signature on the obtained authentication request based on a private key of the first entity;

generating, at the first computing system, an authorization encrypted with a private key of the user indicating a permission for the first entity to access an authentication result of the user endorsed by a second entity, wherein the encrypted authorization comprises the digital signature and the DID of the user;

adding, to a blockchain, a blockchain transaction for obtaining the authentication result endorsed by the second entity, wherein the authentication result indicates whether the DID in the authentication request is registered with the second entity, and the blockchain transaction comprises the encrypted authorization;

obtaining, at the first computing system from the blockchain, the authentication result endorsed by the second entity; and

transmitting the obtained authentication result to the first entity for the first entity to authenticate the user based on the obtained authentication result.

13. The non-transitory computer-readable storage medium of claim 12 , wherein after adding, to the blockchain, the blockchain transaction and before obtaining, at the first computing system from the blockchain, the authentication result, the operations further comprise:

obtaining, at a second computing system from the blockchain, the blockchain transaction for obtaining the authentication result;

obtaining, at the second computing system, the authentication result by searching in a data store for a certification endorsed by the second entity that the DID is registered with the second entity;

generating, at the second computing system, a different blockchain transaction comprising the authentication result; and

adding the different blockchain transaction to the blockchain.

14. The non-transitory computer-readable storage medium of claim 12 , wherein the authentication result comprises a verifiable claim (VC) indicating that the DID in the authentication request is registered with the second entity.

15. The non-transitory computer-readable storage medium of claim 14 , wherein the VC comprises a permission for the first entity to authenticate users based on the VC.

16. The non-transitory computer-readable storage medium of claim 14 , wherein:

the VC is stored in a data store in association with the DID; and

the data store is accessible by the second entity.

17. The non-transitory computer-readable storage medium of claim 14 , wherein a hash value of the VC is stored in the blockchain in association with the DID.

18. The non-transitory computer-readable storage medium of claim 12 , wherein before adding, to the blockchain, the blockchain transaction, the operations further comprise:

obtaining, at the first computing system, a public key of the user from the blockchain based on the DID; and

verifying, at the first computing system, that the user owns the DID based at least on the obtained public key of the user.

19. A system comprising one or more processors and one or more non-transitory computer-readable memories coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the system to perform operations comprising:

obtaining, from a first entity, an authentication request for authenticating a user, wherein the authentication request comprises a decentralized identifier (DID) of the user;

generating, at the first computing system, a digital signature on the obtained authentication request based on a private key of the first entity;

generating, at the first computing system, an authorization encrypted with a private key of the user indicating a permission for the first entity to access an authentication result of the user endorsed by a second entity, wherein the encrypted authorization comprises the digital signature and the DID of the user;

adding, to a blockchain, a blockchain transaction for obtaining the authentication result endorsed by the second entity, wherein the authentication result indicates whether the DID in the authentication request is registered with the second entity, and the blockchain transaction comprises the encrypted authorization;

obtaining, from the blockchain, the authentication result endorsed by the second entity; and

transmitting the obtained authentication result to the first entity for the first entity to authenticate the user based on the obtained authentication result.