A multi-level dynamic authorization method and system for an intelligent seal

CN122933009APending Publication Date: 2026-10-16河南晟宇信息技术有限公司
0 Cites 0 Cited by

Patent Information

Application Number
CN202611092580.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-22
Publication Date
2026-10-16

AI Technical Summary

Technical Problem

静态授权机制无法适应这种需要细粒度、多维度的权限判定场景，导致授权策略过于粗放，无法匹配实际业务的管控要求

Benefits of technology

[0006] This invention refines and decomposes multi-level authorization strategies and constructs a computable Merkle tree containing logical operators. By embedding the root hash into the JWT token payload, authorization evaluation can be completed by providing only a local Merkle proof path during verification. A multi-layered protection mechanism, employing independent multi-key signatures overlaid with a master signature, is used for both the identity and authorization declaration areas, reducing the risk of token forgery or unauthorized tampering. For high-risk permissions, an interaction mechanism between a ratification gateway and a secondary authorization center is utilized. Computable logical root-derived credentials are generated and multiple audits are triggered, strengthening security control in high-risk seal usage scenarios and ensuring absolute security and compliance of seal usage.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

The application provides a multi-level dynamic authorization method and system of an intelligent seal, the authorization method comprising: extracting an authorization request containing a user, a seal parameter and a target entity, disassembling a multi-level authorization strategy into a permission node set with an identifier, a scope and atomic constraints; building a computable Merkle tree with a logic operator from bottom to top with the permission node as a leaf, storing a root hash into a JWT payload, marking a high-risk intermediate node as a reauthorization gateway, generating a reauthorization instruction containing a secondary authorization center address, and generating a reauthorization credential from the root hash; signing the payload identity and the permission area with a one-key and a two-key respectively, substituting the two-area signature into the root hash, and then completing the overall main signature with a master key to generate an aggregated JWT; checking the main signature after receiving a seal request, calculating the true value of the permission node according to the Merkle proof path and real-time context, performing a hierarchical hash check and logical evaluation; and determining that the authorization is completed when the authorization is passed and the reauthorization gateway is passed, and the secondary authorization center reauthorization token is called.
Need to check novelty before this filing date? Find Prior Art