System and method for autonomous mapping of enterprise identity

1. A method comprising:

establishing off-chain a decentralized identifier (DID) associated with a first organization and a second organization registered on a public blockchain;

encrypting, by the first organization, a mapping solicitation message comprising an authentication token with a limited time to live (TTL);

broadcasting, to the public blockchain, the mapping solicitation message;

decrypting the mapping solicitation message by a second organization registered on the public blockchain:

deriving the authentication token from the decrypted mapping solicitation message;

validating the authentication token within the TTL by an autonomous blockchain verification process;

responsive to the validation, establishing a private channel of communication on the public blockchain between the second organization and a message end point associated with the first organization;

mapping an internal identifier associated with a system of record connected to the message end point of the first organization to the DID over the private channel, wherein the mapping of the internal identifier comprises a conversion associated with a public key of the first organization and a private key of the second organization.

2. The method of claim 1 , further comprising:

executing a smart contract to broadcast the mapping solicitation message over the public blockchain.

3. The method of claim 1 , further comprising:

listening for a broadcast of the mapping solicitation message comprising an encrypted payload;

retrieving the mapping solicitation message containing the encrypted payload;

decrypting the payload using, at least in part, a secret key of the second organization;

determining an endpoint address for establishing the private channel of communication with the authentication token within the TTL; and

presenting the authentication token for establishing the private channel of communication at the endpoint address within the TTL.

4. The method of claim 3 , wherein determining the endpoint address for establishing the private channel of communication with the authentication token within the TTL comprises:

performing a lookup, in a decentralized registry, of the endpoint address for establishing the private channel of communication; and

retrieving, from the decentralized registry, the endpoint address for establishing the private channel of communication with the authentication token within the TTL.

5. The method of claim 4 , wherein determining the endpoint address for establishing the private channel of communication with the authentication token within the TTL comprises extracting the payload to retrieve the endpoint address.

6. The method of claim 1 , further comprising:

maintaining a decentralized registry on the public blockchain; and

executing one or more smart contracts on the public blockchain to:

publish a public key associated with the first organization;

publish a public key associated with the second organization;

publish a first endpoint address associated with the first organization; and

publish a second endpoint address associated with the second organization.

7. The method of claim 6 , further comprising:

performing a lookup of a second organization's decentralized identifier in the decentralized registry; and

associating the second organization with the decentralized identifier.

8. The method of claim 1 , further comprising:

communicating a message comprising a methodology to derive a secret key;

listening for a message containing a confirmation of receipt of the methodology for deriving the secret key;

receiving the message containing the confirmation of receipt; and

initiating a process to broadcast the encrypted mapping solicitation message.

9. The method of claim 3 , further comprising:

listening for a message containing a methodology for deriving the secret key;

retrieving the message containing the methodology for deriving the secret key; and

communicating a confirmation message.

10. A method comprising:

retrieving a target public key associated with a target party, wherein retrieving the target public key comprises utilizing a decentralized identifier associated with the target party and a requesting party;

generating a secret off-chain based on, at least in part, the target public key associated with the target party and a private key associated with the requesting party;

generating a payload off-chain configured to be used for establishing a direct private channel of communication between the requesting party and the target party for validating each party's identity, wherein the payload comprises an authentication token with a limited time to live (TTL);

encrypting the payload off-chain using the secret;

broadcasting a message comprising the payload to a public blockchain;

determining whether an intended recipient, as represented by an internal identifier within the requesting party's system of record, will be able to provide the authentication token to the requesting party in order to establish that the intended recipient is the target party represented by the decentralized identifier used to retrieve the target party's public key; and

mapping the internal identifier associated with the system of record connected to the requesting party to the decentralized identifier over the direct private channel of communication, wherein the mapping of the internal identifier comprises a conversion associated with a public key of the requesting party and a private key of the target party.

11. The method of claim 10 , further comprising:

scanning the public blockchain for any message that can be decrypted using, at least in part, the requesting party's public key;

identifying a message that can be decrypted using, at least in part, the requesting party's public key and a private key associated with the target party;

decrypting the message to obtain the payload to extract the payload to obtain the authentication token with the limited TTL period; and

requesting to establish the direct private channel of communication at an endpoint associated with the requesting party,

wherein a request comprises receiving the authentication token within the TTL period.

12. The method of claim 11 , further comprising:

establishing a connection when the requesting party accepts the direct private channel of communication request; and

exchanging, via the direct private channel of communication between the requesting party and the target party, data used to validate the identity of each party.

13. The method of claim 12 , further comprising:

validating the identity of the requesting party based on the data; and

mapping an internal identifier to the decentralized identifier.

14. The method of claim 10 , further comprising:

receiving, from the target party, a request to establish the direct private channel of communication at an endpoint address associated with the requesting party, wherein receiving the request comprises receiving the authentication token with the request; and

accepting a connection if, at least in part, the request comprises the authentication token within the TTL period.

15. The method of claim 14 , further comprising:

exchanging, via the direct private channel of communication between the requesting party and the target party, data used to validate the identity of at least one party;

validating the identity of the at least one party based on the data; and

mapping, upon validation, a private identifier of the first party with a public identifier of the target party.

16. The method of claim 14 , wherein receiving the request comprises receiving a request signed by the target party's public key.

17. The method of claim 14 , wherein receiving the request comprises receiving the request within the limited TTL period.

18. The method of claim 15 , wherein the data comprises hashes associated with underlying data corresponding to at least one internal record.

19. The method of claim 10 , wherein the authentication token is packaged in the payload.

20. The method of claim 10 , further comprising:

maintaining an organizational registry on the public blockchain; and

executing one or more smart contracts on the public blockchain to:

publish the public key associated with the requesting party;

publish the public key associated with the target party;

publish a first endpoint address associated with the requesting party; and

publish a second endpoint address associated with the target party.