Blockchain authorization
A computer-implemented method includes: receiving, by a server storing one or more blockchain ledgers, an authorization request from a client, in which the authorization request includes a service end identifier and a user identifier; generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request; authorizing a service end corresponding to the service end identifier as a user in a blockchain ledger corresponding to the ledger identifier; configuring a permission value of the user in the blockchain ledger, in which the permission value determines a degree to which the service end can operate the blockchain ledger; and sending authorization information including the user identifier and the ledger identifier to the service end.
1. A computer-implemented method comprising:
receiving, by a server storing a plurality of blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request, the ledger identifier identifying a first blockchain ledger of the plurality of blockchain ledgers;
authorizing a service end corresponding to the service end identifier as a user in the first blockchain ledger;
configuring a permission value of the user in the first blockchain ledger, wherein the permission value determines a degree to which the service end can operate the first blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end,
wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier, the ledger identifier, and the permission value is written into an operable ledger list stored locally at the service end.
2. The computer-implemented method of claim 1 , wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and
writing the public key information of the service end into a permission configuration file corresponding to the first blockchain ledger.
3. The computer-implemented method of claim 1 , further comprising:
generating a first data record comprising the database authorization instruction; and
writing the first data record into the first blockchain ledger corresponding to the ledger identifier.
4. The computer-implemented method of claim 3 , further comprising obtaining public key information of the service end,
wherein the first data record comprises the public key information of the service end.
5. The computer-implemented method of claim 3 , further comprising:
sending a hash value of the first data record to the client and to the service end.
6. The computer-implemented method of claim 1 , further comprising:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises the service end identifier and the user identifier;
determining a database de-authorization instruction based on the de-authorization request and the ledger identifier based on the de-authorization request; and
cancelling, in the first blockchain ledger corresponding to the ledger identifier, operation permissions of the service end corresponding to the service end identifier.
7. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a server storing a plurality of blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request, the ledger identifier identifying a first blockchain ledger of the plurality of blockchain ledgers;
authorizing a service end corresponding to the service end identifier as a user in the first blockchain ledger;
configuring a permission value of the user in the first blockchain ledger, wherein the permission value determines a degree to which the service end can operate the first blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end,
wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier, the ledger identifier, and the permission value is written into an operable ledger list stored locally at the service end.
8. The computer-readable medium of claim 7 , wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and
writing the public key information of the service end into a permission configuration file corresponding to the first blockchain ledger.
9. The computer-readable medium of claim 7 , wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and
writing the first data record into the first blockchain ledger corresponding to the ledger identifier.
10. The computer-readable medium of claim 9 , wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end.
11. The computer-readable medium of claim 9 , wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end.
12. The computer-readable medium of claim 7 , wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises the service end identifier and the user identifier;
determining a database de-authorization instruction based on the de-authorization request and the ledger identifier based on the de-authorization request; and
cancelling, in the first blockchain ledger corresponding to the ledger identifier, operation permissions of the service end corresponding to the service end identifier.
13. A computer-implemented system, comprising:
one or more computers; and
one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving, by a server storing a plurality of blockchain ledgers, an authorization request from a client, wherein the authorization request comprises a service end identifier and a user identifier;
generating, based on the authorization request, a database authorization instruction corresponding to the authorization request and a ledger identifier corresponding to the authorization request, the ledger identifier identifying a first blockchain ledger of the plurality of blockchain ledgers;
authorizing a service end corresponding to the service end identifier as a user in the first blockchain ledger;
configuring a permission value of the user in the first blockchain ledger, wherein the permission value determines a degree to which the service end can operate the first blockchain ledger; and
sending authorization information comprising the user identifier and the ledger identifier to the service end,
wherein, responsive to the authorization information being received by the service end, a mapping relationship between the user identifier, the ledger identifier, and the permission value is written into an operable ledger list stored locally at the service end.
14. The computer-implemented system of claim 13 , wherein configuring the permission value of the user comprises:
obtaining, by the server, public key information of the service end; and
writing the public key information of the service end into a permission configuration file corresponding to the first blockchain ledger.
15. The computer-implemented system of claim 13 , wherein the operations further comprise:
generating a first data record comprising the database authorization instruction; and
writing the first data record into the first blockchain ledger corresponding to the ledger identifier.
16. The computer-implemented system of claim 15 , wherein the operations further comprise obtaining public key information of the service end, and
wherein the first data record comprises the public key information of the service end.
17. The computer-implemented system of claim 15 , wherein the operations further comprise:
sending a hash value of the first data record to the client and to the service end.
18. The computer-implemented system of claim 13 , wherein the operations further comprise:
receiving, by the server, a de-authorization request from the client, wherein the de-authorization request comprises the service end identifier and the user identifier;
determining a database de-authorization instruction based on the de-authorization request and the ledger identifier based on the de-authorization request; and
cancelling, in the first blockchain ledger corresponding to the ledger identifier, operation permissions of the service end corresponding to the service end identifier.