Method and device for revoking authority

Abstract

This application discloses a method and device for revocation of authority. A permission revocation method includes: determining the authorization record set that needs to be revoked; setting the time-sensitive attribute value for the determined set, so that the set attribute value T ₀ be the current moment or a future moment. The technical solution provided by this application can achieve the effect of updating the state of all records in the collection through one modification operation, without updating authorization records one by one, and will not be affected by different storage locations of multiple authorization records, thus effectively improving batch revocation The processing efficiency of permissions reduces the difficulty of technical implementation.

Description

technical field [0001] The present application relates to the technical field of authority control, in particular to a method and device for revoking authority. Background technique [0002] With the development of computer and Internet technology, users can enjoy many convenient functions. With the continuous improvement of user needs, a single functional subject sometimes cannot meet the complex needs of users. In this case, it is necessary for multiple relatively independent functional subjects to cooperate in a certain way to jointly provide services for users. . For example, in order to meet the shopping needs of users, the cooperation of multiple parties such as e-commerce platforms, payment platforms, and logistics platforms is required. [0003] In order to realize the collaboration between originally independent functional subjects, in addition to the necessary data exchange between the functional subjects, it is often necessary for the functional subjects to open...

AI Technical Summary

Problems solved by technology

The problem with this solution is that every time a permission is revoked, a field update operation needs to be performed on the database. If permissions need to be revoked in batches, the relevant authorization records need to be updated one by one. In the database operating environment, the actual processing efficiency is relatively low

Moreover, the operation logic of "item-by-item update" also needs to consume a lot of manpower and time costs to write and implement. If different authorization records are stored in a sub-database or sub-table, the corresponding data update operation also needs to involve sub-databases or sub-table, resulting in a further increase in the difficulty of technical implementation

Images