WO2019165668A1 - 跨平台用户权限管理方法、装置、计算机设备及存储介质 - Google Patents

跨平台用户权限管理方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2019165668A1
WO2019165668A1 PCT/CN2018/081507 CN2018081507W WO2019165668A1 WO 2019165668 A1 WO2019165668 A1 WO 2019165668A1 CN 2018081507 W CN2018081507 W CN 2018081507W WO 2019165668 A1 WO2019165668 A1 WO 2019165668A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
platform
target
original
rights
Prior art date
Application number
PCT/CN2018/081507
Other languages
English (en)
French (fr)
Inventor
白益仲
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019165668A1 publication Critical patent/WO2019165668A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/604—Tools and structures for managing or administering access control systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices

Definitions

  • the present application relates to the field of big data processing, and in particular, to a cross-platform user rights management method, apparatus, computer device, and storage medium.
  • Rights management generally refers to the security rules or security policies set by the system, users can access and can only access their own authorized resources. Among them, the user right solves the problem of which resources the user can access or operate.
  • the database types supported by different business platforms may be different.
  • multiple business systems support Oracle, Mysql, SQL server, etc., and the differences between such databases are Personalization leads to the control of data rights for each business system corresponding to each business platform.
  • the service system corresponding to different service platforms usually configures the user rights for accessing the service platform resources for users under each service platform.
  • each user can only access the resources on the corresponding service platform according to their own user rights, and cannot access the resources corresponding to other associated service platforms, causing inconvenience to the user.
  • the user rights management logics of different service platforms are independent of each other, which makes the management and maintenance costs relatively large.
  • the embodiment of the present application provides a cross-platform user rights management method, device, computer device, and storage medium to solve the problem that users on different service platforms can only access their corresponding service platforms.
  • the embodiment of the present application provides a cross-platform user rights management method, including:
  • the embodiment of the present application provides a cross-platform user rights management apparatus, including:
  • the original user rights management data obtaining module is configured to obtain original user rights management data sent by at least two service platforms, where the original user rights management data includes an original user ID, a user role, and an original user right, and the original user rights management data Associated with the platform identifier;
  • a target user right obtaining module configured to perform integration processing on the original user rights in the at least two service platforms based on the user role, and acquire target user rights corresponding to each original user ID;
  • a target platform identifier obtaining module configured to acquire at least two target platform identifiers corresponding to the cross-platform identifiers if the target user rights carry cross-platform identifiers;
  • the target user right sending module is configured to send the target user right to the service platform corresponding to the at least two target platform identifiers.
  • an embodiment of the present application provides a computer device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer The following steps are implemented when reading the instruction:
  • the embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions, when the computer readable instructions are executed by one or more processors, such that the one or Multiple processors implement the following steps:
  • Embodiment 1 is a flowchart of a method for managing cross-platform user rights in Embodiment 1;
  • FIG. 2 is a specific schematic view of step S20 of Figure 1;
  • Embodiment 3 is another flowchart of a cross-platform user rights management method in Embodiment 1;
  • FIG. 4 is a schematic block diagram of a cross-platform user rights management apparatus in Embodiment 2;
  • Figure 5 is a schematic illustration of a computer device in the fourth embodiment.
  • FIG. 1 is a flow chart showing a method for managing cross-platform user rights in this embodiment.
  • the cross-platform user rights management method is applied to the user rights management system, and the user rights management system is connected to different service platforms, and is used for centralized management of user rights corresponding to users in different service platforms, so that the service platform is The user has access to other related business platforms, realizes cross-platform user rights management, improves the efficiency of user rights management, and reduces maintenance costs.
  • the cross-platform user rights management method includes the following steps:
  • S10 Acquire original user rights management data sent by at least two service platforms, where the original user rights management data includes an original user ID, a user role, and an original user right, and the original user rights management data is associated with the platform identifier.
  • the service platform refers to a platform for online business processing, including but not limited to the company's business platform, financial platform and third-party outsourcing business platform.
  • Each service platform has a corresponding platform identifier.
  • the platform identifier is an identifier for uniquely identifying the corresponding service platform.
  • the original user rights management data refers to the user rights management data granted to the platform users in each business platform.
  • the user rights management data refers to data that associates each user with its corresponding user rights.
  • each original user rights management system is associated with a platform identifier, so that the user rights management system can determine the source of the corresponding original user rights management data based on the platform identifier.
  • the original user rights management data includes the original user ID, user role, and original user rights.
  • the original user ID refers to an identifier for a uniquely identified user identity in a service platform, and the original user ID may be composed of a platform identifier and a number to facilitate distinguishing users on different service platforms. If the service platform where a user is located is A, the original user ID is A+ number. In this embodiment, the number of each user ID corresponding to different service platforms in the same group company is different, and the number of a user in the same group company is unique, which is convenient for subsequent users to conveniently pass the user when the position changes.
  • the ID manages the user's rights management data.
  • User roles refer to a group of users with the same user rights to manage user and user rights. This group of users with the same user rights is called a role.
  • each user role has different user rights.
  • service platform A including the business manager and the salesperson
  • the user rights of the business manager and the salesperson are different, and the user rights of the business manager in the service platform A include a 1 + a 2 + a 3
  • the user rights of the salesperson in the service platform A include a 1 + a 2 .
  • the service platform A divides the business manager and the salesperson into different user roles, and the business manager corresponds to the user role. It is a manager-level user; the corresponding user role of the salesperson is an employee-level user.
  • the original user rights refer to the user rights that the user can access the resources that are authorized in the service platform according to the security rules or security policies set by the service platform.
  • the original user rights are determined according to the user role and are used to restrict user access to the resources in the service platform.
  • the user rights management system can directly obtain the original user rights management data of at least two service platforms from the big data platform. Since the original user rights management data is associated with the platform identifier, the original user ID, the user role, and the original user rights in the original user rights management data are associated with the platform identifier, which is convenient for identifying the original user ID, the user role, and the original user rights. A business platform. The user rights management system can obtain the original user rights management data of different service platforms, and implement unified management of the original user rights management data of each service platform.
  • S20 Integrate the original user rights in the at least two service platforms based on the user role, and obtain the target user rights corresponding to each original user ID.
  • the target user authority refers to the user right after the user rights of the user corresponding to the original user ID are summarized in different service platforms.
  • the user rights management system obtains the original user rights corresponding to the original user IDs in different service platforms based on the user role, and integrates the original user IDs with the original user rights corresponding to the at least two service platforms to obtain the original user. All original user rights corresponding to the ID in different service platforms are aggregated, that is, the target user rights corresponding to the original user ID.
  • the service platform A a user whose original user ID is A01, the corresponding original user right in the service platform A is a 1 + a 2 + a 3 , and since the user role of the user is a manager-level user, it has to view other
  • the user rights of the employee-level users of the business platform below the manager-level user For example, the original user right owned by user A01 in service platform B is b 1 +b 2 , the original user right in business platform C is c 1 , and the user rights management system will be service platform A, service platform B and service platform.
  • the original user rights corresponding to user A01 in C are integrated, and the user rights corresponding to A01 are a 1 + a 2 + a 3 + b 2 + c 1 , and the target user rights of user A01 are a 1 + a 2 + a 3 +b 2 +c 1 .
  • the original user rights in the at least two service platforms are integrated to obtain the target user rights corresponding to each original user ID, so that the user rights of each original user ID in different service platforms are easily obtained.
  • a cross-platform identifier is an identifier formed when there are more than two identifiers corresponding to all user rights in the target user rights.
  • each original user right has a corresponding platform identifier.
  • the target user rights include at least two platform identifiers, and the target user rights carry a cross-platform identifier, based on the The cross-platform identifier acquires the target platform identifier corresponding to the target user right.
  • the target platform identifier refers to a platform identifier corresponding to each user right included in the target user right.
  • the target user rights carry at least two target platform identifiers. If the target user rights carry at least two target platform identifiers, the cross-platform identifier is generated, so that the target user rights carry cross-platform identifiers, and the user rights management system can Obtain at least two target platform identifiers corresponding to the target user rights.
  • the target user authority of user A01 is a 1 + a 2 + a 3 + b 2 + c 1
  • the platform identifier corresponding to a 1 + a 2 + a 3 includes A
  • the platform identifier corresponding to b 2 is B
  • the corresponding platform identifier is C
  • the target platform identifiers corresponding to the target user rights are A, B, and C.
  • S40 Send the target user right to the service platform corresponding to the at least two target platform identifiers.
  • the user rights management system After obtaining the target user rights, the user rights management system sends the target user rights to the service platform corresponding to each target platform identifier based on at least two target platform identifiers in the target user rights. If the original user ID belongs to only one service platform, and only the corresponding original user rights are stored in the corresponding target user rights, the target user rights only include the platform identifier corresponding to the original user ID, and the target user rights are not required. The reason is that the service platform corresponding to the original user ID is fed back again, because the service platform pre-stores the corresponding target user rights to avoid repeated processing.
  • the user rights management system After the target user right is sent to the service platform corresponding to the at least two target platform identifiers, the user rights management system sends the associated user rights and the corresponding original user IDs in the target user rights to the associated services corresponding to the associated user rights identifiers.
  • platform The associated user authority refers to other user rights in the target user rights that are not the original user rights corresponding to the user ID.
  • the associated user permission identifier refers to the platform identifier carried in the associated user right.
  • the associated service platform refers to the service platform corresponding to the associated user rights identifier.
  • the target user authority of user A01 is a 1 + a 2 + a 3 + b 2 + c 1
  • a 1 + a 2 + a 3 is the original user right of user A01
  • b 2 and c 1 are the associated user rights of A01.
  • User rights management system to a 1 + a 2 + a 3 + b after 2 + c 1 to the user A01 corresponding service platform A, to send b 2 and the user A01 to the associated service platform B, c 1, and the user A01 to a Associated business platform C.
  • the user rights management system sends the target user rights to the service platform corresponding to the original user ID, so that the user A01 retains all user rights belonging to the user in the original service platform, so as to conveniently understand the user rights that can be accessed by different user platforms. .
  • the associated user rights and the corresponding original user IDs are sent to the associated service platform corresponding to the associated user rights identifier, and the user information of the user A01 is not sent to the associated service platform, which can effectively ensure that the user information of the user A01 is not leaked in the associated service platform.
  • the user A01 can access the resources corresponding to the associated service platform in the associated service platform.
  • the user rights management system obtains the original user rights management data sent by at least two service platforms, and integrates the original user rights in the at least two service platforms based on the user role to obtain and compare with each original user.
  • the target user right corresponding to the ID, and the target user right is sent to the service platform corresponding to the target platform identifier, so that the user can understand the target user rights owned by the user on the business platform where the user is located, and the associated platform can also obtain the user.
  • the user rights of the associated platform realize cross-platform management of user rights, improve the efficiency of user rights management, and reduce maintenance costs, so as to avoid the need to separately manage user rights of different service platforms, resulting in higher management and maintenance costs. There was a problem.
  • the target user rights are sent to the service platform corresponding to the at least two target platform identifiers by using a preset URI.
  • the URI Uniform Resource Identifier
  • the URI is a resource identifier based on the http or https protocol, which is used to allow users to interact with any (including local and Internet) resources through a specific protocol.
  • the URI is defined by a scheme that includes determining the grammar and associated protocols. For example, each resource available on the Web, such as HTML documents, images, video clips, programs, etc., is located by a Uniform Resource Identifier ("URI").
  • the http or https protocol refers to a format and a communication protocol for the service platform and the user rights management system to agree on the user rights management data transmission, which are pre-stored in the server, and the resource identifier refers to a character used to identify the name of an Internet resource. string.
  • the protocol is used to implement data transmission between the user rights management system and the service platform, the problem that the data cannot be mutually transmitted due to the incompatibility of the platform can be avoided, so as to ensure the realization of user rights cross-platform management.
  • the user rights management system requests the URI pre-stored in the server in real time, and sends the target user right to the service platform corresponding to the at least two target platform identifiers based on the URI.
  • the service platform compares with the original user rights management data stored in the service platform, and modifies the local original user rights management data to the target user sent by the user rights management system.
  • the permissions are consistent, and the user rights management data in the service platform and the user rights management system are consistent. This step realizes the real-time performance of user rights management data transmission, and avoids the user rights management data update of the user rights management system, but the user rights management data of the service platform cannot be updated in time.
  • the target user authority is sent to the service platform corresponding to the at least two target platform identifiers by using the preset URI, so that the original user rights management data of different service platforms can be uniformly managed, so that the user rights management system and User rights management data in different business platforms can be updated in real time.
  • the user rights management system integrates the original user rights in at least two service platforms by acquiring the user role, and obtains corresponding to each original user ID in at least two service platforms.
  • Target user rights, and the target user rights are sent to the service platform corresponding to the at least two target platform identifiers, thereby implementing cross-platform management based on the storage-based user rights management data of the multi-service platform.
  • step S20 based on the user role, the original user rights in the at least two service platforms are integrated, and the target user rights corresponding to each original user ID are obtained, specifically Including the following steps:
  • S21 Determine an associated user level of the user role in the associated service platform based on the user role.
  • the associated user level refers to the ranking level of the user role in the associated service platform.
  • the user level corresponds to the user role, and different user roles have different user levels on different service platforms.
  • the user level of the user in the service platform A is the level of the user in the service platform A
  • the user level of the user in the service platform A is the second level.
  • Level 1 and Level 2 are the user levels of different user roles in the business platform.
  • the associated user level corresponds to the user role in the associated platform.
  • the corresponding user levels in different service platforms are different.
  • the user level of the manager-level user in the service platform A is one level
  • the level of the associated user in the associated service platform C is the second level, wherein the associated service platform C is the associated service platform of the service platform A.
  • step S21 determining an associated user level of the user role in the associated service platform based on the user role, specifically including the following steps: determining, based on the user role, a user level conversion table in advance, determining that the user role is associated The associated user level in the business platform.
  • the user level conversion table refers to a level conversion table of the same user role in different business platforms.
  • the user level conversion table includes user IDs, user roles, and user levels for different service platforms.
  • the user level conversion table can be used to determine the user level of the same user role in different service platforms, that is, the user level conversion table is used to determine the associated user level of the user role in the associated service platform, thereby determining that the same user ID is in the associated service platform.
  • Associate user levels Based on the user role, determining the associated user level of the user role in the associated service platform, and conveniently obtaining the associated user right of the user in step S22.
  • the associated user right refers to the user right corresponding to the user level below the associated user level determined by the user role in the associated service platform.
  • the user rights of the user in the associated service platform can only include the original user rights of the associated service platforms below the associated user level corresponding to the user in the associated service platform, so as to prevent any user from accessing the same user in the associated service platform across platforms.
  • the service manager in the service platform A is at the first level of the user role of the service platform A
  • the service platform B is the associated service platform of the service platform A
  • the user role of the business manager on the service platform B is also the first level, because the service platform A
  • the business manager does not belong to the user of the service platform B. Therefore, the associated user rights of the business manager on the service platform B are the user rights of the user level B in the service platform B and below the second level and below.
  • each original user ID corresponds to a user role, and there is also a corresponding user role and associated user rights in the associated service platform, and the user rights management system associates the associated user rights and original users corresponding to the same original user ID.
  • the permissions are consolidated as the target user rights for the original user ID.
  • the target user rights corresponding to each original user ID embodies all user rights of the user corresponding to the original user ID in each service platform, and implements cross-platform management user rights, so that each user can access the corresponding related service based on the target user rights. platform.
  • the cross-platform user rights management method further includes the following steps:
  • S51 Acquire a user rights change request, where the user rights change request includes changing user rights management data, and changing the user rights management data includes changing a user ID or changing a role.
  • the user rights change request refers to a request sent by the service platform to the user rights management system for changing user rights.
  • the service platform changes.
  • a user permission change request is sent to the user rights management system.
  • the user authority change request includes changing the user rights management data, and the changed user rights management data refers to the rights management data after the user changes.
  • Changing user rights management data includes changing user IDs and changing roles.
  • Changing the user ID means that when the user is transferred from one service platform to another, the user ID corresponding to the user needs to be changed, and the changed user ID is referred to as the changed user ID.
  • the user's original user ID will be changed to the platform ID + number after the transfer. For example, a user whose original user ID is A01 is transferred from the service platform to the service platform B. The original user ID corresponding to the user will be changed to B01, and B01 is the changed user ID corresponding to the user.
  • the user IDs in each service platform belonging to the same group enterprise are numbered by the same set of numbering rules.
  • the numbering rule means that the labels of each user in all service platforms are not repeated and are unique. One number corresponds to only one user.
  • each user number is unique, when the user A01 is transferred from the service platform A to the service platform B, only the platform identifier of the user needs to be changed, and the user number in the original user ID corresponding to the user does not need to be changed. Easy to manage.
  • a change role is a user role that corresponds to a user role change.
  • the corresponding user role when a user is promoted or demoted, the corresponding user role also changes, and the changed user role is called a change role. If the user A02 is promoted from the salesperson to the business manager in the service platform A, the corresponding user role is also changed from the employee-level user to the manager-level user, and the manager-level user is the corresponding change role of the user.
  • the service platform After obtaining the change user ID and the change role, the service platform sends the acquired change user ID and the change role to the user rights management system, so that the user rights management system performs the user authority change process based on the change user ID and the change role.
  • S52 Acquire change user rights management data based on the change role, perform integration processing on the change user rights management data in the at least two service platforms, and acquire the change user authority corresponding to each original user ID.
  • Changing user rights refers to changing the target user rights corresponding to the role.
  • the change user rights management data also includes changing user rights.
  • the original user rights corresponding to each change role are changed user rights.
  • the salesperson A02 in the service platform A is promoted to the business manager in the service platform A, that is, the change role is the manager-level user
  • the original user authority of the manager-level user in the service platform A is a 1 + a 2 + a 3 .
  • a 1 + a 2 + a 3 is the change user authority corresponding to the salesperson A02 of the service platform A becoming the business manager A02.
  • the user rights of the original user ID in the corresponding service platform also change.
  • the service platform changes the user rights management data corresponding to the change role.
  • the data is sent to the big data platform storage, and the big data platform sends the change user rights management data corresponding to the change role to the user rights management system.
  • the user rights management system integrates the changed user rights management data based on the change role, integrates the changed user rights belonging to the same user ID in each service platform, and acquires the changed user rights corresponding to each original user ID.
  • the salesperson A02 in the service platform A is promoted to the business manager in the business platform A, and the original user authority of the business manager in the business platform A is a 1 + a 2 + a 3 .
  • the user level of the salesperson A02 is one level. It can be known from step S20 that the user A02 also has the original user right b 2 in the service platform B, and the original user right in the service platform C is c 1 , the user rights management system.
  • the user rights management data corresponding to the same user ID in at least one service platform is integrated, and the change user authority corresponding to the change role is a 1 + a 2 + a 3 + b 2 + c 1
  • the change user authority of the user A02 is a 1 + a 2 + a 3 + b 2 + c 1 .
  • S53 Acquire the changed user authority management data based on the changed user ID, integrate the changed user authority management data in the at least two service platforms, and acquire the changed user authority corresponding to the changed user ID.
  • the original user right of the user role corresponding to the changed user ID in the service platform is searched based on the platform identifier associated with the changed user ID. For example, if the user whose user ID is A01 in service platform A is transferred to service platform B, the corresponding change user ID is B01, and the user whose user ID is B01 is transferred from service platform A to service platform B for level transfer. That is, the user role has not changed, and is still a manager-level user.
  • the original user right of the manager-level user in the service platform B in the service platform B is b 1 + b 2 , and the change user authority whose user ID is B01 is changed to b. 1 +b 2 .
  • the user rights management system After obtaining the changed user rights management data sent by the service platform, the user rights management system searches for the associated user rights in the associated service platform related to the service platform based on the user role corresponding to the changed user ID, and then changes the user rights management data. The user rights and associated user rights are integrated to obtain the changed user rights corresponding to the changed user ID. After the user rights management system obtains the changed user rights management data sent by the service platform B, it searches for the associated user rights in the associated service platform A related to the service platform B based on the user role corresponding to the B01, and obtains the changed user corresponding to B01. The permissions are a 2 + a 3 + b 1 + b 2 .
  • the user rights management system After obtaining the change user right, the user rights management system sends the change user right to the service platform corresponding to each target platform identifier based on at least two platform identifiers in the change user rights. If the change user ID belongs to a certain service platform, the target user right is transmitted to the service platform corresponding to the changed user ID based on the platform identifier included in the change user ID. After the change user right is sent to the service platform corresponding to the change user ID, the user rights management system sends the associated user right and the corresponding original user ID in the changed user right to the associated service platform corresponding to the associated user rights identifier, so that The associated service platform can update the user rights management data in the service platform in time.
  • the rights management system acquires the changed user rights based on the changed user rights management data carried in the user permission change request, and facilitates the rights management personnel to manage the rights management data. Maintenance and management.
  • the cross-platform authority centralized management method integrates the original authority management data of different service platforms based on the user role through the user rights management system to obtain the target user rights. Then, the user rights management system sends the target user rights to the service platform corresponding to the target platform identifier through the preset URI, so that the user can understand the target user rights owned by the user on the business platform where the user is located, and the associated platform can also obtain the target user rights.
  • the user's user rights in the associated platform realizes cross-platform management of user rights.
  • the user role changes or the original user ID changes the corresponding user rights are changed.
  • the rights management system obtains the changed user rights based on the changed user rights management data carried in the user permission change request, so that the rights management personnel can maintain the rights management data. And management.
  • FIG. 4 is a schematic block diagram showing a cross-platform user rights management apparatus corresponding to the cross-platform user rights management method in Embodiment 1.
  • the cross-platform user rights management apparatus includes an original user rights management data acquisition module 10, a target user rights acquisition module 20, a target platform identity acquisition module 30, and a target user rights transmission module 40.
  • the implementation functions of the original user rights management data obtaining module 10, the target user rights obtaining module 20, the target platform identifier obtaining module 30, and the target user right sending module 40 correspond to the steps corresponding to the cross-platform user rights management method in the embodiment. In order to avoid redundancy, the present embodiment will not be described in detail.
  • the original user rights management data obtaining module 10 is configured to obtain original user rights management data sent by at least two service platforms, where the original user rights management data includes an original user ID, a user role, and an original user right, and the original user rights management data and the platform identifier. Association.
  • the target user right obtaining module 20 is configured to perform integration processing on the original user rights in the at least two service platforms based on the user role, and acquire target user rights corresponding to each original user ID.
  • the target platform identifier obtaining module 30 is configured to acquire at least two target platform identifiers corresponding to the cross-platform identifiers if the target user rights carry the cross-platform identifiers.
  • the target user right sending module 40 is configured to send the target user right to the service platform corresponding to the at least two target platform identifiers.
  • the target user right obtaining module 20 includes: a user level obtaining unit 21, an associated user right obtaining unit 22, and a target user right obtaining unit 23.
  • the user level obtaining unit 21 is configured to determine, according to the user role, an associated user level of the user role in the associated service platform.
  • the associated user right obtaining unit 22 is configured to use the original user right below the associated user level in the associated service platform as the associated user right.
  • the target user right obtaining unit 23 is configured to integrate the associated user rights corresponding to each original user ID with the original user rights as the target user rights.
  • the user level obtaining unit 21 is configured to determine an associated user level of the user role in the associated service platform by using a preset user level conversion table based on the user role.
  • the target user right sending module 40 is configured to send the target user right to the service platform corresponding to the original user ID, and send the associated user right and the corresponding original user ID in the target user right to the associated service platform.
  • the target user right sending module 40 is configured to send the target user right to the service platform corresponding to the at least two target platform identifiers by using a preset URI.
  • the cross-platform user rights management apparatus further includes a user authority change request acquisition module 51, a first change user authority acquisition module 52, a second change user authority acquisition module 53, and a change user authority transmission module 54.
  • the user right change request obtaining module 51 is configured to acquire a user right change request, and the user right change request includes changing the user right management data, and changing the user right management data includes changing the user ID or changing the role.
  • the first change user right obtaining module 52 is configured to acquire the changed user rights management data based on the change role, integrate the changed user rights management data in the at least two service platforms, and acquire the change corresponding to each original user ID. User rights.
  • the second change user right acquisition module 53 is configured to acquire the changed user right management data based on the changed user ID, integrate the changed user right management data in the at least two service platforms, and acquire the changed user right corresponding to the changed user ID.
  • the change user right sending module 54 is configured to send the changed user right to the corresponding service platform.
  • This embodiment provides one or more non-volatile readable storage media having computer readable instructions stored thereon.
  • the one or more non-transitory readable storage mediums storing computer readable instructions
  • the computer readable instructions when executed by one or more processors, causing one or more processors to perform cross-platform in embodiment 1.
  • the user rights management method in order to avoid duplication, will not be described here.
  • the functions of the modules/units in the cross-platform user rights management device in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.
  • non-volatile readable storage media storing computer readable instructions may comprise: any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a mobile hard drive, Disk, optical disk, computer memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.
  • FIG. 5 is a schematic diagram of a computer device according to an embodiment of the present application.
  • computer device 60 of this embodiment includes a processor 61, a memory 62, and computer readable instructions 63 stored in memory 62 and operative on processor 61.
  • the processor 61 executes the steps of the cross-platform user rights management method in the first embodiment, such as steps S10 to S40 shown in FIG. 1, when the computer readable instructions 63 are executed.
  • the functions of the modules/units of the cross-platform user rights management apparatus in the second embodiment are implemented, for example, the original user rights management data obtaining module 10 and the target user rights acquisition shown in FIG.
  • the functions of the module 20, the target platform identifier acquisition module 30, and the target user rights sending module 40 are used to avoid repetition, and are not described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Health & Medical Sciences (AREA)
  • Automation & Control Theory (AREA)
  • Storage Device Security (AREA)

