Authority management method and device of software platform, equipment and medium
By unifying the management of account permission data across multiple software platforms, generating permission selection lists, and automatically creating new accounts, the problem of low efficiency in manually creating permissions in existing technologies is solved, thus achieving efficient permission management.
Patent Information
- Application Number
- CN202511567672.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-30
- Publication Date
- 2026-01-23
AI Technical Summary
In enterprise software development, when using multiple software platforms, existing technologies require manually creating and assigning accounts and permissions for multiple software platforms, resulting in low efficiency.
This paper provides a method for managing permissions on a software platform. By acquiring account permission data from multiple software platforms, a permission selection list is generated, and a permission approval request is sent to the permission management terminal. After approval, a new account is automatically created and permissions are assigned. The method supports custom and template permission applications and automatically cleans up expired permissions.
It enables unified management of permissions across multiple software platforms, improves the efficiency of permission requests, reduces manual operations, and enhances the automation of permission management.
Smart Images
Figure CN121389078A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of computer software, in particular to a permission management method and device of a software platform, equipment and medium. BACKGROUND
[0002] In the process of enterprise software development, different software platforms such as GitLab code hosting platform, cicd tool platform, artifact repository platform, project management platform and image warehouse platform are usually used, and there are mixed scenarios of open source version, enterprise version and self-research version of the software platforms. Before using these software platforms, the user needs to apply for an account, and different permissions can be set for each account to obtain resources allowed by the permissions.
[0003] In the prior art, when the user needs an account of a software platform, the user can apply to the administrator of the software platform, and the administrator will create an account for the user and set the corresponding permissions.
[0004] However, when the user needs accounts of multiple software platforms, the user needs to apply to the administrators of the software platforms one by one, and the administrators need to manually create accounts and allocate permissions one by one, which is low in efficiency. SUMMARY
[0005] In view of the above problems, the present application is proposed to provide a permission management method, device, equipment and medium of a software platform to solve the above problems, which can uniformly manage the permissions of all software platforms, apply for the permissions of multiple software platforms at the same time, and uniformly allocate accounts and permissions without manual creation one by one, thereby improving the efficiency of permission management.
[0006] In a first aspect, the present application provides a permission management method of a software platform, which comprises: obtaining account permission data of multiple software platforms, the account permission data comprising resource object information, permission information and business information; generating a permission selection list according to all account permission data; if a permission application instruction triggered by the permission selection list is received, sending a permission approval request to a permission management end, the permission application instruction comprising permission application information of multiple target software platforms; if an approval instruction sent by the permission management end is received, generating a new account of the target software platform, and allocating target permissions in the permission application information to the new account.
[0007] Optionally, the approval instruction comprises the validity period of each target permission in the permission application information, and the method further comprises: If the effective duration of the target permission is greater than the corresponding valid period, the target permission is cleaned up.
[0008] Optionally, the approval instruction includes the valid period of each target permission in the permission application information, the account permission data includes existing account information, the existing account information includes the valid period of the existing permission under the existing account, and the method further includes: According to the valid period of the effective permission, the expiration time of the effective permission is determined, and the effective permission includes the existing permission and the target permission. The expiration time is sorted in chronological order. The effective permission corresponding to the expiration time between the first position and the set position in the sorting is determined as the permission to be cleaned up. If the current time is the expiration time of the permission to be cleaned up, the permission to be cleaned up is cleaned up, and the permission to be cleaned up is re-determined after all the permissions to be cleaned up are cleaned up.
[0009] Optionally, the permission application instruction includes a custom permission application instruction, the permission selection list includes a custom permission selection list, the custom permission application instruction is triggered through the custom permission selection list, and the custom permission selection list includes all resource objects and permissions of the plurality of software platforms.
[0010] Optionally, the custom permission selection list includes the plurality of software platform selection lists, the software platform selection list includes a plurality of resource group selection lists, the resource group selection list includes a plurality of resource object selection lists, and the resource object selection list includes a plurality of permissions.
[0011] Optionally, the permission application instruction includes a template permission application instruction, the permission selection list includes a template permission selection list, the template permission application instruction is triggered through the template permission selection list, the template permission selection list includes a plurality of permission templates, and each permission template includes all permissions required by one business in the business information.
[0012] Optionally, the new account of the plurality of target software platforms is provided with the same primary key, and the primary key includes a mobile phone number, a job number or an email address.
[0013] In a second aspect, the application provides a permission management device of a software platform, the device comprising: The acquisition module is configured to acquire account permission data of a plurality of software platforms, and the account permission data includes resource object information, permission information and business information. The first generation module is configured to generate a permission selection list according to all account permission data. The sending module is configured to send a permission approval request to the permission management end if a permission application instruction triggered by the permission selection list is received, wherein the permission application instruction comprises permission application information of the target software platforms; The second generating module is configured to generate a new account of the target software platform and assign a target permission in the permission application information to the new account if an approval instruction sent by the permission management end is received.
[0014] In a third aspect, the present application provides an electronic device, comprising a memory and a processor, which are communicatively connected with each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the method of the first aspect.
[0015] In a fourth aspect, the present application provides a computer readable storage medium, which stores computer instructions for causing the computer to perform the method of the first aspect.
[0016] The technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: The permission management method, device, equipment and medium for software platforms provided in the embodiments of the present application can first acquire account permission data of multiple software platforms, aggregate the account permission data of each software platform, and the account permission data comprises resource object information, permission information and business information; generate a permission selection list according to all the account permission data, i.e. select the permissions of all the software platforms under the same selection list; if a permission application instruction triggered by the permission selection list is received, send a permission approval request to the permission management end, the permission application instruction comprises permission application information of multiple target software platforms, and the different software platforms are simultaneously applied in batches, which needs to be audited by the permission management end; if an approval instruction sent by the permission management end is received, generate a new account of the target software platform and assign a target permission in the permission application information to the new account, and after the audit is passed, generate the new account and the corresponding target permission in batches. The method can simultaneously apply for the permissions of multiple software platforms, and improves the application efficiency of the permissions.
[0017] The above description is only a summary of the technical solutions of the present application. In order to more clearly understand the technical means of the present application, the following detailed embodiments of the present application can be implemented according to the content of the description, and in order to make the above and other purposes, characteristics and advantages of the present application more obvious and easy to understand, the following detailed embodiments of the present application are described. BRIEF DESCRIPTION OF DRAWINGS
[0018] Various other advantages and benefits will become apparent to those of ordinary skill in the art, upon reading the following detailed description of the preferred embodiments with reference made to the accompanying drawings. The drawings are for purposes of illustration only and are not intended to limit the scope of the present application. The same reference numbers in different drawings identify the same components. In the drawings: Figure 1 is a flowchart of a permission management method of a software platform provided by an embodiment of the present application; Figure 2 is a schematic diagram of a custom permission selection list provided by an embodiment of the present application; Figure 3 is a schematic diagram of a template permission selection list provided by an embodiment of the present application; Figure 4 is a structural block diagram of a permission management device of a software platform provided by an embodiment of the present application. DETAILED DESCRIPTION
[0019] In order to make the purposes, technical solutions and advantages of the present application clearer, the embodiments of the present application will be described in further detail below with reference to the drawings, and it should be understood that the embodiments of the present application and the specific features in the embodiments are detailed descriptions of the technical solutions of the present application, and are not limitations of the technical solutions of the present application. In the case of no conflict, the technical features in the embodiments of the present application and the embodiments can be combined with each other.
[0020] Figure 1 is a flowchart of a permission management method of a software platform provided by an embodiment of the present application, as shown in Figure 1 the method comprises: Step S110, obtaining account permission data of a plurality of software platforms, the account permission data comprising resource object information, permission information and business information.
[0021] In the embodiments of the present application, in the process of developing enterprise software, a developer may need to use multiple software platforms at the same time, for example, a GitLab code hosting platform, a cicd tool platform, a artifact repository platform, a project management platform, an image warehouse platform, etc. Therefore, the account and permission of multiple software platforms are needed. In this case, the permission management system is connected with each software platform through a permission interface, so that the account and permission of multiple software platforms can be applied through the permission management system.
[0022] Specifically, the account permission data of multiple software platforms of an enterprise is first obtained through the permission management system and stored in a relational database. For example, the resource groups of the GitLab code hosting platform, the resource objects under the resource groups, and the developer, maintainer and owner permissions of the resource objects, as well as the business information, are obtained.
[0023] The resource object information includes resource groups and resource objects possessed by the software platform, the permission information includes permissions possessed by the software platform, and the business information can include research and development projects and research and development teams.
[0024] In step S120, a permission selection list is generated according to all the account permission data.
[0025] The account permission data further includes existing account information.
[0026] In the embodiments of the present application, all the account permission data can be processed first, for example, the account permission data of different software platforms is processed to the same dimension. Then, the processed account permission data is grouped, for example, grouping can be performed according to software platforms, one software platform is one group, and the data under each group is classified according to the existing account information, the resource object information and the business information, and each category is stored in a table to obtain a user information table, a resource object permission table and a business information table. Finally, based on the grouped and processed account permission data, a permission selection list is generated, and the permission selection list can be displayed through an interface.
[0027] Next, the permission applicant can select the permissions he needs in the permission selection list on the interface to apply, and multiple permissions in the list can be selected at a time, and the multiple permissions can be different permissions of different resource objects of different software platforms.
[0028] In step S130, if a permission application instruction triggered by the permission selection list is received, a permission approval request is sent to the permission management end, and the permission application instruction includes permission application information of multiple target software platforms.
[0029] The target software platform is a software platform selected by the permission applicant to apply for permissions among multiple software platforms.
[0030] In the embodiments of the present application, after the permission applicant selects the permissions he needs through the permission selection list, he can click the “Confirm” button to trigger the permission application instruction. After the permission application instruction is triggered, a permission approval request is sent to the permission management end to make the permission administrator know that someone has applied for permissions. If the permission application of different software platforms is approved by different permission administrators, the permission approval request is sent to different permission administrators in the permission management end. The permission administrator can check the permission application information in the permission approval request through the permission management end. If the permission administrator agrees with the application, he can click the “Approve” button on the permission management end to trigger an approval instruction; if the permission administrator does not agree with the application, he can click the “Reject” button on the permission management end to trigger a rejection instruction. The permission management system can asynchronously generate the permission approval request to improve the processing efficiency when the permission application request is too much.
[0031] In the embodiment of the present application, the permission application information includes an application target resource object and a target permission of the application target resource object. For example, the permission application instruction triggered by the permission application personnel includes a developer permission of a first object under a first resource of a GitLab code hosting platform and a read-only permission of a second object of a second resource of a product library platform.
[0032] The permission management end can be a Feishu software or other office software used by an enterprise. For example, the permission approval request is pushed to the permission manager through a Feishu card, and the permission manager can directly click the “approve” or “reject” button on the card.
[0033] In step S140, if the approval instruction sent by the permission management end is received, a new account of the target software platform is generated, and the target permission in the permission application information is assigned to the new account.
[0034] In the embodiment of the present application, if the permission management system receives the approval instruction sent by the permission management end, it means that the permission application of the permission application personnel is approved, and the permission management system automatically generates a new account of the software platform that the permission application personnel wants to open, that is, a new account of the target software platform, and assigns the target permission applied by the permission application personnel to the new account. The permission manager does not need to create an account and assign a permission for each software platform, but creates and assigns them uniformly through the permission management system, thereby improving the efficiency of permission management.
[0035] The generated new account and corresponding target permission automatically call the corresponding target software platform interface, and send the new account and corresponding target permission to the corresponding target software platform. After receiving the new account and corresponding target permission, the target software platform automatically creates the new account and automatically assigns the corresponding target permission to the new account. The account information of the target software platform is synchronized with the permission management system, so that the permission application personnel can normally use the resource object of the target software platform without manual intervention.
[0036] Optionally, the new accounts of the plurality of target software platforms have the same primary key, and the primary key includes a mobile phone number, a work number or an email address.
[0037] In the embodiment of the present application, each software platform has a unique primary key, which facilitates the permission management system to automatically identify and associate the user primary key of the corresponding software platform.
[0038] It should be noted that if the permission application personnel already has an account of the target software platform, which is referred to as an existing account, the newly generated new account will be the same as the existing account, that is, the same primary key, such as the work number of the permission application personnel.
[0039] In the embodiment of the present application, after the new account and the corresponding target permission are assigned, a notification is sent to the permission applicant to inform the permission applicant that the permission application is approved, and the approval state in the Feishu card is updated correspondingly.
[0040] Optionally, the approval instruction includes the validity period of each target permission in the permission application information, and the method further includes: If the effective duration of the target permission is longer than the corresponding validity period, the target permission is cleaned up.
[0041] In the embodiment of the present application, when the permission manager selects “Approve” on the permission management end, the permission manager can also set the validity period for each target permission. After receiving the approval instruction, the permission management system sets the corresponding validity period for the target permission. When the effective duration of the target permission is longer than the corresponding validity period, the target permission is cleaned up, so that the target permission cannot be used after the validity period expires, and there is no need to manually clean up the unused permissions one by one. Instead, the permission management system automatically cleans up, improving the efficiency of permission management.
[0042] Optionally, the approval instruction includes the validity period of each target permission in the permission application information, and the existing account information includes the validity period of the existing permission under the existing account, and the method further includes: Step 1: Determine the expiration time of the effective permission according to the validity period of the effective permission, and the effective permission includes the existing permission and the target permission.
[0043] In the embodiment of the present application, the validity period of the newly assigned target permission and the previously assigned existing permission is monitored at the same time, and the existing permission and the target permission are used as effective permissions at the same time. Based on the effective time and the validity period of the effective permission, the expiration time of the effective permission, i.e. the invalidation time, is calculated.
[0044] Step 2: Sort the expiration times in chronological order.
[0045] In the embodiment of the present application, in order to better manage the validity period of all permissions, the expiration times can be sorted in chronological order.
[0046] Step 3: Determine the effective permission corresponding to the expiration time between the first position and the set position in the sorting as the permission to be cleaned up.
[0047] In the embodiment of the present application, one or more effective permissions that expire first are used as the permission to be cleaned up, and these permissions to be cleaned up are monitored, avoiding too many permissions being monitored at the same time, which causes pressure on the system. The set position can be 10 or 20, and can be set according to actual conditions.
[0048] Step 4: If the current time is the expiration time of the permissions to be cleared, then clear the permissions to be cleared, and re-determine the permissions to be cleared after all the permissions to be cleared have been cleared.
[0049] In this embodiment, if the current time is the expiration time of a permission to be cleared, it means that the permission has expired and needs to be cleared so that it can no longer be used. After all permissions to be cleared have expired, new permissions to be cleared are determined again according to steps one through three. At the same time, when a new target permission application is approved, the permissions to be cleared can also be determined once according to steps one through three to update the permissions to be cleared.
[0050] After clearing permissions, an expiration notification can be sent to the permission management system to remind permission administrators and users that their permissions have expired. The permission management system also supports functions such as querying permission application records.
[0051] Optionally, the permission request instruction includes a custom permission request instruction, and the permission selection list includes a custom permission selection list. The custom permission request instruction is triggered by the custom permission selection list, which includes all resource objects and permissions of multiple software platforms.
[0052] Figure 2 This is a schematic diagram of a custom permission selection list provided in an embodiment of this application, such as... Figure 2 As shown, the custom permission selection list can be displayed on the page. Permission applicants can select resources, objects, and permissions for various software platforms under the custom permission list. For example, they can select permission 1 for resource object 1 in resource group 1 of software platform 1, and permission 1 for resource object 1 in resource group 1 of software platform 2.
[0053] Optionally, the custom permission selection list includes multiple software platform selection lists, each containing multiple software platforms. After selecting a software platform, there is a second-level list: the resource group selection list, which contains multiple resource groups. After selecting a resource group, there is a third-level list: the resource object selection list, which contains multiple resource objects. After selecting a resource object, there is a fourth-level list: the permission selection list, which contains multiple permissions.
[0054] like Figure 2 As shown, the custom permission selection list includes Software Platform 1 and Software Platform 2. Under each Software Platform, there is a Resource Group Selection List, which contains multiple resource groups such as Resource Group 1. Under each resource group, there is a Resource Object Selection List, which contains multiple resource objects such as Resource Object 1. Under each resource object selection list, there is a Permission Selection List, which contains multiple permissions such as Permission 1.
[0055] Optionally, the permission application instruction comprises a template permission application instruction, the permission selection list comprises a template permission selection list, the template permission application instruction is triggered by the template permission selection list, the template permission selection list comprises a plurality of permission templates, and each permission template comprises all permissions required by one business in the business information.
[0056] The business information comprises a research and development project or a research and development team, and the plurality of permission templates comprise a permission template of a research and development project 1 development business, a research and development project 1 architecture business, and a research and development project 1 product business. The research and development project 1 development business requires which software platform permissions, and the permission module of the research and development project 1 development business corresponds to which software platform permissions.
[0057] In the embodiment of the present application, the permission selection page of the permission management system further comprises a template permission selection list. After selecting a permission template under the template permission selection list, the resource groups, resource objects, and permissions of the target software platform corresponding to the permission template are automatically displayed, and the permission application personnel do not need to enter different software platform permission selection lists to select resource groups, resource objects, and permissions one by one.
[0058] Figure 3 is a schematic diagram of a template permission selection list provided by the embodiment of the present application. As shown in Figure 3 , the template permission selection list comprises a plurality of permission templates, such as template 1, template 2, and template 3. After selecting one of the permission templates, the software platform, resource groups, resource objects, and permissions corresponding to the permission template are displayed. The permission application personnel can select a permission template according to their own post or the current research and development project, so as to one-key generate the required permissions, greatly improving the efficiency of permission application. For example, the developer of the xxx project development can select template 1 (xxx project development) to apply for permissions in batches. Figure 3
[0059] The permission manager can configure different dimension permission templates according to business information such as a research and development project or a research and development team, and each permission template can be combined and constructed according to required permissions of the research and development project, a research and development module under the research and development project, or a research and development team. For example, during the development process of the A project, the developer needs the developer permission of the project a of the software platform 1 (such as a project management platform), and also needs the permissions of group1 and warehouse report1 of the code warehouse platform, and the development process also needs the permissions of artifact group1 and groupxx, and the several software platforms and corresponding required permissions can be combined into a permission template. Meanwhile, the administrator can also batch configure the permissions of each software platform for specific users to obtain specific permission templates. The permission module can be combined and constructed according to actual conditions, and no specific limitation is made here.
[0060] Based on the same application concept, the embodiment of the present application also provides a permission management device of a software platform, Figure 4 which is a structural block diagram of the permission management device of the software platform provided by the embodiment of the present application, as Figure 4 shown, the device 400 includes an acquisition module 401, a first generation module 402, a sending module 403, and a second generation module 404.
[0061] The acquisition module 401 is used to acquire account permission data of a plurality of software platforms, and the account permission data includes resource object information, permission information, and business information. The first generation module 402 is used to generate a permission selection list according to all account permission data. The sending module 403 is used to send a permission approval request to a permission management end if a permission application instruction triggered through the permission selection list is received, and the permission application instruction includes permission application information of a plurality of target software platforms. The second generation module 404 is used to generate a new account of a target software platform and allocate target permissions in the permission application information to the new account if an approval instruction sent by the permission management end is received.
[0062] Optionally, the approval instruction includes a validity period of each target permission in the permission application information, and the device further includes: A first cleaning module is used to clean the target permission if the validity time length of the target permission is greater than the corresponding validity period.
[0063] Optionally, the approval instruction includes a validity period of each target permission in the permission application information, and the account permission data includes existing account information, and the existing account information includes a validity period of an existing permission under an existing account, and the device further includes a second cleaning module configured to: determine an expiration time of the effective permission according to the validity period of the effective permission, and the effective permission includes the existing permission and the target permission. sort the expiration time in chronological order; determine the effective authority corresponding to the expiration time between the first position in the sorting and the set position as the to-be-cleaned authority; If the current time is the expiration time of the to-be-cleaned authority, the to-be-cleaned authority is cleaned, and the to-be-cleaned authority is re-determined after all to-be-cleaned authorities are cleaned.
[0064] Optionally, the authority application instruction includes a custom authority application instruction, the authority selection list includes a custom authority selection list, the custom authority application instruction is triggered through the custom authority selection list, and the custom authority selection list includes all resource objects and authorities of a plurality of software platforms.
[0065] Optionally, the custom authority selection list includes a plurality of software platform selection lists, the software platform selection list includes a plurality of resource group selection lists, the resource group selection list includes a plurality of resource object selection lists, and the resource object selection list includes a plurality of authorities.
[0066] Optionally, the authority application instruction includes a template authority application instruction, the authority selection list includes a template authority selection list, the template authority application instruction is triggered through the template authority selection list, the template authority selection list includes a plurality of authority templates, and each authority template includes all authorities required by one business in the business information.
[0067] Optionally, the new account of the plurality of target software platforms is provided with the same primary key, and the primary key includes a mobile phone number, a job number or an email address.
[0068] It can be understood that the apparatus provided in the above embodiments is only used as an example for the division of the above functional modules, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules to complete all or part of the above described functions.
[0069] Embodiments of the present application also provide an electronic device, which can include a processor and a memory, wherein the processor and the memory can be connected to each other in communication through a bus or other means.
[0070] The processor can be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured as one or more integrated circuits to implement the embodiments of the present application, or can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. chips, or a combination of the above chips.
[0071] The memory can include a mass storage for data or instructions. By way of example and not limitation, the memory can include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. The memory can include removable or non-removable (or fixed) media, where appropriate. The memory can be internal or external to the electronic device, where appropriate. In certain embodiments, the memory can be non-volatile solid-state memory.
[0072] In one example, the memory can be read only memory (ROM). In one example, the ROM can be mask programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory, or a combination of two or more of these.
[0073] The processor implements the permission management method of any one of the software platforms in the above embodiments by reading and executing the computer program instructions stored in the memory.
[0074] In one example, the electronic device can further include a communication interface and a bus. The processor, the memory, and the communication interface are connected through the bus and complete communication with each other. The communication interface is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiments of the present application. Where appropriate, the bus can include one or more buses.
[0075] In addition, in combination with the permission management method of the software platform in the above embodiments, a computer readable storage medium can be provided to implement the embodiments. The computer readable storage medium stores computer program instructions; the computer program instructions are executed by a processor to implement any one of the permission management methods of the software platform in the above embodiments.
[0076] Those skilled in the art can understand that all or part of the processes in the above embodiments can be completed by a computer program instructing related hardware, and the program can be stored in a computer readable storage medium. When the program is executed, the processes of the above embodiments can be included. The storage medium can be a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid state drive (SSD), etc. The storage medium can also include a combination of the above types of memories.
[0077] The technical solutions in the above embodiments have at least the following technical effects or advantages: The software platform permission management method, device, equipment and medium provided by the embodiments can first acquire account permission data of multiple software platforms, aggregate the account permission data of each software platform, and the account permission data includes resource object information, permission information and business information. According to all account permission data, a permission selection list is generated, that is, the permissions of all software platforms are selected under the same selection list. If a permission application instruction triggered by the permission selection list is received, a permission approval request is sent to the permission management end, the permission application instruction includes permission application information of multiple target software platforms, and after batch application to different software platforms, the permission management end needs to be audited. If an approval instruction sent by the permission management end is received, a new account of the target software platform is generated, and the target permission in the permission application information is allocated to the new account. After the audit is passed, the new account and the corresponding target permission are generated in batches. The method can apply for the permissions of multiple software platforms at the same time, and improves the application efficiency of the permissions.
[0078] In the specification provided herein, a large number of specific details are described. However, it can be understood that the embodiments of the present application can be practiced without these specific details. In some examples, well-known methods, structures and techniques are not shown in detail in order not to obscure the understanding of the present specification.
[0079] Similarly, it should be understood that, in order to simplify this disclosure and aid in understanding one or more of the various aspects of the invention, in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof. However, this method of disclosure should not be construed as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as reflected in the following claims, inventive aspects lie in fewer than all features of a single foregoing disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into this detailed description, wherein each claim itself is a separate embodiment of the invention.
[0080] It should be noted that the above embodiments are illustrative of the invention and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention can be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.
Claims
1. A method for managing rights of a software platform, characterized by, The method comprises: obtaining account permission data of a plurality of software platforms, the account permission data comprising resource object information, permission information and business information; generating a permission selection list according to all account permission data; if a permission application instruction triggered by the permission selection list is received, sending a permission approval request to a permission management end, the permission application instruction comprising permission application information of a plurality of target software platforms; if an approval instruction sent by the permission management end is received, generating a new account of the target software platform and assigning target permissions in the permission application information to the new account.
2. The rights management method of a software platform according to claim 1, characterized in that, The approval instruction comprises a validity period of each target permission in the permission application information, and the method further comprises: if the validity period of the target permission is greater than the corresponding validity period, the target permission is cleaned up.
3. The rights management method of a software platform according to claim 1, characterized in that, The approval instruction comprises a validity period of each target permission in the permission application information, and the account permission data comprises existing account information, the existing account information comprising a validity period of existing permissions under an existing account, and the method further comprises: determining an expiration time of the effective permission according to the validity period of the effective permission, the effective permission comprising the existing permission and the target permission; sorting the expiration time in chronological order; determining the effective permission corresponding to the expiration time between the first position and the set position in the sorting as a permission to be cleaned up; if the current time is the expiration time of the permission to be cleaned up, the permission to be cleaned up is cleaned up, and the permission to be cleaned up is re-determined after all the permissions to be cleaned up are cleaned up.
4. The rights management method of a software platform according to claim 1, characterized in that, The permission application instruction comprises a custom permission application instruction, the permission selection list comprises a custom permission selection list, the custom permission application instruction is triggered by the custom permission selection list, and the custom permission selection list comprises all resource objects and permissions of the plurality of software platforms.
5. The rights management method of a software platform according to claim 4, characterized in that, The custom permission selection list comprises a plurality of software platform selection lists, the software platform selection list comprises a plurality of resource group selection lists, the resource group selection list comprises a plurality of resource object selection lists, and the resource object selection list comprises a plurality of permissions.
6. The rights management method of a software platform according to claim 1, characterized by, The permission application instruction comprises a template permission application instruction, the permission selection list comprises a template permission selection list, the template permission application instruction is triggered by the template permission selection list, the template permission selection list comprises a plurality of permission templates, and each permission template comprises all permissions required by one business in the business information.
7. The rights management method of a software platform according to claim 1, characterized by, The new account of the plurality of target software platforms is provided with the same primary key, and the primary key comprises a mobile phone number, a job number or an email address.
8. An apparatus for managing rights of a software platform, characterized by comprising: The device comprises: an acquisition module configured to acquire account permission data of a plurality of software platforms, the account permission data comprising resource object information, permission information and business information; a first generation module configured to generate a permission selection list according to all account permission data; The sending module is configured to send, if an authority application instruction triggered by the authority selection list is received, an authority approval request to an authority management end, and the authority application instruction comprises authority application information of a plurality of target software platforms; The second generating module is configured to generate a new account of the target software platform and assign a target authority in the authority application information to the new account if an approval instruction sent by the authority management end is received.
9. An electronic device, comprising: The computer readable storage medium stores computer instructions, and the computer instructions are used to make the computer execute the method in any one of claims 1-7. The computer readable storage medium stores computer instructions, and the computer instructions are used to make the computer execute the method in any one of claims 1-7.
10. A computer readable storage medium characterized by,