A method for implementing aspera account management
By deploying an LDAP server and an Aspera server in the Aspera account management module, combined with scripts and a database, the synchronization and management of Aspera account information were achieved, solving the problems of high difficulty in account management and high repetitiveness of operations, and improving management efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-29
- Publication Date
- 2026-03-27
AI Technical Summary
In existing technologies, Aspera account management is difficult and involves highly repetitive operations, making it impossible to achieve effective operations within the Aspera account management module.
The Aspera account management module deploys an LDAP server and an Aspera server, manages account information through add and delete scripts, and integrates a MySQL database for information synchronization and storage, providing an intuitive user interface.
It simplifies the Aspera account management process, reduces management difficulty, improves account management efficiency, and reduces repetitive operations.
Smart Images
Figure CN115883189B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of Aspera management, and particularly relates to a method for realizing Aspera account management. BACKGROUND
[0002] Aspera software can move data of any size across any distance, and is a breakthrough transmission protocol. In order to use the Aspera transmission service, a user needs to create a corresponding storage account. Therefore, in a use scenario with a large number of users, a large amount of storage account data will be generated. In the prior art, the user identity authentication of Aspera is realized based on LDAP (Lightweight Directory Access Protocol). However, LDAP is usually used in the scene of unified authentication service, and needs to be maintained through an LDAP related command. Therefore, the corresponding operation cannot be realized in the Aspera account management module, and there are problems such as great difficulty in Aspera account management, high operation repeatability and the like.
[0003] Therefore, the prior art has defects and needs to be improved. SUMMARY
[0004] The present application aims at overcoming the defects of the prior art, and provides a method for realizing Aspera account management, which solves the problems of great difficulty in Aspera account management, high operation repeatability and the like in the prior art.
[0005] The technical scheme of the present application is as follows: a method for realizing Aspera account management, comprising the following steps:
[0006] S1: deploying an LDAP server for an Aspera account management module.
[0007] The LDAP server is used for storing Aspera account information of all Aspera users.
[0008] S2: deploying a plurality of Aspera servers for the Aspera account management module.
[0009] The Aspera servers are used for providing transmission services for Aspera users.
[0010] S3: deploying an adding script and a deleting script on the Aspera servers.
[0011] The adding script is used for adding Aspera account information of Aspera users in the Aspera account management module, and the deleting script is used for deleting Aspera account information of Aspera users in the Aspera account management module.
[0012] S4: The Aspera account management module acquires Aspera account information of all Aspera users stored on the LDAP server, performs an adding operation or a deleting operation of the Aspera account information on an operation interface of the Aspera account management module, and saves the updated Aspera account information and text information corresponding to the performed operation to the Aspera account management module after the operation is completed.
[0013] Further, the Aspera account information includes a username, a user password, a user storage path, a platform where the user is located, user attributes, and a user type.
[0014] Further, the operation step of performing the adding operation of the Aspera account information on the operation interface of the Aspera account management module includes:
[0015] 101: Acquire operation information of an Aspera user.
[0016] 102: Verify whether the corresponding Aspera server and LDAP server exist.
[0017] 103: If the Aspera server and the LDAP server exist, determine whether an adding operation of Aspera account information is to be performed, and if yes, the Aspera account management module connects the Aspera server, executes an adding script, and performs the adding operation of the Aspera account information.
[0018] Further, the operation step of performing the deleting operation of the Aspera account information on the operation interface of the Aspera account management module includes:
[0019] 201: Verify whether the Aspera server and the LDAP server corresponding to an Aspera user exist.
[0020] 202: If the Aspera server and the LDAP server exist, query whether Aspera account information of the Aspera user is stored in the Aspera account management module.
[0021] 203: If the result of step 202 is yes, the Aspera account management module connects the Aspera server, executes a deleting script, performs a deleting operation of the Aspera account information, and deletes text information corresponding to the performed operation.
[0022] Further, the Aspera account management module is provided with a MySQL database.
[0023] Further, the adding script and the deleting script are both shell scripts.
[0024] With the above scheme, the application provides a method for realizing Aspera account management, which has the following beneficial effects: Aspera account information of Aspera users can be synchronized to an Aspera account management module, and a communication connection is established between an Aspera server and the Aspera account management module, so that Aspera users can add and delete their Aspera account information in the Aspera account management module through the Aspera server, and back-end operation and maintenance personnel can realize unified management of Aspera user accounts in the background of the Aspera account management module, thereby simplifying the management process, reducing the management difficulty, and improving the account management efficiency. BRIEF DESCRIPTION OF DRAWINGS
[0025] Figure 1 is a flow chart of the application;
[0026] Figure 2 is a flow chart of the application adding a script runtime;
[0027] Figure 3 is a flow chart of the application deleting a script runtime. DETAILED DESCRIPTION
[0028] The application will be described in detail below in combination with the drawings and specific embodiments.
[0029] Please refer to Figure 1 The application provides a method for realizing Aspera account management, which comprises the following steps:
[0030] S1: deploying an LDAP server for an Aspera account management module. Specifically, the LDAP server is used to store Aspera account information of all Aspera users, and in this embodiment, the Aspera account information comprises a username, a user password, a user storage path, a platform where the user is located, user attributes, and a user type. It should be noted that the LDAP server is a unified authentication entry for Aspera users, and it is deployed by point, so for the same Aspera account management module, the LDAP server is unique. In the application, the deployment of the LDAP server is implemented by using a free and open source implementation "OpenLDAP", and the detailed steps can refer to the official document of OpenLDAP.
[0031] S2: Deploy several Aspera service ends to the Aspera account management module. Specifically, the Aspera service ends are used to provide transmission services for Aspera users; for the Aspera account management module, one LDAP service end corresponds to multiple Aspera service ends, and different platforms (platforms where Aspera users are located) correspond to different Aspera service ends, so that the deployment amount of the Aspera service ends deployed by the platform can be adjusted according to the actual transmission requirements of Aspera users in the business scenario.
[0032] S3: Deploy an adding script and a deleting script on the Aspera service end. Both the adding script and the deleting script are shell scripts.
[0033] Specifically, the adding script is used to perform an adding operation of Aspera account information of an Aspera user in the Aspera account management module, and the deleting script is used to perform a deleting operation of Aspera account information of an Aspera user in the Aspera account management module. The parameters required in the adding script and the deleting script are transmitted when the back end of the Aspera account management module remotely calls the script; specifically, the adding operation of Aspera account information of an Aspera user by the adding script mainly includes adding operations of a user name, a user password, a user storage path, a platform where the user is located, and a user type; and the deleting operation of Aspera account information of an Aspera user by the deleting script mainly includes deleting operations of a user name, a platform where the user is located, and a user type.
[0034] S4: The Aspera account management module acquires Aspera account information of all Aspera users stored on the LDAP service end and stores the Aspera account information in a MySQL database in the Aspera account management module, performs an adding operation or a deleting operation of Aspera account information on an operation interface of the Aspera account management module, and saves updated Aspera account information and text information corresponding to the performed operation to the Aspera account management module after the operation is completed. Each time a related operation is performed, the performed operation will correspondingly generate a text information used to record operation steps, and the text information will be saved synchronously. It should be noted that before the related operation is performed on the operation interface, the Aspera account management module needs to provide an account operation interface directly facing operation and maintenance personnel, and a front-end personnel can perform interface design and other operations according to actual requirements of the operator to ensure that the basic adding operation or deleting operation of Aspera account information can be met.
[0035] The method for realizing Aspera account management in the application can synchronize Aspera account information of Aspera users to an Aspera account management module, and establish a communication connection through an Aspera server and the Aspera account management module, so that the Aspera users can add and delete Aspera account information in the Aspera account management module through the Aspera server, and the back-end operation and maintenance personnel can realize unified management of Aspera accounts in the background of the Aspera account management module, simplify the management process, reduce the management difficulty, and improve the account management efficiency. In addition, in the prior art, the creation of an Aspera account is completed by interacting with an LDAP server through an LDAP command, and the corresponding command or script needs to be familiar with. In the application, Aspera account information can be directly configured through an operation interface, and the script execution process is performed by the back-end, so that the account data management can be focused on, and the repeated command operation is reduced.
[0036] Please refer to Figure 2 Specifically, in the embodiment, the operation steps of performing the addition operation of Aspera account information on the operation interface of the Aspera account management module include:
[0037] 101: Obtain operation information of Aspera users.
[0038] 102: Verify whether the corresponding Aspera server and LDAP server exist.
[0039] 103: If the Aspera account information addition operation is to be performed, the Aspera account management module connects the Aspera server, executes an addition script, and performs the addition operation of Aspera account information. After the operation is completed, the MySQL database of the Aspera account management module stores the updated Aspera account information and the text information corresponding to the operation. If the Aspera account information addition operation is not to be performed, the MySQL database of the Aspera account management module directly stores the text information corresponding to the operation.
[0040] Please refer to Figure 3 Specifically, in the embodiment, the operation steps of performing the deletion operation of Aspera account information on the operation interface of the Aspera account management module include:
[0041] 201: Verify whether the Aspera server and the LDAP server corresponding to the Aspera user exist. If not, directly delete the text information corresponding to the operation currently performed, and end the operation process.
[0042] 202: If yes, query whether the Aspera account information of the Aspera user is stored in the Aspera account management module. If no, it means that the Aspera account information of the Aspera user is not currently stored, which may be a new user. At this time, the text information corresponding to the operation performed after entering the operation interface can be directly deleted, and the operation process is ended.
[0043] 203: If the result of step 202 is yes, the Aspera account management module connects the Aspera server, executes the deletion script, and performs the deletion operation of the Aspera account information. The Aspera account management module deletes the text information corresponding to the operation performed.
[0044] In summary, the present application provides a method for managing Aspera accounts, which has the following advantages: the Aspera account information of the Aspera user can be synchronized to the Aspera account management module, and a communication connection can be established between the Aspera server and the Aspera account management module. As a result, the Aspera user can perform the addition operation and the deletion operation of the Aspera account information in the Aspera account management module through the Aspera server. The back-end maintenance personnel can realize the unified management of the Aspera user's account in the background of the Aspera account management module, which simplifies the management process, reduces the management difficulty, and improves the account management efficiency.
[0045] The above is only a preferred embodiment of the present application and is not intended to limit the present application. Any modification, equivalent replacement and improvement within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims
1. A method for implementing Aspera account management, the method comprising: The method comprises the following steps: S1: deploying an LDAP server for an Aspera account management module; The LDAP server is used to store Aspera account information of all Aspera users; S2: deploying a plurality of Aspera servers for the Aspera account management module; The Aspera servers are used to provide transmission services for Aspera users; S3: deploying an adding script and a deleting script on the Aspera servers; The adding script is used to perform an adding operation of Aspera account information of Aspera users in the Aspera account management module, and the deleting script is used to perform a deleting operation of Aspera account information of Aspera users in the Aspera account management module; S4: the Aspera account management module acquires all Aspera account information of Aspera users stored on the LDAP server, performs an adding operation or a deleting operation of Aspera account information on an operation interface of the Aspera account management module, and saves updated Aspera account information and text information corresponding to the performed operation into the Aspera account management module after the operation is completed; An operation step of performing an adding operation of Aspera account information on the operation interface of the Aspera account management module comprises: 101: acquiring operation information of an Aspera user; 102: verifying whether corresponding Aspera servers and LDAP servers exist; 103: if the Aspera servers and the LDAP servers exist, determining whether an adding operation of Aspera account information is to be performed, and if yes, the Aspera account management module connects the Aspera servers, executes the adding script, and performs the adding operation of Aspera account information; An operation step of performing a deleting operation of Aspera account information on the operation interface of the Aspera account management module comprises: 201: verifying whether Aspera servers and LDAP servers corresponding to an Aspera user exist; 202: if the Aspera servers and the LDAP servers exist, querying whether Aspera account information of the Aspera user is stored in the Aspera account management module; 203: if the result of step 202 is yes, the Aspera account management module connects the Aspera servers, executes the deleting script, and performs the deleting operation of Aspera account information, and the Aspera account management module deletes text information corresponding to the performed operation.
2. The method for implementing Aspera account management according to claim 1, wherein, The Aspera account information comprises a username, a user password, a user storage path, a platform where the user is located, user attributes, and a user type.
3. The method for implementing Aspera account management according to claim 1, wherein, The Aspera account management module is provided with a MySQL database.
4. The method for implementing Aspera account management according to claim 1, wherein, The adding script and the deleting script are both shell scripts.
Citation Information
Patent Citations
User and equipment account management system capable of supporting multi-type and multi-point login
CN103581178A