Blockchain Authorization via Segmented Server Roles
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current authorization methods in blockchain-type ledgers are cumbersome and lack efficient solutions for managing user permissions and service end operations, leading to difficulties in user authorization and de-authorization processes.
Innovation Solution
An authorization method and system that includes a client, database server, and service end, where the client initiates an authorization request with a service end identifier and user identifier, and the database server determines and executes the necessary authorization instructions, sending authorization information to the service end to update its operable ledger list, allowing for convenient user permission management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authorization methods are used in blockchain-type ledgers, then user permissions can be managed, but the authorization process becomes cumbersome and complex
Solution Approach 1:
The authorization process is segmented into distinct roles: client initiates authorization requests, database server validates and processes them, and service ends receive and execute authorization information. This segmentation allows each component to specialize in specific tasks, improving both security and operational simplicity.
Solution Approach 2:
The database server acts as an intermediary between the client and service ends. It receives authorization requests from clients, validates them against the ledger, and distributes authorization information to appropriate service ends. This intermediary role simplifies the overall process by centralizing authorization logic and reducing direct complexity between endpoints.
2Reliability
If manual authorization management is implemented, then user permissions can be controlled, but the operational efficiency decreases
Solution Approach 1:
The system enables self-service authorization where service ends automatically receive and process authorization information from the database server without requiring manual intervention. The operable ledger list is automatically updated with mapping relationships, eliminating manual permission management steps and significantly improving operational efficiency while maintaining robust authorization control.
Solution Approach 2:
Authorization information is prepared and validated in advance by the database server before being distributed to service ends. The mapping relationships between user identifiers and ledger identifiers are pre-established and stored in the operable ledger list, allowing service ends to execute authorized operations immediately without delays.
3Reliability
If comprehensive permission tracking is implemented, then authorization integrity is maintained, but the system complexity increases
Solution Approach 1:
The database server performs multiple functions: it validates authorization requests, manages the operable ledger list, distributes authorization information, and maintains mapping relationships. This multi-functionality consolidates what would otherwise require separate complex components into a single coordinated system, maintaining authorization integrity while reducing overall system complexity.
Solution Approach 2:
The system maintains copies of authorization information in the operable ledger list at each service end, rather than requiring all service ends to query the central database server for every authorization check. This local copying reduces communication overhead and system complexity while preserving authorization integrity through cryptographic validation.
Data Source
AI summary
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.