Abstract

本申请公开了跨平台用户权限管理方法、装置、计算机设备及存储介质。该跨平台用户权限管理方法，包括：获取至少两个业务平台发送的原始用户权限管理数据，原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，原始用户权限管理数据与平台标识关联；基于用户角色，对至少两个业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；若目标用户权限携带有跨平台标识，则获取与跨平台标识相对应的至少两个目标平台标识；将目标用户权限发送给与至少两个目标平台标识相对应的业务平台。该方法可以使用户具有访问关联业务平台的权限，实现跨平台用户权限管理，提高用户权限管理的效率，同时降低管理维护成本。

Description

跨平台用户权限管理方法、装置、计算机设备及存储介质
本申请以2018年2月27日提交的申请号为201810161846.1，名称为“跨平台用户权限管理方法、装置、计算机设备及存储介质”的中国发明专利申请为基础，并要求其优先权。
技术领域
本申请涉及大数据处理领域，尤其涉及一种跨平台用户权限管理方法、装置、计算机设备及存储介质。
背景技术
权限管理，一般指根据系统设置的安全规则或者安全策略，用户可以访问而且只能访问自己被授权的资源。其中，用户权限解决的是用户能对哪些资源进行访问或者操作的问题。
出于对平台安全性以及实际业务需求的安全考虑，不同业务平台对应的业务系统支持的数据库类型可能不同，例如多个业务系统分别支持Oracle、Mysql、SQL server等，这种数据库的差异性和个性化导致每个业务平台对应的业务系统对于数据权限的控制都需要自己处理，管理和维护比较困难。例如，当前集团公司根据实际业务需求的安全考虑，需要针对不同的业务需求配置不同的业务系统。出于对平台安全性的考虑，不同业务平台对应的业务系统通常会给每一业务平台下的用户配置访问业务平台资源的用户权限。当前每一用户只能依据其自身的用户权限访问其对应的业务平台上的资源，无法访问其他关联的业务平台对应的资源，给用户造成不便。而且，当前不同业务平台的用户权限管理逻辑相互独立，使得其管理和维护成本较大。
发明内容
本申请实施例提供一种跨平台用户权限管理方法、装置、计算机设备及存储介质，以解决当前不同业务平台上的用户只能访问其对应的业务平台所存在的问题。
第一方面，本申请实施例提供一种跨平台用户权限管理方法，包括：
获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
第二方面，本申请实施例提供一种跨平台用户权限管理装置，包括：
原始用户权限管理数据获取模块，用于获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
目标用户权限获取模块，用于基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
目标平台标识获取模块，用于若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
目标用户权限发送模块，用于将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
第三方面，本申请实施例提供一种计算机设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
第四方面，本申请实施例提供一个或多个存储有计算机可读指令的非易失性可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器实现如下步骤：
获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
本申请的一个或多个实施例的细节在下面的附图及描述中提出。本申请的其他特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是实施例1中跨平台用户权限管理方法的一流程图；
图2是图1中步骤S20的一具体示意图；
图3是实施例1中跨平台用户权限管理方法的另一流程图；
图4是实施例2中跨平台用户权限管理装置的一原理框图；
图5是实施例4中计算机设备的示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
实施例1
图1示出本实施例中跨平台用户权限管理方法的流程图。该跨平台用户权限管理方法应用在用户权限管理系统中，该用户权限管理系统与不同的业务平台相连，用于对不同的业务平台中的用户对应的用户权限进行集中管理，以使业务平台中的用户具备访问其他关联的业务平台的访问权限，实现跨平台用户权限管理，提高用户权限管理的效率，同时降低维护成本。如图1所示，该跨平台用户权限管理方法包括如下步骤：
S10：获取至少两个业务平台发送的原始用户权限管理数据，原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，原始用户权限管理数据与平台标识关联。
其中，业务平台是指线上进行业务处理的平台，包括但不限于本公司的业务平台、财务平台和第三方外购业务平台，每一业务平台都有一对应的平台标识。该平台标识是用于 唯一识别对应的业务平台的标识。
原始用户权限管理数据是指每个业务平台中授予该平台用户的用户权限管理数据。该用户权限管理数据是指将每一用户与其对应的用户权限关联起来的数据。本实施例中，每一原始用户权限管理系统与一平台标识相关联，以使用户权限管理系统可基于平台标识确定对应的原始用户权限管理数据的来源。原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限。
其中，原始用户ID是指在一业务平台中用于唯一识别的用户身份的标识，该原始用户ID可以由平台标识和编号组成，以便于区别不同业务平台上的用户。如一用户所在的业务平台为A，该原始用户ID则为A+编号。本实施例中，同一集团公司中不同业务平台对应的每一用户ID的编号是不一样的，一个用户在同一集团公司中的编号时唯一的，便于后续用户在职位发生变化时，方便通过用户ID管理用户的权限管理数据。
用户角色是指为便于对用户和用户权限进行管理，将一组具有相同用户权限的用户组织在一起，这一组具有相同用户权限的用户就称为角色。在一业务平台中，每一种用户角色对应的用户权限不同。如业务平台A中，包括业务经理和业务员两种类型的用户，业务经理和业务员对应的用户权限是不同的，业务经理在业务平台A中的用户权限包括a 1+a 2+a 3，业务员在业务平台A中的用户权限包括a 1+a 2，为了便于对用户和用户权限进行管理，业务平台A将业务经理和业务员分为不同的用户角色，业务经理对应的用户角色为经理级用户；业务员对应的用户角色为员工级用户。
原始用户权限是指根据业务平台设置的安全规则或者安全策略，用户可以访问自己在业务平台中被授权的资源的用户权限。原始用户权限是根据用户角色确定的，是用于限制用户对业务平台中的资源进行访问调用的用户权限。
由于所有业务平台的原始用户权限管理数据可以存储在大数据平台中，用户权限管理系统可以直接从大数据平台获取至少两个业务平台的原始用户权限管理数据。由于原始用户权限管理数据与平台标识关联，使得原始用户权限管理数据中的原始用户ID、用户角色和原始用户权限都与平台标识关联，便于识别原始用户ID、用户角色和原始用户权限是属于哪一个业务平台的。用户权限管理系统可以获取不同业务平台的原始用户权限管理数据，实现对各业务平台的原始用户权限管理数据进行统一管理。
S20：基于用户角色，对至少两个业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限。
目标用户权限是指原始用户ID对应的用户在不同业务平台中的用户权限进行汇总后 的用户权限。
用户权限管理系统基于用户角色，获取该原始用户ID在不同的业务平台中对应的原始用户权限，将该原始用户ID在至少两个业务平台中对应的原始用户权限进行整合处理，获取该原始用户ID在不同的业务平台中对应的所有原始用户权限并进行汇总，即该原始用户ID对应的目标用户权限。
如业务平台A中的一原始用户ID为A01的用户，在业务平台A中对应的原始用户权限为a 1+a 2+a 3，由于该用户的用户角色为经理级用户，其拥有查看其他业务平台在经理级用户以下的员工级用户的用户权限。例如，用户A01在业务平台B中拥有的原始用户权限为b 1+b 2，在业务平台C中拥有的原始用户权限为c 1,用户权限管理系统将业务平台A、业务平台B和业务平台C中属于用户A01对应的原始用户权限进行整合处理，获取A01对应的用户权限为a 1+a 2+a 3+b 2+c 1，用户A01的目标用户权限则为a 1+a 2+a 3+b 2+c 1。
将至少两个业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限，便于获取每一个原始用户ID在不同业务平台中的用户权限。
S30：若目标用户权限携带有跨平台标识，则获取与跨平台标识相对应的至少两个目标平台标识。
跨平台标识是指目标用户权限中所有用户权限对应的标识超过两种时形成的标识。当目标用户权限中至少两种原始用户权限时，每一原始用户权限都有一对应的平台标识，此时，目标用户权限中包括至少两种平台标识，目标用户权限携带有跨平台标识，基于该跨平台标识获取该目标用户权限对应的目标平台标识。其中，目标平台标识是指目标用户权限中包括的每一用户权限对应的平台标识。
判断目标用户权限中是否携带有至少两种目标平台标识，若目标用户权限携带有至少两种目标平台标识，则生成跨平台标识，以使目标用户权限携带有跨平台标识，用户权限管理系统可获取目标用户权限中对应的至少两个目标平台标识。
如用户A01的目标用户权限则为a 1+a 2+a 3+b 2+c 1，a 1+a 2+a 3对应的平台标识包括A，b 2对应的平台标识为B，c 1对应的平台标识为C，目标用户权限对应的目标平台标识为A、B和C。在获取目标平台标识之后，以便于步骤S40将目标用户权限发送给与目标平台标识对应的业务平台。
S40：将目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
用户权限管理系统在获取目标用户权限后，会基于目标用户权限中的至少两个目标平台标识，将目标用户权限发送给每一目标平台标识对应的业务平台中。若原始用户ID只属于某一业务平台，该其对应的目标用户权限中只存储其对应的原始用户权限，则其目标用户权限中只包含其原始用户ID对应的平台标识，无需将目标用户权限再次反馈给与原始用户ID对应的业务平台，其原因在于该业务平台预先存储有相应的目标用户权限，以避免重复处理。
在将目标用户权限发送给与至少两个目标平台标识对应的业务平台后，用户权限管理系统将目标用户权限中的关联用户权限和对应的原始用户ID，发送给关联用户权限标识对应的关联业务平台。其中，关联用户权限是指目标用户权限中，不属于用户ID对应的原始用户权限的其他用户权限。关联用户权限标识是指关联用户权限中携带的平台标识。关联业务平台是指关联用户权限标识对应的业务平台。
如用户A01的目标用户权限为a 1+a 2+a 3+b 2+c 1，a 1+a 2+a 3为用户A01的原始用户权限，b 2和c 1为A01的关联用户权限。用户权限管理系统将a 1+a 2+a 3+b 2+c 1发送给用户A01对应的业务平台A后，将b 2和用户A01发送给关联业务平台B，c 1和用户A01发送给关联业务平台C。
用户权限管理系统将目标用户权限发送给与原始用户ID对应的业务平台，可使得用户A01在原来所在业务平台中保留所有属于自身的用户权限，方便了解自己在不同业务平台中可以访问的用户权限。将关联用户权限和对应的原始用户ID发送给关联用户权限标识对应的关联业务平台，不将用户A01的其他用户信息发送给关联业务平台，可以有效保证用户A01的用户信息不在关联业务平台中泄露，同时可以保证用户A01在关联业务平台中访问关联业务平台对应的资源。
步骤S10-S40中，用户权限管理系统通过获取至少两个业务平台发送的原始用户权限管理数据，基于用户角色，对至少两个业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限，并将目标用户权限发送给与目标平台标识相对应的业务平台，使得用户在自己所在的业务平台可以了解自己拥有的目标用户权限，也可以让关联平台获取该用户在关联平台的用户权限，实现了用户权限跨平台管理，提高用户权限管理的效率，同时降低维护成本，以避免需要对不同业务平台的用户权限进行分别管理，导致其管理和维护成本较大的问题出现。
在一具体实施方式中，采用预先设置的URI将目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
其中，URI(Uniform Resource Identifier，统一资源标识符)是一个基于http或https协议的资源标识符，用于允许用户对任何(包括本地和互联网)的资源通过特定的协议进行交互操作。URI由包括确定语法和相关协议的方案所定义。如Web上可用的每种资源，如HTML文档、图像、视频片段、程序等都是由一个通用资源标识符(Uniform Resource Identifier,简称"URI")进行定位。
该http或https协议是指业务平台和用户权限管理系统约定好用户权限管理数据传输的格式和通信协议，预先存储在服务器中，该资源标识符是指一个用于标识某一互联网资源名称的字符串。使用该协议实现用户权限管理系统和业务平台之间数据的传输时，可避免平台不兼容导致数据不能相互进行传输的问题，以保证用户权限跨平台管理的实现。
具体地，用户权限管理系统在获取到目标用户权限后，会实时请求服务器中预先存储的URI，基于该URI将该目标用户权限发送给与至少两个目标平台标识相对应的业务平台。业务平台在得到对应的目标用户权限后，与该业务平台存储在本地原有的用户权限管理数据进行对比处理，将本地原有的用户权限管理数据中修改为与用户权限管理系统发送的目标用户权限一致，保证业务平台和用户权限管理系统中的用户权限管理数据一致。该步骤实现了用户权限管理数据传输的实时性，避免用户权限管理系统的用户权限管理数据更新，但业务平台的用户权限管理数据得不到及时更新的问题。
本实施方式中，采用预先设置的URI将目标用户权限发送给与至少两个目标平台标识相对应的业务平台，可以实现将不同业务平台原始用户权限管理数据进行统一管理，使得用户权限管理系统和不同业务平台中的用户权限管理数据可以得到实时更新。
该跨平台权限集中管理方法中，用户权限管理系统通过获取用户角色，对至少两个业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID在至少两个业务平台中相对应的目标用户权限，并将目标用户权限发送给与至少两个目标平台标识相对应的业务平台，从而实现基于多业务平台基于存储的用户权限管理数据进行跨平台管理。
在一具体实施方式中，如图2所示，步骤S20，基于用户角色，对至少两个业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限，具体包括如下步骤：
S21：基于用户角色，确定用户角色在关联业务平台中的关联用户等级。
关联用户等级是指用户角色在关联业务平台中的排序等级。用户等级与用户角色相对 应，不同的用户角色在不同业务平台对应的用户等级不同。如业务平台A中用户角色为经理级用户的用户在业务平台A中的用户等级为一级，用户角色为员工级用户的用户在业务平台A中的用户等级为二级。一级和二级就是不同用户角色在业务平台中的用户等级。关联用户等级与关联平台中用户角色相对应。
本实施例中，不同的业务平台中的对应的用户等级是不相同的。如经理级用户在业务平台A中的用户等级为一级，在关联业务平台C中的关联用户等级为二级，其中，关联业务平台C为业务平台A的关联业务平台。
在一具体实施方式中，步骤S21，基于用户角色，确定用户角色在关联业务平台中的关联用户等级，具体包括如下步骤：基于用户角色，采用预先设置的用户等级转换表，确定用户角色在关联业务平台中的关联用户等级。
用户等级转换表是指同一用户角色在不同的业务平台中的等级转化表。用户等级转换表包括用户ID、用户角色和不同业务平台的用户等级。基于用户等级转化表可以确定同一用户角色在不同的业务平台中的用户等级，即通过用户等级转化表确定用户角色在关联业务平台中的关联用户等级，从而确定同一用户ID在关联业务平台中的关联用户等级。基于用户角色，确定用户角色在关联业务平台中的关联用户等级，方便步骤S22获取用户的关联用户权限。
S22：将关联业务平台中，关联用户等级以下的原始用户权限作为关联用户权限。
关联用户权限是指在关联业务平台中，基于用户角色确定的关联用户等级以下的用户等级对应的用户权限。
用户在关联业务平台中的用户权限只能包括关联业务平台中该用户对应的关联用户等级以下的各关联业务平台的原始用户权限，以避免使得任一用户可跨平台访问关联业务平台中同一用户等级的资源，以满足各业务平台的安全规则和安全策略。
如业务平台A中的业务经理在业务平台A的用户角色是一级，业务平台B是业务平台A的关联业务平台，业务经理在业务平台B的用户角色也为一级，由于业务平台A中的业务经理不属于业务平台B的用户，因此，业务经理在业务平台B的关联用户权限为业务平台B中用户等级为二级及二级以下的用户权限。
S23：将每一原始用户ID对应的关联用户权限和原始用户权限进行整合，作为目标用户权限。
本实施例中，每一原始用户ID都对应一用户角色，在关联业务平台中也有对应的用户角色和关联用户权限，用户权限管理系统会将同一个原始用户ID对应的关联用户权限 和原始用户权限进行整合，作为该原始用户ID的目标用户权限。每一原始用户ID对应的目标用户权限体现了原始用户ID对应的用户在各业务平台中的所有用户权限，实现跨平台管理用户权限，以使每一用户可基于目标用户权限访问相应的关联业务平台。
在一具体实施方式中，如图3所示，该跨平台用户权限管理方法还包括如下步骤：
S51：获取用户权限变更请求，用户权限变更请求包括变更用户权限管理数据，变更用户权限管理数据包括变更用户ID或变更角色。
用户权限变更请求是指业务平台发送给用户权限管理系统的用于变更用户权限的请求。用户ID或者用户角色发生变更时，对应的原始用户权限也会发生变更，变更后的用户权限需要发送给用户权限管理系统，业务平台中有用户ID发生变化或者用户角色发生变化时，业务平台就会向用户权限管理系统发送用户权限变更请求。
该用户权限变更请求包括变更用户权限管理数据，变更用户权限管理数据是指用户变更后的权限管理数据。变更用户权限管理数据包括变更用户ID和变更角色。
变更用户ID是指用户在从一业务平台中调岗到另一业务平台时，需要变更该用户对应的用户ID，变更后的用户ID称为变更用户ID。用户从一业务平台中调岗到另一业务平台时，用户的原始用户ID会变为调岗后的平台标识+编号，如一原始用户ID为A01的用户从业务平台调到业务平台B中，该用户对应的原始用户ID会变为B01，B01则为该用户对应的变更用户ID。属于同一集团企业的每一业务平台中的用户ID，采用同一套编号规则进行编号。该编号规则是指所有业务平台中的每一用户的标号都不会重复，是唯一的，一个编号仅对应一个用户。由于每一用户编号是唯一的，因此，在用户A01从业务平台A调岗到业务平台B时，只需要变动该用户的平台标识，不需要变动该用户对应的原始用户ID中的用户编号，方便管理。
变更角色是指用户角色发生变更后对应的用户角色。本实施例中，用户在升职或者降职时，其对应的用户角色也会发生变化，变化后的用户角色称为变更角色。如用户A02在业务平台A中从业务员升职为业务经理后，其对应的用户角色也会从员工级用户更改为经理级用户，经理级用户则为用户对应的变更角色。
业务平台在获取变更用户ID和变更角色后，会将获取的变更用户ID和变更角色发送给用户权限管理系统，以使用户权限管理系统基于变更用户ID和变更角色进行用户权限变更处理。
S52：基于变更角色，获取变更用户权限管理数据，对至少两个业务平台中的变更用户权限管理数据进行整合处理，获取与每一原始用户ID相对应的变更用户权限。
变更用户权限是指变更角色对应的目标用户权限。变更用户权限管理数据中还包括变更用户权限，在一业务平台中，每一变更角色对应的原始用户权限为变更用户权限。如业务平台A中的业务员A02在业务平台A中升职为业务经理，即变更角色为经理级用户，经理级用户在业务平台A中的原始用户权限为a 1+a 2+a 3，a 1+a 2+a 3为业务平台A中业务员A02变为业务经理A02对应的变更用户权限。
当原始用户ID不变，用户角色发生变化时，原始用户ID在对应的业务平台中的用户权限也会发生变化，用户角色发生变化后，业务平台会将该变更角色对应的变更用户权限管理数据发送给大数据平台存储，大数据平台将与变更角色对应的变更用户权限管理数据发送给用户权限管理系统。用户权限管理系统基于变更角色对变更用户权限管理数据进行整合处理，将每一业务平台中属于同一用户ID的变更用户权限进行整合处理，获取与每一原始用户ID相对应的变更用户权限。
如业务平台A中的业务员A02在业务平台A中升职为业务经理，在业务平台A中业务经理的原始用户权限为a 1+a 2+a 3。业务员A02的用户等级为一级，由步骤S20可知，用户A02也有在业务平台B中对应的原始用户权限为b 2，在业务平台C中对应的原始用户权限为c 1，用户权限管理系统会基于变更用户角色，对至少一个业务平台中的同一用户ID对应的用户权限管理数据进行整合处理，变更角色对应的变更用户权限为a 1+a 2+a 3+b 2+c 1，则用户A02的变更用户权限为a 1+a 2+a 3+b 2+c 1。
S53：基于变更用户ID，获取变更用户权限管理数据，对至少两个业务平台中的变更用户权限管理数据进行整合处理，获取变更用户ID对应的变更用户权限。
当原始用户ID发生变化，变为变更用户ID，且用户角色没有发生变化时，基于变更用户ID关联的平台标识，查找该业务平台中与变更用户ID对应的用户角色的原始用户权限。如业务平台A中原始用户ID为A01的用户调岗到业务平台B后对应的变更用户ID为B01，由于用户ID为B01的用户从业务平台A中调到业务平台B中为平级调动，即用户角色没有发生变化，仍为经理级用户，业务平台B中的经理级用户在业务平台B中的原始用户权限为b 1+b 2，则其变更用户ID为B01的变更用户权限为b 1+b 2。
用户权限管理系统获取到业务平台发送的变更用户权限管理数据后，会基于变更用户ID对应的用户角色，查找与业务平台相关的关联业务平台中的关联用户权限，然后对变更用户权限管理数据中的用户权限和关联用户权限进行整合处理，获取变更用户ID对应的 变更用户权限。如用户权限管理系统获取到业务平台B发送的变更用户权限管理数据后，会基于B01对应的用户角色，查找与业务平台B相关的关联业务平台A中的关联用户权限，获取B01对应的变更用户权限为a 2+a 3+b 1+b 2。
S54：将变更用户权限发送给对应的业务平台。
用户权限管理系统在获取变更用户权限后，会基于变更用户权限中的至少两个平台标识将变更用户权限发送给每一目标平台标识对应的业务平台中。若变更用户ID属于某一业务平台，则基于变更用户ID中包含的平台标识，将目标用户权限发送给与变更用户ID对应的业务平台。在将变更用户权限发送给与变更用户ID对应的业务平台后，用户权限管理系统将变更用户权限中的关联用户权限和对应的原始用户ID，发送给关联用户权限标识对应的关联业务平台，使得关联业务平台能及时更新业务平台中的用户权限管理数据。当用户角色发生变更或者原始用户ID发生变更导致对应的用户权限发生变更时，权限管理系统会基于用户权限变更请求携带的变更用户权限管理数据获取变更用户权限，方便权限管理人员对权限管理数据的维护和管理。
该跨平台权限集中管理方法，通过用户权限管理系统将不同业务平台的原始权限管理数据基于用户角色进行整合处理，获取目标用户权限。然后用户权限管理系统通过预先设置的URI，将目标用户权限发送给与目标平台标识相对应的业务平台，使得用户在自己所在的业务平台可以了解自己拥有的目标用户权限，也可以让关联平台获取该用户在关联平台的用户权限，实现了用户权限跨平台管理。用户角色发生变更或者原始用户ID发生变更导致对应的用户权限发生变更时，权限管理系统会基于用户权限变更请求携带的变更用户权限管理数据获取变更用户权限，方便权限管理人员对权限管理数据的维护和管理。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
实施例2
图4示出与实施例1中跨平台用户权限管理方法一一对应的跨平台用户权限管理装置的原理框图。如图4所示，该跨平台用户权限管理装置包括原始用户权限管理数据获取模块10、目标用户权限获取模块20、目标平台标识获取模块30和目标用户权限发送模块40。其中，原始用户权限管理数据获取模块10、目标用户权限获取模块20、目标平台标识获取模块30和目标用户权限发送模块40的实现功能与实施例中跨平台用户权限管理方法对应的步骤一一对应，为避免赘述，本实施例不一一详述。
原始用户权限管理数据获取模块10，用于获取至少两个业务平台发送的原始用户权 限管理数据，原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，原始用户权限管理数据与平台标识关联。
目标用户权限获取模块20，用于基于用户角色，对至少两个业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限。
目标平台标识获取模块30，用于若目标用户权限携带有跨平台标识，则获取与跨平台标识相对应的至少两个目标平台标识。
目标用户权限发送模块40，用于将目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
优选地，目标用户权限获取模块20，包括：用户等级获取单元21、关联用户权限获取单元22和目标用户权限获取单元23。
用户等级获取单元21，用于基于用户角色，确定用户角色在关联业务平台中的关联用户等级。
关联用户权限获取单元22，用于将关联业务平台中，关联用户等级以下的原始用户权限作为关联用户权限。
目标用户权限获取单元23，用于将每一原始用户ID对应的关联用户权限和原始用户权限进行整合，作为目标用户权限。
优选地，用户等级获取单元21，用于基于用户角色，采用预先设置的用户等级转换表，确定用户角色在关联业务平台中的关联用户等级。
优选地，目标用户权限发送模块40，用于将目标用户权限发送给与原始用户ID对应的业务平台，并将目标用户权限中的关联用户权限和对应的原始用户ID发送给关联业务平台。
优选地，目标用户权限发送模块40，用于采用预先设置的URI将目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
优选地，该跨平台用户权限管理装置还包括用户权限变更请求获取模块51、第一变更用户权限获取模块52、第二变更用户权限获取模块53和变更用户权限发送模块54。
用户权限变更请求获取模块51，用于获取用户权限变更请求，用户权限变更请求包括变更用户权限管理数据，变更用户权限管理数据包括变更用户ID或变更角色。
第一变更用户权限获取模块52，用于基于变更角色，获取变更用户权限管理数据，对至少两个业务平台中的变更用户权限管理数据进行整合处理，获取与每一原始用户ID相对应的变更用户权限。
第二变更用户权限获取模块53，用于基于变更用户ID，获取变更用户权限管理数据，对至少两个业务平台中的变更用户权限管理数据进行整合处理，获取变更用户ID对应的变更用户权限。
变更用户权限发送模块54，用于将变更用户权限发送给对应的业务平台。
实施例3
本实施例提供一个或多个存储有计算机可读指令的非易失性可读存储介质。该一个或多个存储有计算机可读指令的非易失性可读存储介质中，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行实施例1中跨平台用户权限管理方法，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现实施例2中跨平台用户权限管理装置中各模块/单元的功能，为避免重复，这里不再赘述。
可以理解地，一个或多个存储有计算机可读指令的非易失性可读存储介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号和电信信号等。
实施例4
图5是本申请一实施例提供的计算机设备的示意图。如图5所示，该实施例的计算机设备60包括：处理器61、存储器62以及存储在存储器62中并可在处理器61上运行的计算机可读指令63。处理器61执行计算机可读指令63时实现上述实施例1中跨平台用户权限管理方法的步骤，例如图1所示的步骤S10至S40。或者，处理器61执行计算机可读指令63时实现上述实施例2中跨平台用户权限管理装置各模块/单元的功能，例如图4所示的原始用户权限管理数据获取模块10、目标用户权限获取模块20、目标平台标识获取模块30和目标用户权限发送模块40的功能，以避免重复，此处不一一赘述。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含 在本申请的保护范围之内。

