WO2021139319A1 - 多平台权限统一管理方法、装置、终端及存储介质 - Google Patents
多平台权限统一管理方法、装置、终端及存储介质 Download PDFInfo
- Publication number
- WO2021139319A1 WO2021139319A1 PCT/CN2020/123194 CN2020123194W WO2021139319A1 WO 2021139319 A1 WO2021139319 A1 WO 2021139319A1 CN 2020123194 W CN2020123194 W CN 2020123194W WO 2021139319 A1 WO2021139319 A1 WO 2021139319A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- party platform
- authority
- label
- target
- Prior art date
Links
- 238000007726 management method Methods 0.000 title claims abstract description 61
- 230000014509 gene expression Effects 0.000 claims abstract description 108
- 238000000034 method Methods 0.000 claims abstract description 53
- 238000010276 construction Methods 0.000 claims abstract description 10
- 230000001360 synchronised effect Effects 0.000 claims description 8
- 230000005540 biological transmission Effects 0.000 claims description 6
- 230000008520 organization Effects 0.000 claims description 3
- 230000007613 environmental effect Effects 0.000 abstract description 3
- 230000001737 promoting effect Effects 0.000 abstract 1
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000008878 coupling Effects 0.000 description 4
- 238000010168 coupling process Methods 0.000 description 4
- 238000005859 coupling reaction Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
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/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
Definitions
- This application relates to the technical field of authority management, and in particular to a method, device, terminal and storage medium for unified multi-platform authority management.
- the existing management of platform authority data is often carried out on a single platform, and different levels of users are processed according to the differentiated and hierarchical processing, so that users of different levels can obtain fixed authority data.
- the existing multi-platform account permission management method generally classifies users into different categories based on the authentication business, and then binds the different categories of users with the permission data.
- the method has poor uniformity and scalability, and the permission setting method is too rigid to meet the individual needs of different platforms.
- the present application provides a method, device, terminal, and storage medium for unified management of multi-platform permissions to solve the problem that the existing multi-platform permission management methods are too rigid.
- a technical solution adopted in this application is to provide a method for unified management of multi-platform permissions, including: obtaining user information provided by a third-party platform.
- the user information includes label information.
- the label information is set when creating user information. Set; receive at least one label expression fed back by the third-party platform and the permissions configured for the label expression; after querying the target user group corresponding to each label expression, configure the corresponding permission for the target user group to obtain the permission configuration information; Synchronize authority configuration information to third-party platforms.
- a multi-platform authority unified management device including: an acquisition module for acquiring user information provided by a third-party platform.
- the user information includes label information and label information. Set when creating user information; receiving module, used to receive at least one label expression fed back by a third-party platform, and permissions configured for label expressions; query module, used to query the target user group corresponding to each label expression After that, configure the corresponding permissions for the target user group to obtain the permission configuration information; the synchronization module is used to synchronize the permission configuration information to the third-party platform.
- a terminal including a memory, a processor, and a program file stored in the memory and capable of running on the processor, where the processor executes the program file when the program file is executed.
- the processor executes the program file when the program file is executed.
- Another technical solution adopted in this application is to provide a storage medium in which a program file capable of implementing a unified management method for multi-platform permissions is stored, and the following steps are implemented when the program file is executed by a processor:
- the user information includes label information, which is set when the user information is created; receives at least one label expression fed back by the third-party platform, and the authority configured for the label expression; queries each label expression After corresponding to the target user group, configure the corresponding permissions for the target user group to obtain the permission configuration information; synchronize the permission configuration information to the third-party platform.
- the beneficial effect of this application is that the multi-platform authority unified management method of this application obtains the label information of the user of the third-party platform, configures the corresponding authority for the label expression constructed based on the label information, and then uses the label expression to confirm the target user After the group, configure the permissions for the target user group uniformly, and finally synchronize the permission configuration information to the third-party platform.
- the method of label expression can realize the configuration of user permissions according to the corresponding characteristic information of users on different third-party platforms.
- the third-party platform can set label expressions that meet its own needs, which meets the personalized configuration requirements of different platforms, and a user can correspond to multiple label expressions, and can freely combine permissions through different label expressions.
- the multi-platform permission unified management method of this application can also be applied to smart government affairs/smart city management/smart communities/smart security/smart logistics/smart medical treatment/smart education/smart environmental protection/smart transportation scenarios to promote the construction of smart cities.
- FIG. 1 is a schematic flowchart of a method for unified management of multi-platform permissions according to a first embodiment of the present application
- FIG. 2 is a schematic flowchart of a method for unified management of multi-platform permissions according to a second embodiment of the present application
- FIG. 3 is a schematic flowchart of a method for unified management of multi-platform permissions according to a third embodiment of the present application
- FIG. 4 is a schematic flowchart of a method for unified management of multi-platform permissions according to a fourth embodiment of the present application.
- Fig. 5 is a schematic diagram of functional modules of a multi-platform authority unified management device according to an embodiment of the present application
- FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present application.
- FIG. 7 is a schematic structural diagram of a storage medium according to an embodiment of the present application.
- first”, “second”, and “third” in this application are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined with “first”, “second”, and “third” may explicitly or implicitly include at least one of the features.
- "a plurality of” means at least two, such as two, three, etc., unless otherwise specifically defined. All directional indications (such as up, down, left, right, front, back%) in the embodiments of this application are only used to explain the relative positional relationship between the components in a specific posture (as shown in the figure) , Movement status, etc., if the specific posture changes, the directional indication will also change accordingly.
- FIG. 1 is a schematic flowchart of a method for unified management of multi-platform permissions according to a first embodiment of the present application. It should be noted that if there is substantially the same result, the method of the present application is not limited to the sequence of the process shown in FIG. 1. As shown in Figure 1, the method includes steps:
- Step S101 Obtain user information provided by a third-party platform, the user information includes tag information, and the tag information is set when the user information is created.
- the multi-platform authority unified management method of this application can be applied to the authority management platform. Before performing authority management on the third-party platform, it needs to be associated with the third-party platform. Data communication can be carried out between.
- step S101 obtain user information that needs to configure permissions from a third-party platform, where the user information includes tag information, and the tag information is set when the user information is created.
- the label information can be the label information that is actively set when the user information is created, such as the client type used by the user, the system version number used by the user, etc.; on the other hand, the label information can also be Part of the characteristic information that comes with the user information, such as: department, rank, establishment, in-service status, organizational structure, etc.
- step S101 before step S101, it further includes: after receiving the login information initiated by the third-party platform, identifying the current system ID in the login information; The target system ID that matches the current system ID; if it exists, it associates with the authority management system of the third-party platform, and allows the third-party platform to call the interface for data transmission.
- the system ID is the unique identification number generated by the third-party platform for the docking authority management platform and the third-party platform
- the login information initiated by the third-party platform is received, it is determined whether the login information includes the current third-party platform's Current system ID, if there is a current system ID, then match the current system ID with each system ID to confirm whether there is a matching target system ID, if there is a target system ID, associate the authority management system of the third-party platform, and allow
- the third-party platform calls the interface for data transmission. After linking the authority management system of the third-party platform, the third-party platform can only see the authority configuration information of this platform, and can only modify the authority configuration information of this platform.
- Step S102 Receive at least one label expression fed back by the third-party platform and the permissions configured for the label expression.
- the label expression can be set by the authority administrator of the third-party platform according to the needs of its own platform, and the authority administrator can construct one or more label expressions, for example: set the first according to the client type and system version number.
- Each label expression can be configured with one or more corresponding permissions.
- the label expression is composed of one or more of department, rank, organization, in-service status, organizational structure, client type, and system version number. After the label expression is established, the label expression and permissions are associated.
- Step S103 After querying the target user group corresponding to each label expression, configure corresponding permissions for the target user group to obtain permission configuration information.
- step S103 the label information set in the label expression is used to query the matched target user group, and the permission corresponding to the label expression is configured to the target user group to obtain permission configuration information.
- a user can be the target user group corresponding to one or more label expressions. Therefore, when a user belongs to the target user group of multiple label expressions, it can be configured according to multiple label expressions. Multiple permissions realize the free combination of different permissions with strong flexibility.
- Step S104 Synchronize the authority configuration information to the third-party platform.
- the multi-platform authority unified management method of the first embodiment of the present application obtains the label information of the user of the third-party platform, configures the corresponding authority for the label expression constructed based on the label information, and then uses the label expression to confirm the target user group, Configure permissions for the target user group uniformly, and finally synchronize the permissions configuration information to the third-party platform. It uses label expressions to configure user permissions based on the corresponding characteristics of users on different third-party platforms.
- the platform can set label expressions that meet its own needs, which meets the personalized configuration requirements of different platforms, and a user can correspond to multiple label expressions, and the permissions can be freely combined through different label expressions.
- the unified management method of multi-platform permissions can also be applied to smart government affairs/smart city management/smart community/smart security/smart logistics/smart healthcare/smart education/smart environmental protection/smart transportation scenarios to promote the construction of smart cities.
- Fig. 2 is a schematic flowchart of a method for unified management of multi-platform permissions according to a second embodiment of the present application. It should be noted that if there is substantially the same result, the method of the present application is not limited to the sequence of the process shown in FIG. 2. As shown in Figure 2, the method includes steps:
- Step S201 Obtain user information provided by a third-party platform, the user information includes tag information, and the tag information is set when the user information is created.
- step S201 in FIG. 2 is similar to step S101 in FIG. 1. For the sake of brevity, it will not be repeated here.
- Step S202 Receive at least one label expression fed back by the third-party platform and the permissions configured for the label expression.
- step S202 in FIG. 2 is similar to step S102 in FIG.
- Step S203 After querying the target user group corresponding to each label expression, configure corresponding permissions for the target user group to obtain permission configuration information.
- step S203 in FIG. 2 is similar to step S103 in FIG.
- Step S204 Synchronize the authority configuration information to the third-party platform.
- step S204 in FIG. 2 is similar to step S104 in FIG.
- Step S205 When it is detected that the tag information is changed, the authority of the user corresponding to the tag information is adjusted based on the changed tag information and the tag expression.
- step S205 the user’s label information is periodically synchronized from the third-party platform to confirm whether the label information has changed.
- the corresponding label expression is queried according to the changed user label information, and then the label
- the permission of the expression is allocated to the user, and the previous permission of the user is overwritten, thereby completing the update of the user's permission.
- the position in the user label information is a salesperson, and now it is modified as a business manager, you need to match the corresponding label expression according to the label information of "the position is business manager", and then configure the corresponding permissions after obtaining the corresponding permissions, covering Remove the previous permission of "the rank is a salesman".
- the label information of the user of the third-party platform it is also possible to monitor the change of the label information of the user of the third-party platform. If the label information is detected to be changed, the user's authority will be adjusted immediately according to the changed label information, which is relative to the timing synchronization of the user’s label. The information has better timeliness, ensuring that the user's authority can be updated in a timely manner.
- the multi-platform authority unified management method of the second embodiment of the present application is based on the first embodiment, by monitoring the change of the label information of the third-party platform user, and timely updating and adjusting the authority of the user whose label information has changed, so as to avoid It affects the use of users, and the update of user permissions is automatically completed without human involvement in adjustments, which further reduces manpower consumption and improves office efficiency.
- FIG. 3 is a schematic flowchart of a method for unified management of multi-platform permissions according to a third embodiment of the present application. It should be noted that if there are substantially the same results, the method of the present application is not limited to the sequence of the process shown in FIG. 3. As shown in Figure 3, the method includes steps:
- Step S301 Obtain user information provided by the third-party platform, the user information includes tag information, and the tag information is set when the user information is created.
- step S301 in FIG. 3 is similar to step S101 in FIG.
- Step S302 Receive at least one label expression fed back by the third-party platform and the permissions configured for the label expression.
- step S302 in FIG. 3 is similar to step S102 in FIG.
- Step S303 After querying the target user group corresponding to each label expression, configure corresponding permissions for the target user group to obtain permission configuration information.
- step S303 in FIG. 3 is similar to step S103 in FIG.
- Step S304 Synchronize the authority configuration information to the third-party platform.
- step S304 in FIG. 3 is similar to step S104 in FIG.
- Step S305 Associate the approval system of the third-party platform.
- the approval system refers to a third-party platform management system for newly added users.
- Step S306 When it is detected that the new user information has been approved by the approval system, corresponding permissions are configured for the corresponding new user based on the label information and label expression of the new user information.
- step S305 ⁇ step S306 through the approval system of the associated third-party platform, when the approval system approves the new user information, the label information of the new user information is obtained, and the label expression and the new label information are combined one by one Match, get the matched label expression, and then configure the permissions of the matched label expression to the newly added user. Therefore, when adding a new user, you only need to set the label information of the new user to automatically complete the addition. User's permission configuration.
- the multi-platform authority unified management method of the third embodiment of the present application is based on the first embodiment.
- the authority configuration is automatically completed according to the label information of the new user. Additional manual configuration is required, which further reduces manpower consumption and improves work efficiency.
- FIG. 4 is a schematic flowchart of a method for unified management of multi-platform permissions according to a fourth embodiment of the present application. It should be noted that if there is substantially the same result, the method of the present application is not limited to the sequence of the process shown in FIG. 4. As shown in Figure 4, the method includes the steps:
- Step S401 Obtain user information provided by a third-party platform, the user information includes tag information, and the tag information is set when the user information is created.
- step S401 in FIG. 4 is similar to step S101 in FIG.
- Step S402 Receive at least one label expression fed back by the third-party platform and the permissions configured for the label expression.
- step S402 in FIG. 4 is similar to step S102 in FIG.
- Step S403 After querying the target user group corresponding to each label expression, configure corresponding permissions for the target user group to obtain permission configuration information.
- step S403 in FIG. 4 is similar to step S103 in FIG.
- Step S404 Synchronize the authority configuration information to the third-party platform.
- step S404 in FIG. 4 is similar to step S104 in FIG. 1, and for the sake of brevity, it will not be repeated here.
- Step S405 Receive permission application information sent by the third-party platform, where the permission application information includes target user information and target permission information.
- Step S406 Configure corresponding authority for the target user information according to the target authority information.
- step S405 to step S406 when a permission application request initiated by a third-party platform is received, target permissions are configured for the target user according to the target user information and target permission information in the permission application information.
- step S406 the method further includes:
- Step S407 Initiate a label construction query to the third-party platform.
- step S407 after the target authority is configured for the target user, a label construction query is initiated to the third-party platform according to the target label information and target authority information of the target user to confirm whether to construct a label expression according to the label information of the target user.
- Step S408 When receiving a label building instruction fed back by the third-party platform, generate a target label expression according to the target label information in the target user information, and configure target authority information for the target label expression.
- step S408 when receiving the tag building instruction fed back by the third-party platform, the target tag information in the target user information is obtained, and then the target tag expression is constructed based on the target tag information.
- the target user group corresponding to the target tag expression is the user For all users whose information contains the target label information, configure target authority information for the target label expression.
- Step S409 The authority configuration information is updated and synchronized to the authority management system of the third-party platform.
- step S409 after the target label expression is obtained, the permissions of all users of the third-party platform are updated according to the target label expression, and the updated permission configuration information is obtained, and then synchronized to the permission management system of the third-party platform, thereby Uniformly update or uniformly configure the permissions of users containing target tag information.
- the multi-platform authority unified management method of the fourth embodiment of the present application is based on the first embodiment, by configuring the target authority for a target user, and then using the target label information of the target user to construct the target label expression, using the target label expression
- the unified authority update or unified configuration authority is performed on all users containing the target label information. It does not require manual construction of label expressions, which further simplifies the process of building label expressions and improves work efficiency.
- Fig. 5 is a schematic diagram of functional modules of a multi-platform authority unified management device according to an embodiment of the present application.
- the device 50 includes an acquisition module 51, a receiving module 52, an inquiry module 53 and a synchronization module 54.
- the obtaining module 51 is used to obtain user information provided by a third-party platform, the user information includes tag information, and the tag information is set when the user information is created;
- the receiving module 52 is configured to receive at least one label expression fed back by the third-party platform and the permissions configured for the label expression;
- the query module 53 is used to query the target user group corresponding to each label expression, configure corresponding permissions for the target user group, and obtain permission configuration information;
- the synchronization module 54 is used to synchronize the authority configuration information to the third-party platform.
- the synchronization module 54 synchronizes the authority configuration information to the third-party platform, when it detects that the tag information is changed, adjust the authority of the user corresponding to the tag information based on the changed tag information and tag expression.
- the synchronization module 54 synchronizes the authority configuration information to the third-party platform, it is also used to associate the approval system of the third-party platform; when it is detected that the approval system approves the new user information, it is based on the new user information
- the synchronization module 54 synchronizes the authority configuration information to the third-party platform, it is also used to receive authority application information sent by the third-party platform.
- the authority application information includes target user information and target authority information; according to the target authority information Configure the corresponding permissions for the target user information.
- the synchronization module 54 configures the corresponding authority for the target user information according to the target authority information, it is also used to: initiate a label building query to the third-party platform; when receiving a label building instruction fed back by the third-party platform, according to the target user
- the target label information in the information generates the target label expression, and configures the target authority information for the target label expression; the authority configuration information is updated and synchronized to the authority management system of the third-party platform.
- the obtaining module 51 obtains the user information provided by the third-party platform, it is also used to: after receiving the login information initiated by the third-party platform, identify the current system ID in the login information; The matching target system ID; if it exists, it is associated with the authority management system of the third-party platform, and the third-party platform is allowed to call the interface for data transmission.
- the label expression is composed of one or more of department, rank, organization, in-service status, organizational structure, client type, and system version number.
- FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the application.
- the terminal 60 includes a processor 61 and a memory 62 coupled to the processor 61.
- the memory 62 stores program files used to implement the multi-platform authority unified management method described in any of the foregoing embodiments.
- the processor 61 is configured to execute the program files stored in the memory 62 to uniformly manage the permissions of multiple platforms.
- the processor 61 may also be referred to as a CPU (Central Processing Unit, central processing unit).
- the processor 61 may be an integrated circuit chip with signal processing capabilities.
- the processor 61 may also be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components .
- the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
- FIG. 7 is a schematic structural diagram of a storage medium according to an embodiment of the application.
- the storage medium of the embodiment of the present application stores a program file 71 that can implement all the above methods.
- the program file 71 can be stored in the above storage medium in the form of a software product, and includes several instructions to enable a computer device (which can It is a personal computer, a server, or a network device, etc.) or a processor (processor) that executes all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes, or terminal devices such as computers, servers, mobile phones, and tablets.
- the storage medium may be non-volatile or volatile.
- the disclosed terminal, device, and method may be implemented in other ways.
- the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
- the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. The above are only implementations of this application, and do not limit the scope of this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of this application, or directly or indirectly applied to other related technical fields, The same reasoning is included in the scope of patent protection of this application.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Storage Device Security (AREA)
Abstract
一种多平台权限统一管理方法、装置、终端及存储介质，其中方法包括：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定（S101）；接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限（S102）；查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息（S103）；将权限配置信息同步至第三方平台（S104）。该方法通过标签表达式，再基于标签表达式和用户的标签信息配置权限，使得不同的平台均可进行个性化的权限配置，其可应用于智慧政务/智慧城管/智慧社区/智慧安防/智慧物流/智慧医疗/智慧教育/智慧环保/智慧交通场景中，从而推动智慧城市的建设。
Description
本申请要求于2020年08月06日提交中国专利局、申请号为202010784276.9，发明名称为“多平台权限统一管理方法、装置、终端及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请涉及权限管理技术领域，特别是涉及一种多平台权限统一管理方法、装置、终端及存储介质。
现有对平台权限数据的管理，往往在单个平台上来进行，根据不同用户的差异化分级处理，使不同级别的用户获得固定的权限数据。此外，除单平台权限数据管理方法外，现有多平台账户权限管理方法，一般基于认证业务将用户区分为不同类别，然后，将不同类别的用户与权限数据绑定。然而，由于这种方法中权限数据与业务的关系过分耦合，发明人发现该方法统一性和拓展性较差，权限设置方式过于呆板，难以满足不同平台的个性化需求。
本申请提供一种多平台权限统一管理方法、装置、终端及存储介质，以解决现有多平台权限管理方法权限设置方式过于呆板的问题。
为解决上述技术问题，本申请采用的一个技术方案是：提供一种多平台权限统一管理方法，包括：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定；接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限；查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息；将权限配置信息同步至第三方平台。
为解决上述技术问题，本申请采用的另一个技术方案是：提供一种多平台权限统一管理装置，包括：获取模块，用于获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定；接收模块，用于接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限；查询模块，用于查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息；同步模块，用于将权限配置信息同步至第三方平台。
为解决上述技术问题，本申请采用的再一个技术方案是：提供一种终端，包括存储器、处理器以及存储在存储器上并可在处理器上运行的程序文件，其中，处理器执行程序文件时实现以下步骤：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定；接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限；查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息；将权限配置信息同步至第三方平台。
为解决上述技术问题，本申请采用的再一个技术方案是：提供一种存储介质，其中，存储有能够实现多平台权限统一管理方法的程序文件，程序文件被处理器执行时实现以下步骤：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定；接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限；查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息；将权限配置信息同步至第三方平台。
本申请的有益效果是：本申请的多平台权限统一管理方法通过获取第三方平台的用户的标签信息，再为基于标签信息构建的标签表达式配置相应的权限，然后利用标签表达式确认目标用户群体后，为该目标用户群体统一配置权限，最后将权限配置信息同步给第三方平台，其采用标签表达式的方式可以根据不同第三方平台的用户的相应特征信息来实现配置用户的权限，不同的第三方平台可以设置符合自身需要的标签表达式，满足了不同平台的个性化配置需求，并且一个用户可以对应多个标签表达式，可以通过不同的标签表达式进行权限之间的自由组合，本申请的多平台权限统一管理方法还可应用于智慧政务/智慧城管/智慧社区/智慧安防/智慧物流/智慧医疗/智慧教育/智慧环保/智慧交通场景中，从而推动智慧城市的建设。
图1是本申请第一实施例的多平台权限统一管理方法的流程示意图；
图2是本申请第二实施例的多平台权限统一管理方法的流程示意图；
图3是本申请第三实施例的多平台权限统一管理方法的流程示意图；
图4是本申请第四实施例的多平台权限统一管理方法的流程示意图；
图5是本申请实施例的多平台权限统一管理装置的功能模块示意图；
图6是本申请实施例的终端的结构示意图；
图7是本申请实施例的存储介质的结构示意图。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅是本申请的一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请中的术语“第一”、“第二”、“第三”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”、“第三”的特征可以明示或者隐含地包括至少一个该特征。本申请的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。本申请实施例中所有方向性指示（诸如上、下、左、右、前、后……）仅用于解释在某一特定姿态（如附图所示）下各部件之间的相对位置关系、运动情况等，如果该特定姿态发生改变时，则该方向性指示也相应地随之改变。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
图1是本申请第一实施例的多平台权限统一管理方法的流程示意图。需注意的是，若有实质上相同的结果，本申请的方法并不以图1所示的流程顺序为限。如图1所示，该方法包括步骤：
步骤S101：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定。
需要理解的是，本申请的多平台权限统一管理方法可以应用于权限管理平台，在对第三方平台进行权限管理之前，需要与第三方平台进行关联，关联后的权限管理平台与第三方平台之间可以进行数据通信。
在步骤S101中，从第三方平台中获取需要配置权限的用户信息，其中，该用户信息包括标签信息，标签信息在建立用户信息时设定。需要说明的是，一方面，该标签信息可以为建立用户信息时主动设置的标签信息，例如：用户使用的客户端类型、用户使用的系统版本号等；另一方面，该标签信息也可以为用户信息中自带的部分特征信息，例如：部门、职级、编制、在职状态、组织架构等。
进一步的，为了方便对多个第三方平台进行管理，在一些实施例中，步骤S101之前还包括：接收到第三方平台发起的登录信息后，识别登录信息中的当前系统ID；判断是否存在与当前系统ID匹配的目标系统ID；若存在，则关联第三方平台的权限管理系统，并允许第三方平台调用接口以进行数据传输。
具体地，系统ID为对接权限管理平台和第三方平台时，为第三方平台生成的唯一识别号，当接收到第三方平台发起的登录信息时，判断该登录信息中是否存在当前第三方平台的当前系统ID，若存在当前系统ID，再将当前系统ID与每个系统ID进行匹配以确认是否存在匹配的目标系统ID，若存在目标系统ID，则关联第三方平台的权限管理系统，并允许第三方平台调用接口以进行数据传输。在关联第三方平台的权限管理系统后，第三方平台仅可以看到本平台的权限配置信息，且只能修改本平台的权限配置信息。
步骤S102：接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限。
在步骤S102中，标签表达式可以由第三方平台的权限管理员根据自身平台需要进行设置，权限管理员可以构建一个或多个标签表达式，例如：根据客户端类型、系统版本号设置第一个标签表达式，具体为【客户端=安卓客户端】、【系统版本号=V1.15】，根据部门、职级、编制设置第二个标签表达式，具体为【部门=行政部】、【职级=行政专员】、【编制=正式编制】。每个标签表达式可以配置一个或多个相应的权限。具体地，该标签表达式由部门、职级、编制、在职状态、组织架构、客户端类型、系统版本号中的一个或多个组成。在建立好标签表达式之后，再将标签表达式与权限之间进行关联。
步骤S103：查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息。
在步骤S103中，利用标签表达式中设定的标签信息来查询匹配的目标用户群体，再将该标签表达式对应的权限配置给目标用户群体，得到权限配置信息。其中，需要说明的是，一个用户可以为一个或多个标签表达式对应的目标用户群体，因此，当一个用户属于多个标签表达式的目标用户群体时，即可根据多个标签表达式配置多条权限，实现了不同权限之间的自由组合，灵活性强。
步骤S104：将权限配置信息同步至第三方平台。
本申请第一实施例的多平台权限统一管理方法通过获取第三方平台的用户的标签信息，再为基于标签信息构建的标签表达式配置相应的权限，然后利用标签表达式确认目标用户群体后，为该目标用户群体统一配置权限，最后将权限配置信息同步给第三方平台，其采用标签表达式的方式可以根据不同第三方平台的用户的相应特征信息来实现配置用户的权限，不同的第三方平台可以设置符合自身需要的标签表达式，满足了不同平台的个性化配置需求，并且一个用户可以对应多个标签表达式，可以通过不同的标签表达式进行权限之间的自由组合，本申请的多平台权限统一管理方法还可应用于智慧政务/智慧城管/智慧社区/智慧安防/智慧物流/智慧医疗/智慧教育/智慧环保/智慧交通场景中，从而推动智慧城市的建设。
图2是本申请第二实施例的多平台权限统一管理方法的流程示意图。需注意的是，若有实质上相同的结果，本申请的方法并不以图2所示的流程顺序为限。如图2所示，该方法包括步骤：
步骤S201：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定。
在本实施例中，图2中的步骤S201和图1中的步骤S101类似，为简约起见，在此不再赘述。
步骤S202：接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限。
在本实施例中，图2中的步骤S202和图1中的步骤S102类似，为简约起见，在此不再赘述。
步骤S203：查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息。
在本实施例中，图2中的步骤S203和图1中的步骤S103类似，为简约起见，在此不再赘述。
步骤S204：将权限配置信息同步至第三方平台。
在本实施例中，图2中的步骤S204和图1中的步骤S104类似，为简约起见，在此不再赘述。
步骤S205：检测到标签信息发生变更时，基于变更后的标签信息和标签表达式调整与标签信息对应的用户的权限。
在步骤S205中，通过定时从第三方平台同步用户的标签信息，以确认标签信息是否发生变更，当用户标签信息发生变更时，根据变更后的用户标签信息查询相应的标签表达式，再将标签表达式的权限配置给该用户，并覆盖掉用户之前的权限，从而完成对用户权限的更新。例如：用户标签信息中的职级为业务员，现修改为了业务经理，则需要根据“职级为业务经理”这一标签信息去匹配相应的标签表达式，再获取到相应的权限后进行配置，覆盖掉之前“职级为业务员”时的权限。
进一步的，本实施例中，还可通过监听第三方平台用户的标签信息变更情况，监听到标签信息发生变更，则立刻根据变更后的标签信息调整用户的权限，其相对于定时同步用户的标签信息具有更好的时效性，保证能够及时更新用户的权限。
本申请第二实施例的多平台权限统一管理方法在第一实施例的基础上，通过监测第三方平台用户的标签信息的变化情况，及时对标签信息发生变化的用户的权限进行更新调整，避免影响用户使用，并且，用户权限的更新自动完成，不需要人为参与调整，进一步降低了人力消耗，提升了办公效率。
图3是本申请第三实施例的多平台权限统一管理方法的流程示意图。需注意的是，若有实质上相同的结果，本申请的方法并不以图3所示的流程顺序为限。如图3所示，该方法包括步骤：
步骤S301：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定。
在本实施例中，图3中的步骤S301和图1中的步骤S101类似，为简约起见，在此不再赘述。
步骤S302：接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限。
在本实施例中，图3中的步骤S302和图1中的步骤S102类似，为简约起见，在此不再赘述。
步骤S303：查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息。
在本实施例中，图3中的步骤S303和图1中的步骤S103类似，为简约起见，在此不再赘述。
步骤S304：将权限配置信息同步至第三方平台。
在本实施例中，图3中的步骤S304和图1中的步骤S104类似，为简约起见，在此不再赘述。
步骤S305：关联第三方平台的审批系统。
需要说明的是，该审批系统是指第三方平台的管理新增用户的系统。
步骤S306：检测到审批系统审批通过新增的用户信息时，基于新增的用户信息的标签信息和标签表达式为对应的新增用户配置相应的权限。
在步骤S305~步骤S306中，通过关联第三方平台的审批系统，当审批系统审批通过新增的用户信息时，获取到新增用户信息的标签信息，逐个将标签表达式与新增的标签信息匹配，得到匹配的标签表达式，再将匹配的标签表达式的权限配置给新增的用户，从而，在新增用户时，仅需设置好新增用户的标签信息，即可自动完成新增用户的权限配置。
本申请第三实施例的多平台权限统一管理方法在第一实施例的基础上，通过关联第三方系统的审批系统，当新增用户时，根据新增用户的标签信息自动完成权限配置，不需要人工另外配置，进一步降低了人力消耗，提升了工作效率。
图4是本申请第四实施例的多平台权限统一管理方法的流程示意图。需注意的是，若有实质上相同的结果，本申请的方法并不以图4所示的流程顺序为限。如图4所示，该方法包括步骤：
步骤S401：获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定。
在本实施例中，图4中的步骤S401和图1中的步骤S101类似，为简约起见，在此不再赘述。
步骤S402：接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限。
在本实施例中，图4中的步骤S402和图1中的步骤S102类似，为简约起见，在此不再赘述。
步骤S403：查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息。
在本实施例中，图4中的步骤S403和图1中的步骤S103类似，为简约起见，在此不再赘述。
步骤S404：将权限配置信息同步至第三方平台。
在本实施例中，图4中的步骤S404和图1中的步骤S104类似，为简约起见，在此不再赘述。
步骤S405：接收到第三方平台发送的权限申请信息，权限申请信息包括目标用户信息和目标权限信息。
步骤S406：根据目标权限信息为目标用户信息配置相应的权限。
在步骤S405~步骤S406中，当接收到第三方平台发起的权限申请请求时，根据权限申请信息中的目标用户信息和目标权限信息为目标用户配置目标权限。
进一步的，为了精简标签表达式的构建过程，在步骤S406之后，还包括：
步骤S407：向第三方平台发起标签构建询问。
在步骤S407中，在为目标用户配置目标权限之后，根据目标用户的目标标签信息和目标权限信息向第三方平台发起标签构建询问，以确认是否根据目标用户的标签信息构建标签表达式。
步骤S408：当接收到第三方平台反馈的构建标签指令时，根据目标用户信息中的目标标签信息生成目标标签表达式，且为目标标签表达式配置目标权限信息。
在步骤S408中，当接收到第三方平台反馈的构建标签指令时，获取目标用户信息中的目标标签信息，再基于目标标签信息构建目标标签表达式，目标标签表达式对应的目标用户群体即用户信息中包含目标标签信息的所有用户，再为该目标标签表达式配置目标权限信息。
步骤S409：将权限配置信息更新后同步至第三方平台的权限管理系统。
在步骤S409中，在得到目标标签表达式之后，根据目标标签表达式对第三方平台的所有用户的权限进行更新，得到更新后的权限配置信息，再同步至第三方平台的权限管理系统，从而对包含目标标签信息的用户的权限进行统一更新或统一配置。
本申请第四实施例的多平台权限统一管理方法在第一实施例的基础上，通过对一个目标用户配置目标权限，再利用该目标用户的目标标签信息构建目标标签表达式，利用目标标签表达式对包含目标标签信息的所有用户进行统一的权限更新或统一配置权限，其不需要人工构建标签表达式，进一步简化了构建标签表达式的过程，提升了工作效率。
图5是本申请实施例的多平台权限统一管理装置的功能模块示意图。如图5所示，该装置50包括获取模块51、接收模块52、查询模块53和同步模块54。
获取模块51，用于获取第三方平台提供的用户信息，用户信息包括标签信息，标签信息在建立用户信息时设定；
接收模块52，用于接收第三方平台反馈的至少一个标签表达式，以及为标签表达式配置的权限；
查询模块53，用于查询每一个标签表达式对应的目标用户群体后，为目标用户群体配置相应的权限，得到权限配置信息；
同步模块54，用于将权限配置信息同步至第三方平台。
可选地，同步模块54将权限配置信息同步至第三方平台的操作之后，还用于检测到标签信息发生变更时，基于变更后的标签信息和标签表达式调整与标签信息对应的用户的权限。
可选地，同步模块54将权限配置信息同步至第三方平台的操作之后，还用于关联第三方平台的审批系统；检测到审批系统审批通过新增的用户信息时，基于新增的用户信息的标签信息和标签表达式为对应的新增用户配置相应的权限。
可选地，同步模块54将权限配置信息同步至第三方平台的操作之后，还用于接收到第三方平台发送的权限申请信息，权限申请信息包括目标用户信息和目标权限信息；根据目标权限信息为目标用户信息配置相应的权限。
可选地，同步模块54根据目标权限信息为目标用户信息配置相应的权限之后，还用于：向第三方平台发起标签构建询问；当接收到第三方平台反馈的构建标签指令时，根据目标用户信息中的目标标签信息生成目标标签表达式，且为目标标签表达式配置目标权限信息；将权限配置信息更新后同步至第三方平台的权限管理系统。
可选地，获取模块51获取第三方平台提供的用户信息的操作之前，还用于：接收到第三方平台发起的登录信息后，识别登录信息中的当前系统ID；判断是否存在与当前系统ID匹配的目标系统ID；若存在，则关联第三方平台的权限管理系统，并允许第三方平台调用接口以进行数据传输。
可选地，标签表达式由部门、职级、编制、在职状态、组织架构、客户端类型、系统版本号中的一个或多个组成。
请参阅图6，图6为本申请实施例的终端的结构示意图。如图6所示，该终端60包括处理器61及和处理器61耦接的存储器62。
存储器62存储有用于实现上述任一实施例所述的多平台权限统一管理方法的程序文件。
处理器61用于执行存储器62存储的程序文件以对多个平台的权限进行统一管理。
其中，处理器61还可以称为CPU（Central Processing Unit，中央处理单元）。处理器61可能是一种集成电路芯片，具有信号的处理能力。处理器61还可以是通用处理器、数字信号处理器（DSP）、专用集成电路（ASIC）、现场可编程门阵列（FPGA）或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
参阅图7，图7为本申请实施例的存储介质的结构示意图。本申请实施例的存储介质存储有能够实现上述所有方法的程序文件71，其中，该程序文件71可以以软件产品的形式存储在上述存储介质中，包括若干指令用以使得一台计算机设备（可以是个人计算机，服务器，或者网络设备等）或处理器（processor）执行本申请各个实施方式所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器（ROM，Read-Only Memory）、随机存取存储器（RAM，Random Access
Memory）、磁碟或者光盘等各种可以存储程序代码的介质，或者是计算机、服务器、手机、平板等终端设备。所述存储介质可以是非易失性，也可以是易失性。
在本申请所提供的几个实施例中，应该理解到，所揭露的终端，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。以上仅为本申请的实施方式，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。
Claims (20)
1、一种多平台权限统一管理方法，其中，包括：
获取第三方平台提供的用户信息，所述用户信息包括标签信息，所述标签信息在建立所述用户信息时设定；
接收所述第三方平台反馈的至少一个标签表达式，以及为所述标签表达式配置的权限；
查询每一个所述标签表达式对应的目标用户群体后，为所述目标用户群体配置相应的权限，得到权限配置信息；
将所述权限配置信息同步至所述第三方平台。
2、根据权利要求1所述的多平台权限统一管理方法，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
检测到标签信息发生变更时，基于变更后的标签信息和所述标签表达式调整与所述标签信息对应的用户的权限。
3、根据权利要求1所述的多平台权限统一管理方法，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
关联所述第三方平台的审批系统；
检测到所述审批系统审批通过新增的用户信息时，基于所述新增的用户信息的标签信息和所述标签表达式为对应的新增用户配置相应的权限。
4、根据权利要求1所述的多平台权限统一管理方法，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
接收到所述第三方平台发送的权限申请信息，所述权限申请信息包括目标用户信息和目标权限信息；
根据所述目标权限信息为所述目标用户信息配置相应的权限。
5、根据权利要求4所述的多平台权限统一管理方法，其中，所述根据所述目标权限信息为所述目标用户信息配置相应的权限之后，还包括：
向所述第三方平台发起标签构建询问；
当接收到所述第三方平台反馈的构建标签指令时，根据所述目标用户信息中的目标标签信息生成目标标签表达式，且为所述目标标签表达式配置所述目标权限信息；
将所述权限配置信息更新后同步至所述第三方平台的权限管理系统。
6、根据权利要求1所述的多平台权限统一管理方法，其中，所述获取第三方平台提供的用户信息之前，还包括：
接收到所述第三方平台发起的登录信息后，识别所述登录信息中的当前系统ID；
判断是否存在与所述当前系统ID匹配的目标系统ID；
若存在，则关联所述第三方平台的权限管理系统，并允许所述第三方平台调用接口以进行数据传输。
7、根据权利要求1所述的多平台权限统一管理方法，其中，所述标签表达式由部门、职级、编制、在职状态、组织架构、客户端类型、系统版本号中的一个或多个组成。
8、一种多平台权限统一管理装置，其中，包括：
获取模块，用于获取第三方平台提供的用户信息，所述用户信息包括标签信息，所述标签信息在建立所述用户信息时设定；
接收模块，用于接收所述第三方平台反馈的至少一个标签表达式，以及为所述标签表达式配置的权限；
查询模块，用于查询每一个所述标签表达式对应的目标用户群体后，为所述目标用户群体配置相应的权限，得到权限配置信息；
同步模块，用于将所述权限配置信息同步至所述第三方平台。
9、一种终端，包括存储器、处理器以及存储在存储器上并可在处理器上运行的程序文件，其中，所述处理器执行所述程序文件时实现以下步骤：
获取第三方平台提供的用户信息，所述用户信息包括标签信息，所述标签信息在建立所述用户信息时设定；
接收所述第三方平台反馈的至少一个标签表达式，以及为所述标签表达式配置的权限；
查询每一个所述标签表达式对应的目标用户群体后，为所述目标用户群体配置相应的权限，得到权限配置信息；
将所述权限配置信息同步至所述第三方平台。
10、根据权利要求9所述的终端，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
检测到标签信息发生变更时，基于变更后的标签信息和所述标签表达式调整与所述标签信息对应的用户的权限。
11、根据权利要求9所述的终端，，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
关联所述第三方平台的审批系统；
检测到所述审批系统审批通过新增的用户信息时，基于所述新增的用户信息的标签信息和所述标签表达式为对应的新增用户配置相应的权限。
12、根据权利要求9所述的终端，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
接收到所述第三方平台发送的权限申请信息，所述权限申请信息包括目标用户信息和目标权限信息；
根据所述目标权限信息为所述目标用户信息配置相应的权限。
13、根据权利要求12所述的终端，其中，所述根据所述目标权限信息为所述目标用户信息配置相应的权限之后，还包括：
向所述第三方平台发起标签构建询问；
当接收到所述第三方平台反馈的构建标签指令时，根据所述目标用户信息中的目标标签信息生成目标标签表达式，且为所述目标标签表达式配置所述目标权限信息；
将所述权限配置信息更新后同步至所述第三方平台的权限管理系统。
14、根据权利要求9所述的终端，其中，所述获取第三方平台提供的用户信息之前，还包括：
接收到所述第三方平台发起的登录信息后，识别所述登录信息中的当前系统ID；
判断是否存在与所述当前系统ID匹配的目标系统ID；
若存在，则关联所述第三方平台的权限管理系统，并允许所述第三方平台调用接口以进行数据传输。
15、一种存储介质，其中，存储有能够实现多平台权限统一管理方法的程序文件，所述程序文件被处理器执行时实现以下步骤：
获取第三方平台提供的用户信息，所述用户信息包括标签信息，所述标签信息在建立所述用户信息时设定；
接收所述第三方平台反馈的至少一个标签表达式，以及为所述标签表达式配置的权限；
查询每一个所述标签表达式对应的目标用户群体后，为所述目标用户群体配置相应的权限，得到权限配置信息；
将所述权限配置信息同步至所述第三方平台。
16、根据权利要求15所述的存储介质，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
检测到标签信息发生变更时，基于变更后的标签信息和所述标签表达式调整与所述标签信息对应的用户的权限。
17、根据权利要求15所述的存储介质，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
关联所述第三方平台的审批系统；
检测到所述审批系统审批通过新增的用户信息时，基于所述新增的用户信息的标签信息和所述标签表达式为对应的新增用户配置相应的权限。
18、根据权利要求15所述的存储介质，其中，所述将所述权限配置信息同步至所述第三方平台之后，还包括：
接收到所述第三方平台发送的权限申请信息，所述权限申请信息包括目标用户信息和目标权限信息；
根据所述目标权限信息为所述目标用户信息配置相应的权限。
19、根据权利要求18所述的存储介质，其中，所述根据所述目标权限信息为所述目标用户信息配置相应的权限之后，还包括：
向所述第三方平台发起标签构建询问；
当接收到所述第三方平台反馈的构建标签指令时，根据所述目标用户信息中的目标标签信息生成目标标签表达式，且为所述目标标签表达式配置所述目标权限信息；
将所述权限配置信息更新后同步至所述第三方平台的权限管理系统。
20、根据权利要求15所述的存储介质，其中，所述获取第三方平台提供的用户信息之前，还包括：
接收到所述第三方平台发起的登录信息后，识别所述登录信息中的当前系统ID；
判断是否存在与所述当前系统ID匹配的目标系统ID；
若存在，则关联所述第三方平台的权限管理系统，并允许所述第三方平台调用接口以进行数据传输。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010784276.9A CN111914296A (zh) | 2020-08-06 | 2020-08-06 | 多平台权限统一管理方法、装置、终端及存储介质 |
| CN202010784276.9 | 2020-08-06 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2021139319A1 true WO2021139319A1 (zh) | 2021-07-15 |
Family
ID=73287929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2020/123194 WO2021139319A1 (zh) | 2020-08-06 | 2020-10-23 | 多平台权限统一管理方法、装置、终端及存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111914296A (zh) |
| WO (1) | WO2021139319A1 (zh) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113392712A (zh) * | 2021-05-19 | 2021-09-14 | 河南观潮智能科技有限公司 | 基于社交关系识别的智慧社区管理方法、装置、电子设备 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101441688A (zh) * | 2007-11-20 | 2009-05-27 | 阿里巴巴集团控股有限公司 | 一种用户权限分配方法和一种用户权限控制方法 |
| CN102088351A (zh) * | 2009-12-08 | 2011-06-08 | 长春吉大正元信息技术股份有限公司 | 授权管理系统及其实现方法 |
| US20130136263A1 (en) * | 2011-11-29 | 2013-05-30 | American Megatrends, Inc. | System and method for registering a personal computing device to a service processor |
| CN103853970A (zh) * | 2014-03-27 | 2014-06-11 | 浪潮软件集团有限公司 | 一种将多个web应用系统的操作权限集成的方法 |
| CN104243453A (zh) * | 2014-08-26 | 2014-12-24 | 中国科学院信息工程研究所 | 基于属性和角色的访问控制方法及系统 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109388921A (zh) * | 2017-08-10 | 2019-02-26 | 顺丰科技有限公司 | 一种统一用户权限管理平台及运行方法 |
| CN109740333B (zh) * | 2018-12-28 | 2023-07-18 | 上汽通用五菱汽车股份有限公司 | 集成系统和子系统的权限管理方法、服务器及存储介质 |
| CN110866243B (zh) * | 2019-10-25 | 2022-11-22 | 北京达佳互联信息技术有限公司 | 登录权限校验方法、装置、服务器及存储介质 |
-
2020
- 2020-08-06 CN CN202010784276.9A patent/CN111914296A/zh active Pending
- 2020-10-23 WO PCT/CN2020/123194 patent/WO2021139319A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101441688A (zh) * | 2007-11-20 | 2009-05-27 | 阿里巴巴集团控股有限公司 | 一种用户权限分配方法和一种用户权限控制方法 |
| CN102088351A (zh) * | 2009-12-08 | 2011-06-08 | 长春吉大正元信息技术股份有限公司 | 授权管理系统及其实现方法 |
| US20130136263A1 (en) * | 2011-11-29 | 2013-05-30 | American Megatrends, Inc. | System and method for registering a personal computing device to a service processor |
| CN103853970A (zh) * | 2014-03-27 | 2014-06-11 | 浪潮软件集团有限公司 | 一种将多个web应用系统的操作权限集成的方法 |
| CN104243453A (zh) * | 2014-08-26 | 2014-12-24 | 中国科学院信息工程研究所 | 基于属性和角色的访问控制方法及系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111914296A (zh) | 2020-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11812282B2 (en) | Collaborative computing and electronic records | |
| US20200327145A1 (en) | Cooperative naming for configuration items in a distributed configuration management database environment | |
| US9886563B2 (en) | Personalized online content access experiences using inferred user intent to configure online session attributes | |
| EP3734932B1 (en) | Implicitly linking access policies using group names | |
| US10325076B2 (en) | Personalized online content access experiences using online session attributes | |
| CN103475577B (zh) | 一种获得特征信息的方法、装置及网络设备 | |
| CN107580083A (zh) | 一种容器ip地址分配的方法和系统 | |
| CN104508678A (zh) | 商业数据系统中针对承租人的安全和数据隔离 | |
| CN102984194A (zh) | 虚拟应用程序分布机架的配置文件的同步 | |
| SG186137A1 (en) | Online service access controls using scale out directory features | |
| JP2000235513A (ja) | 複数データベースを同期させる方法及び装置 | |
| CN107920138A (zh) | 一种用户统一标识生成方法、装置及系统 | |
| WO2022095366A1 (zh) | 基于Redis的数据读取方法、装置、设备及可读存储介质 | |
| CN110928681A (zh) | 数据的处理方法和装置、存储介质及电子装置 | |
| WO2021139319A1 (zh) | 多平台权限统一管理方法、装置、终端及存储介质 | |
| CN102521755A (zh) | 一种信息管理系统及信息管理方法 | |
| WO2021051569A1 (zh) | 一种数据隔离方法、装置、计算机设备及存储介质 | |
| CN112862544A (zh) | 对象信息的获取方法、装置以及存储介质 | |
| KR100467580B1 (ko) | Ｓｔａｒ 형 네트워크 상에서의 그룹관리방법 및 장치 | |
| CN113312669B (zh) | 密码同步方法、设备及存储介质 | |
| CN107145606A (zh) | 一种数据管理方法及装置 | |
| CN103475741A (zh) | 数据同步系统和数据同步方法 | |
| US11200319B2 (en) | Cloud enabling of legacy trusted networking devices for zero touch provisioning and enterprise as a service | |
| US10778524B2 (en) | Method and system of in home wi-fi access point replication | |
| CN109587038A (zh) | 消息推送方法及装置 |
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: 20912834 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 15/05/2023) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 20912834 Country of ref document: EP Kind code of ref document: A1 |