Decentralized identities for access to multiple computing resource systems
At least one identity for a given entity is established in accordance with a decentralized identity management system maintained in accordance with a distributed ledger, wherein the identity of the given entity and a set of attributes relating to the identity are defined by a secure token file. The secure token file is referenced in the distributed ledger enabling two or more computing resource systems (e.g., storage systems) to at least one of authenticate and authorize the given entity in accordance with the secure token file.
1. A method, comprising:
associating a secure token file with at least one identity for a given entity, wherein the at least one identity of the given entity and a set of attributes relating to the identity are defined by the secure token file to create an identity profile for the given entity, wherein the set of attributes defined by the secure token file comprises at least one permission attribute;
receiving, at a given storage system, a write request from the given entity to store a data set on the given storage system;
determining if the write request is authorized based on authentication of the permission attribute of the secure token file;
in response to the write request being authorized, sending, from the given storage system to the given entity, at least one smart contract to define one or more terms of an access relationship comprising access to store the data set on the given storage system;
receiving, at the given storage system from the given entity, acceptance of the at least one smart contract; and
granting access to the given entity to store a data set on the given storage system;
wherein the method is implemented via one or more processing devices each comprising a processor coupled to a memory.
2. The method of claim 1 , wherein, upon receipt of the write request, the given storage system returns the at least one smart contract to the given entity as a reference to a smart contract or the at least one smart contract itself.
3. The method of claim 1 , wherein the at least one smart contract specifies one or more payment terms between the given storage system and the given entity for storing a certain type of file.
4. The method of claim 1 , wherein the given entity maintains the at least one smart contract and the given storage system agrees to the one or more terms of the at least one smart contract.
5. The method of claim 1 , wherein the at least one smart contract specifies when payment occurs with respect to read requests of the data set at the given storage system.
6. The method of claim 1 , wherein the at least one smart contract specifies a set of cryptocurrency transfer options when other entities read the data set stored on the given storage system, and wherein a given read request by one of the other entities causes execution of a payment.
7. The method of claim 1 , wherein the at least one smart contract specifies a set of cryptocurrency transfer options dependent on the identity of a read requesting entity, and wherein a given read request by the read requesting entity causes execution of a payment.
8. The method of claim 1 , wherein the at least one smart contract specifies a set of cryptocurrency transfer options dependent on one or more of an amount of content access given to the data set and an amount of resolution access given to the data set, and wherein a given read request causes execution of a payment.
9. The method of claim 1 , wherein the at least one smart contract specifies that the given storage system and the given entity share a payment associated with a read request for the data set.
10. The method of claim 1 , further comprising receiving a query from a subsequent user of the given storage system requesting the set of terms of the at least one smart contract prior to the given storage system responding to a read request from the subsequent user for the data set.
11. An apparatus, comprising:
at least one processor operatively coupled to at least one memory and configured to:
associate a secure token file with at least one identity for a given entity, wherein the at least one identity of the given entity and a set of attributes relating to the identity are defined by the secure token file to create an identity profile for the given entity, wherein the set of attributes defined by the secure token file comprises at least one permission attribute;
receive, at a given storage system, a write request from the given entity to store a data set on the given storage system;
determine if the write request is authorized based on authentication of the permission attribute of the secure token file;
in response to the write request being authorized, send, from the given storage system to the given entity, at least one smart contract to define one or more terms of an access relationship comprising access to store the data set on the given storage system;
receive, at the given storage system from the given entity, acceptance of the at least one smart contract; and
grant access to the given entity to store a data set on the given storage system.
12. The apparatus of claim 11 , wherein, upon receipt of the write request, the given storage system returns the at least one smart contract to the given entity as a reference to a smart contract or the at least one smart contract itself.
13. The apparatus of claim 11 , wherein the at least one smart contract specifies one or more payment terms between the given storage system and the given entity for storing a certain type of file.
14. The apparatus of claim 11 , wherein the given entity maintains the at least one smart contract and the given storage system agrees to the one or more terms of the at least one smart contract.
15. The apparatus of claim 11 , wherein the at least one smart contract specifies when payment occurs with respect to read requests of the data set at the given storage system.
16. The apparatus of claim 11 , wherein the at least one smart contract specifies a set of cryptocurrency transfer options when other entities read the data set stored on the given storage system, and wherein a given read request by one of the other entities causes execution of a payment.
17. The apparatus of claim 11 , wherein the at least one smart contract specifies a set of cryptocurrency transfer options dependent on the identity of a read requesting entity, and wherein a given read request by the read requesting entity causes execution of a payment.
18. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device to:
associate a secure token file with at least one identity for a given entity, wherein the at least one identity of the given entity and a set of attributes relating to the identity are defined by the secure token file to create an identity profile for the given entity, wherein the set of attributes defined by the secure token file comprises at least one permission attribute;
receive, at a given storage system, a write request from the given entity to store a data set on the given storage system;
determine if the write request is authorized based on authentication of the permission attribute of the secure token file;
in response to the write request being authorized, send, from the given storage system to the given entity, at least one smart contract to define one or more terms of an access relationship comprising access to store the data set on the given storage system;
receive, at the given storage system from the given entity, acceptance of the at least one smart contract; and
grant access to the given entity to store a data set on the given storage system.
19. The computer program product of claim 18 , wherein, upon receipt of the write request, the given storage system returns the at least one smart contract to the given entity as a reference to a smart contract or the at least one smart contract itself.
20. The computer program product of claim 18 , wherein the at least one smart contract specifies one or more payment terms between the given storage system and the given entity for storing a certain type of file.