Claims (20)

  1. 一种跨平台用户权限管理方法，其特征在于，包括：
    获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
    基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
    若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
    将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
  2. 如权利要求1所述的跨平台用户权限管理方法，其特征在于，所述基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限，包括：
    基于所述用户角色，确定所述用户角色在关联业务平台中的关联用户等级；
    将所述关联业务平台中，所述关联用户等级以下的原始用户权限作为关联用户权限；
    将每一原始用户ID对应的所述关联用户权限和所述原始用户权限进行整合，作为所述目标用户权限。
  3. 如权利要求2所述的跨平台用户权限管理方法，其特征在于，所述基于所述用户角色，确定所述用户角色在关联业务平台中的关联用户等级，包括：
    基于所述用户角色，采用预先设置的用户等级转换表，确定所述用户角色在所述关联业务平台中的关联用户等级。
  4. 如权利要求1所述的跨平台用户权限管理方法，其特征在于，所述将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台，包括：
    将所述目标用户权限发送给与所述原始用户ID对应的业务平台，并将所述目标用户权限中的关联用户权限和对应的原始用户ID发送给所述关联业务平台。
  5. 如权利要求1所述的跨平台用户权限管理方法，其特征在于，所述将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台，包括：
    采用预先设置的URI将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
  6. 如权利要求1所述的跨平台用户权限管理方法，其特征在于，所述跨平台用户权限 管理方法还包括：
    获取用户权限变更请求，所述用户权限变更请求包括变更用户权限管理数据，所述变更用户权限管理数据包括变更用户ID或变更角色；
    基于所述变更角色，获取变更用户权限管理数据，对至少两个所述业务平台中的变更用户权限管理数据进行整合处理，获取与每一原始用户ID相对应的变更用户权限；或者，
    基于所述变更用户ID，获取变更用户权限管理数据，对至少两个业务平台中的变更用户权限管理数据进行整合处理，获取变更用户ID对应的变更用户权限；
    将所述变更用户权限发送给对应的业务平台。
  7. 一种跨平台用户权限管理装置，其特征在于，包括：
    原始用户权限管理数据获取模块，用于获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
    目标用户权限获取模块，用于基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
    目标平台标识获取模块，用于若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
    目标用户权限发送模块，用于将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
  8. 如权利要求7所述的跨平台用户权限管理装置，其特征在于，所述目标用户权限获取模块，包括：
    用户等级获取单元，用于基于所述用户角色，确定所述用户角色在关联业务平台中的用户等级；
    关联用户权限获取单元，用于将所述关联业务平台中，所述用户等级以下的原始用户权限作为关联用户权限；
    目标用户权限获取单元，用于将每一原始用户ID对应的所述关联用户权限和所述原始用户权限进行整合，作为所述目标用户权限。
  9. 一种计算机设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包 括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
    基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
    若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
    将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
  10. 如权利要求9所述的计算机设备，其特征在于，所述基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限，包括：
    基于所述用户角色，确定所述用户角色在关联业务平台中的关联用户等级；
    将所述关联业务平台中，所述关联用户等级以下的原始用户权限作为关联用户权限；
    将每一原始用户ID对应的所述关联用户权限和所述原始用户权限进行整合，作为所述目标用户权限。
  11. 如权利要求10所述的计算机设备，其特征在于，所述基于所述用户角色，确定所述用户角色在关联业务平台中的关联用户等级，包括：
    基于所述用户角色，采用预先设置的用户等级转换表，确定所述用户角色在所述关联业务平台中的关联用户等级。
  12. 如权利要求9所述的计算机设备，其特征在于，所述将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台，包括：
    将所述目标用户权限发送给与所述原始用户ID对应的业务平台，并将所述目标用户权限中的关联用户权限和对应的原始用户ID发送给所述关联业务平台。
  13. 如权利要求9所述的计算机设备，其特征在于，所述将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台，包括：
    采用预先设置的URI将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
  14. 如权利要求9所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    获取用户权限变更请求，所述用户权限变更请求包括变更用户权限管理数据，所述变更用户权限管理数据包括变更用户ID或变更角色；
    基于所述变更角色，获取变更用户权限管理数据，对至少两个所述业务平台中的变更 用户权限管理数据进行整合处理，获取与每一原始用户ID相对应的变更用户权限；或者，
    基于所述变更用户ID，获取变更用户权限管理数据，对至少两个业务平台中的变更用户权限管理数据进行整合处理，获取变更用户ID对应的变更用户权限；
    将所述变更用户权限发送给对应的业务平台。
  15. 一个或多个存储有计算机可读指令的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器实现如下步骤：
    获取至少两个业务平台发送的原始用户权限管理数据，所述原始用户权限管理数据包括原始用户ID、用户角色和原始用户权限，所述原始用户权限管理数据与平台标识关联；
    基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限；
    若所述目标用户权限携带有跨平台标识，则获取与所述跨平台标识相对应的至少两个目标平台标识；
    将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
  16. 如权利要求15所述的非易失性可读存储介质，其特征在于，所述基于所述用户角色，对至少两个所述业务平台中的原始用户权限进行整合处理，获取与每一原始用户ID相对应的目标用户权限，包括：
    基于所述用户角色，确定所述用户角色在关联业务平台中的关联用户等级；
    将所述关联业务平台中，所述关联用户等级以下的原始用户权限作为关联用户权限；
    将每一原始用户ID对应的所述关联用户权限和所述原始用户权限进行整合，作为所述目标用户权限。
  17. 如权利要求16所述的非易失性可读存储介质，其特征在于，所述基于所述用户角色，确定所述用户角色在关联业务平台中的关联用户等级，包括：
    基于所述用户角色，采用预先设置的用户等级转换表，确定所述用户角色在所述关联业务平台中的关联用户等级。
  18. 如权利要求15所述的非易失性可读存储介质，其特征在于，所述将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台，包括：
    将所述目标用户权限发送给与所述原始用户ID对应的业务平台，并将所述目标用户权限中的关联用户权限和对应的原始用户ID发送给所述关联业务平台。
  19. 如权利要求15所述的非易失性可读存储介质，其特征在于，所述将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台，包括：
    采用预先设置的URI将所述目标用户权限发送给与至少两个目标平台标识相对应的业务平台。
  20. 如权利要求15所述的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还实现如下步骤：
    获取用户权限变更请求，所述用户权限变更请求包括变更用户权限管理数据，所述变更用户权限管理数据包括变更用户ID或变更角色；
    基于所述变更角色，获取变更用户权限管理数据，对至少两个所述业务平台中的变更用户权限管理数据进行整合处理，获取与每一原始用户ID相对应的变更用户权限；或者，
    基于所述变更用户ID，获取变更用户权限管理数据，对至少两个业务平台中的变更用户权限管理数据进行整合处理，获取变更用户ID对应的变更用户权限；
    将所述变更用户权限发送给对应的业务平台。
