System or method to implement record level access on metadata driven blockchain using shared secrets and consensus on read

Patent metadata

Field	Value
Publication number	US-2020374106-A1
Application number	US-201916667847-A
Country	US
Kind code	A1
Filing date	Oct 29, 2019
Priority date	May 22, 2019
Publication date	Nov 26, 2020
Grant date	—

Abstract

A method performed by a system of a host organization for providing access controls for data a blockchain, the system providing a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization each serving as nodes in a blockchain network. The method includes receiving a request including an identifier of a requestor, the request to access transaction data having defined privileges, requesting access to the transaction data from nodes in the blockchain network, a request for access including the identifier of the requestor, receiving at least one shared secret from an owner node in the blockchain network indicating consensus to access the transaction data by the requestor, and denying access to the transaction data in response to receiving insufficient shared secrets from the nodes indicating the requestor does not meet requirements of the defined privileges of the transaction data.

First claim

What is claimed is:

1 . A method performed by a system of a host organization for providing access controls for data a blockchain, the system providing a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization each serving as nodes in a blockchain network, the method comprising:
receiving a request including an identifier of a requestor, the request to access transaction data having defined privileges; requesting access to the transaction data from nodes in the blockchain network, a request for access including the identifier of the requestor; receiving at least one shared secret from an owner node in the blockchain network indicating consensus to access the transaction data by the requestor; and denying access to the transaction data in response to receiving insufficient shared secrets from the nodes indicating the requestor does not meet requirements of the defined privileges of the transaction data.

2 . The method of claim 1 , the method further comprising:
determining whether the identifier of the requestor has read access privileges before requesting access to the transaction data.

3 . The method of claim 1 , the method further comprising:
receiving request to write data associated with the transaction data; and determining whether the request to write is permitted by the privileges of the transaction data by a smart contract.

4 . The method of claim 1 , wherein the transaction data is decrypted in response to receiving a threshold number of shared secrets.

5 . The method of claim 1 , wherein a decryption key is recovered from received shared secrets.

6 . The method of claim 1 , wherein denying access to the transaction data is in response to a number of received shared secrets being below a threshold for recovering a key for encryption. The method of claim 1 , further comprising:
defining object and metadata for the transaction data to be stored in the blockchain including identification of access privileges for objects and fields.

8 . A computing system of a host organization configured to perform a method for providing a right to forget data in a blockchain, the computer system providing a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization each serving as nodes in a blockchain network, the computer system comprising:
a computer readable medium having stored therein the blockchain interface and a permissions manager; and a processor coupled to the blockchain interface, the processor configured to execute the blockchain interface and the permissions manager, the permissions manager to receive a request including an identifier of a requestor, the request to access transaction data having defined privileges, to request access to the transaction data from nodes in the blockchain network, a request for access including the identifier of the requestor, to receive at least one shared secret from an owner node in the blockchain network indicating consensus to access the transaction data by the requestor, and to deny access to the transaction data in response to receiving insufficient shared secrets from the nodes indicating the requestor does not meet requirements of the defined privileges of the transaction data.

9 . The computer system of claim 8 , wherein the permissions manager is further to determine whether the identifier of the requestor has read access privileges before requesting access to the transaction data.

10 . The computer system of claim 8 , wherein the permissions manager is further to determine to receive request to write data associated with the transaction data, and to determine whether the request to write is permitted by the privileges of the transaction data by a smart contract.

11 . The computer system of claim 8 , wherein the transaction data is decrypted in response to receiving a threshold number of shared secrets.

12 . The computer system of claim 8 , wherein a decryption key is recovered from received shared secrets.

13 . The computer system of claim 8 , wherein denying access to the transaction data is in response to a number of received shared secrets being below a threshold for recovering a key for encryption.

14 . The computer system of claim 8 , wherein the permissions manager is further to define object and metadata for the transaction data to be stored in the blockchain including identification of access privileges for objects and fields.

15 . A computer-readable medium having stored therein a set of instructions, which when executed cause a computer system of a host organization to perform a set of operations of a method for managing read access of data in a blockchain, the computer system providing a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization, the set of operations comprising:
receiving a request including an identifier of a requestor, the request to access transaction data having defined privileges; requesting access to the transaction data from nodes in the blockchain network, a request for access including the identifier of the requestor; receiving at least one shared secret from an owner node in the blockchain network indicating consensus to access the transaction data by the requestor; and denying access to the transaction data in response to receiving insufficient shared secrets from the nodes indicating the requestor does not meet requirements of the defined privileges of the transaction data.

16 . The computer-readable medium of claim 15 , the operations further comprising:
determining whether the identifier of the requestor has read access privileges before requesting access to the transaction data.

17 . The computer-readable medium of claim 15 , the operations further comprising:
receiving request to write data associated with the transaction data; and determining whether the request to write is permitted by the privileges of the transaction data by a smart contract.

18 . The computer-readable medium of claim 15 , wherein the transaction data is decrypted in response to receiving a threshold number of shared secrets.

19 . The computer-readable medium of claim 15 , wherein a decryption key is recovered from received shared secrets.

20 . The computer-readable medium of claim 15 , wherein denying access to the transaction data is in response to a number of received shared secrets being below a threshold for recovering a key for encryption.

Assignees

• Salesforce Com Inc

Inventors

• Padmanabhan Prithvi Krishnan

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• G06F16/1837

  Management specially adapted to peer-to-peer storage networks (topology management mechanisms of peer-to-peer networks H04L67/1042) · CPC title

• G06F16/137

  Hash-based (content-based indexing of textual data G06F16/31) · CPC title

• G06F21/64 Primary

  Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title