PCT/CN2018/081507 2018-02-27 2018-04-02 跨平台用户权限管理方法、装置、计算机设备及存储介质 WO2019165668A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810161846.1A CN108416195B (zh) 2018-02-27 2018-02-27 跨平台用户权限管理方法、装置、计算机设备及存储介质
CN201810161846.1 2018-02-27

Publications (1)

Publication Number Publication Date
WO2019165668A1 true WO2019165668A1 (zh) 2019-09-06

Family

ID=63129118

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081507 WO2019165668A1 (zh) 2018-02-27 2018-04-02 跨平台用户权限管理方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN108416195B (zh)
WO (1) WO2019165668A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112163833A (zh) * 2020-09-27 2021-01-01 北京金山云网络技术有限公司 权限管理方法、装置和系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111324778B (zh) * 2020-01-22 2024-04-30 先进新星技术(新加坡)控股有限公司 数据、业务处理方法、装置及电子设备
CN113242310B (zh) * 2020-06-30 2024-04-12 浙江口碑网络技术有限公司 基于小程序实现服务的方法及装置
CN113742749B (zh) * 2021-09-10 2024-03-29 广州市奥威亚电子科技有限公司 平台用户权限管理方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101714920A (zh) * 2008-10-07 2010-05-26 英业达股份有限公司 集中多服务帐号的权限管理系统及其方法
CN102882715A (zh) * 2012-09-21 2013-01-16 北京国电通网络技术有限公司 一种权限管理系统
CN105894159A (zh) * 2014-12-03 2016-08-24 北京航天长峰科技工业集团有限公司 一种跨领域跨平台的用户统一管理系统的实现方法
TW201721530A (zh) * 2015-12-01 2017-06-16 Chunghwa Telecom Co Ltd 多元權限身分識別與存取策略管理系統

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7298734B2 (en) * 2001-03-05 2007-11-20 Qwest Communications International, Inc. Method and system communication system message processing based on classification criteria
JP2002312731A (ja) * 2001-04-12 2002-10-25 Nec Corp 特典ポイント共通化システム
CN101656625A (zh) * 2008-08-18 2010-02-24 中兴通讯股份有限公司 一种基于企业融合通讯的分布式策略管理方法
CN102664967A (zh) * 2012-05-18 2012-09-12 北京慧创新盈科技有限公司 跨平台的个人信息交互方法和系统及后台服务器
CN103684878B (zh) * 2013-12-30 2017-01-25 大唐移动通信设备有限公司 一种操作命令参数管控方法和设备
CN103853970A (zh) * 2014-03-27 2014-06-11 浪潮软件集团有限公司 一种将多个web应用系统的操作权限集成的方法
CN105262725B (zh) * 2015-09-08 2018-06-22 浪潮(北京)电子信息产业有限公司 一种账号共享控制方法和系统
CN106682487A (zh) * 2016-11-04 2017-05-17 浙江蘑菇加电子商务有限公司 一种用户权限管理方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101714920A (zh) * 2008-10-07 2010-05-26 英业达股份有限公司 集中多服务帐号的权限管理系统及其方法
CN102882715A (zh) * 2012-09-21 2013-01-16 北京国电通网络技术有限公司 一种权限管理系统
CN105894159A (zh) * 2014-12-03 2016-08-24 北京航天长峰科技工业集团有限公司 一种跨领域跨平台的用户统一管理系统的实现方法
TW201721530A (zh) * 2015-12-01 2017-06-16 Chunghwa Telecom Co Ltd 多元權限身分識別與存取策略管理系統

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112163833A (zh) * 2020-09-27 2021-01-01 北京金山云网络技术有限公司 权限管理方法、装置和系统

Also Published As

Publication number Publication date
CN108416195A (zh) 2018-08-17
CN108416195B (zh) 2020-09-25

Similar Documents

Publication Publication Date Title
US11128465B2 (en) Zero-knowledge identity verification in a distributed computing system
JP7037555B2 (ja) サービス層のためのアクセス制御ポリシーの同期
US11082226B2 (en) Zero-knowledge identity verification in a distributed computing system
WO2019165668A1 (zh) 跨平台用户权限管理方法、装置、计算机设备及存储介质
US9672053B2 (en) Service request processing
US20170012958A1 (en) Techniques for credential generation
US20160219109A1 (en) Cloud storage brokering service
US10924497B2 (en) Just-in-time access based on geolocation to maintain control of restricted data in cloud computing environments
US10848522B2 (en) Just-in-time access based on screening criteria to maintain control of restricted data in cloud computing environments
WO2020238359A1 (zh) 分区授权方法、装置、设备及计算机可读存储介质
WO2020168692A1 (zh) 海量数据共享方法、开放共享平台及电子设备
WO2018095326A1 (zh) 访问权限的确定方法和装置、终端
GB2464397A (en) Accessing dynamic content on a web server using a default anonymous user account and cached logons of the web site owner.
US11556386B2 (en) Synthesizing a resource request to obtain resource identifier based on extracted unified model, user requirement and policy requirements to allocate resources
US9766881B2 (en) Social project management system and marketplace
US11297501B2 (en) Firewall discovery and management
US9237156B2 (en) Systems and methods for administrating access in an on-demand computing environment
WO2020001162A1 (zh) 容器管理方法、装置和设备
US9015790B2 (en) Integrating sudo rules with entities represented in an LDAP directory
US11546307B2 (en) Method to implement multi-tenant/shared Redis cluster using envoy
US9256641B1 (en) Dynamic optimization of data aggregation
US8108523B2 (en) Automatic extension of distributed managed ranges in a multi-master system
CN103902637B (zh) 用于向用户提供计算资源的方法和装置
US20230086068A1 (en) Enabling an action based on a permission identifier for real-time identity resolution in a distributed system
US11494500B1 (en) Account security configuration replication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18907800

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 30/11/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18907800

Country of ref document: EP

Kind code of ref document: A1