User management method based on data interface platform

Abstract

The invention relates to a user management method based on a data interface platform, and relates to the technical field of log management, a user registers an account through the data interface platform, completes identity authentication and obtains a login credential, the user carries out login operation by inputting the login credential, and the data interface platform carries out user authentication and authorization. The authentication passes the input of a user name and a password and verifies whether the user name is matched with the password, the authorization is set according to the role and authority of the user, after the user authentication and authorization are completed, an administrator checks a registered new user, and after the check is passed, the user can normally use a data interface. The method comprises the following steps: checking a user, monitoring behaviors of the user and the use condition of a data interface, tracking the behaviors of the user and the use condition of the data interface by using a log recording and monitoring technology for the checked user, interacting with a background through the data interface, and performing management operation on the user by an administrator.

Description

Technical Field

[0001] The present invention relates to the technical field of log management. More specifically, the present invention relates to a user management method based on a data interface platform. Background Art

[0002] With the continuous development and popularization of information technology, more and more enterprises and organizations have begun to use data interface platforms to process and manage data. However, how to effectively manage the users of these data interface platforms has become an important issue.

[0003] Traditional user management methods usually adopt the way of manually adding, modifying and deleting users. This method has many drawbacks, such as being error-prone, inefficient, and having poor security. Therefore, it is of great significance to study an automated user management method based on a data interface platform. Summary of the Invention

[0004] In view of the technical problems existing in the prior art, the present invention provides a user management method based on a data interface platform, which interacts with the background through a data interface to perform management operations on users, so as to solve the problems raised in the above background art.

[0005] The technical solution of the present invention to solve the above technical problems is as follows: A user management method based on a data interface platform specifically includes the following steps: Step 101: The user registers an account through the data interface platform and completes identity authentication to obtain a login credential; Step 102: The user performs a login operation by inputting the login credential, and the data interface platform authenticates and authorizes the user; Step 103: After the user authentication and authorization are completed, the administrator reviews the newly registered users and monitors the user behavior and the usage of the data interface; Step 104: Through interaction with the background through the data interface, the administrator performs management operations on the users.

[0006] In a preferred embodiment, in step 101, when the user registers an account through the data interface platform and completes identity authentication to obtain a login credential, including a username and a password, the specific steps are as follows: Step A1: The user accesses the registration page: The user accesses the registration page on the data interface platform and fills in the necessary registration information on the registration page, including the username, email address, and mobile phone number; Step A2: Verify the information: The data interface platform verifies the information provided by the user by verifying whether the email address is valid and whether the mobile phone number is correct, preventing malicious users from spamming and maliciously registering a large number of accounts, and maintaining the security and order of the platform; Step A3: Set login credentials: The user sets login credentials, requires the user to use a strong password, provides password strength tips, sets the minimum password length to 8 characters, and sets the password to include uppercase and lowercase letters, numbers, and special characters to increase the complexity of the password; Step A4: Complete registration: After the user submits the registration information, perform data verification and processing, create a user account, and store the registration information in the database.

[0007] In a preferred embodiment, in step 102, after the user logs in, perform user authentication and authorization. The authentication is through entering the username and password to verify whether the username and password match, and use multi-factor authentication to verify according to the dynamic verification code generated by the mobile application to enhance the security of user identity verification. The authorization is set according to the user's role and permissions to ensure that the user can only access the data interfaces within their authorized scope. The specific steps are as follows: Step B1: Authentication: After the user submits the login credentials username and password, the data interface platform verifies whether the credentials provided by the user are correct. Verify the correctness of the password by hashing the password and comparing it with the hashed password stored in the database. Let the input password be P, the hashed password stored in the database be H, and the generated authentication token be T. The specific steps include: Step 201: Hash the password. The specific calculation formula is as follows:

[0008] Where, The hash value obtained after the hash operation, P represents the input password, represents the hash function;

[0009] Step 202: Compare the hashed password: Compare the hash value obtained after the hash operation with the hashed password stored in the database. When the hash value is the same as the result of the hashed password stored in the database, it indicates successful verification. The specific calculation formula is as follows:

[0010] Where, The hash value obtained after the hash operation, H represents the hashed password stored in the database;

[0011] Step 203: Generate an authentication token: And use multi-factor authentication to require the user to perform a second verification, the dynamic verification code generated by the mobile application, to enhance the security of user identity verification. When the credential verification is successful, the data interface platform generates an authentication token and returns it to the user. The specific calculation formula is as follows:

[0012] Among them, T represents the generated authentication token, represents the function for generating the token;

[0013] Step B2, Authorization: Set according to the user's role and permissions to ensure that the user can only access the data interfaces within their authorized scope. The specific steps include: Step 301, After obtaining the authentication token, the user uses the token for subsequent requests; Step 302, When the user requests a resource that requires authorization, the data interface platform verifies the user's authentication token and checks whether the user has the permission to access the resource; Step 303, When the user has sufficient permissions, the data interface platform returns the data of the requested resource; when the user does not have sufficient permissions, the data interface platform rejects the user's request.

[0014] In a preferred embodiment, in step 103, after the user registers, an audit process is set up to audit new users. After passing the audit, the user can use the data interface normally, and the user's behavior and the usage of the data interface are monitored to detect anomalies and handle them in a timely manner. The specific steps are as follows: Step C1, Registration audit process: After the user registers, the user's registration information is saved to a pending audit list in the database. The administrator logs in to the background, views the pending audit list, and audits each registered user; Step C2, Auditing users: After the administrator logs in to the background, views the pending audit list, and audits users one by one. By verifying the information submitted by the user, verifying the user's identity, and checking whether the user meets the registration conditions, according to the audit results, the administrator marks different users as passed and not passed; Step C3, Monitoring user behavior and data interface usage: For users who have passed the audit, their behavior and data interface usage are tracked through logging and monitoring techniques, including recording the user's login activities, the API paths and parameters of the requests, access frequency, and data transfer volume. Let u represent a user who has passed the audit, and t represent the current time, represents the behavior of user u logging in to the background at time t, represents the behavior of user u requesting a data interface with API path p and parameters v at time t. The specific steps include:

[0015] Step 401, Recording the user's login activities: Calculate the number of user logins. The specific calculation formula is as follows:

[0016] Among them, Denotes the total number of logins of user u, where u represents a user who has passed the review, and t represents the current time. Denotes the login behavior of user u at time t.

[0017] Step 402, API path and parameters of the request: Calculate the number of API requests. The specific calculation formula is as follows:

[0018] Among them, Denotes the total number of times the data interface with API path p is requested. Denotes that when user u requests the data interface with API path p and parameter v at time t, the value of this expression is 1.

[0019] Step 403, User access frequency: Calculate the average access frequency of the user. The specific calculation formula is as follows:

[0020] Among them, Denotes the average access frequency of user u. Denotes the total number of logins of user u. Is a time period, u represents a user who has passed the review, and t represents the current time.

[0021] Step 404, API data transfer volume: Calculate the API data transfer volume. The specific calculation formula is as follows:

[0022] Among them, Denotes the total data volume transferred by the data interface with API path p. Denotes the behavior of user u requesting the data interface with API path p and parameter v at time t.

[0023] Step C4, Anomaly detection and handling: After monitoring user behavior and data interface usage, set thresholds for abnormal behavior. When the request frequency and data transfer volume of a certain user exceed the thresholds, it indicates that the user has abnormal behavior, and an alarm is automatically sent to the administrator. The administrator conducts security management by suspending the user's access rights and contacting the user to verify the situation.

[0024] In a preferred embodiment, in step 104, interact with the background through a data interface to provide a user management interface, and the administrator can perform management operations on users, including adding new users, deleting users, and modifying user information. The specific steps are as follows: Step D1. Add a new user: Interact with the background through the data interface. On the user management interface, provide a form for adding a new user. After the administrator fills in the user information, the front-end sends the user information to the background data interface in the form of a POST request. After receiving the request, the background interface saves the information of the new user into the database; Step D2. Delete a user: Interact with the background through the data interface. On the user management interface, display a form for deleting user information. After the administrator deletes the user information in the form, the front-end sends a DELETE request to the background data interface. The request carries the unique identifier user ID of the user to be deleted. The background interface will delete the corresponding user information from the database according to the user identifier in the request; Step D3. Modify user information: Interact with the background through the data interface. On the user management interface, display a form for modifying user information. After the administrator modifies the user information in the form, the front-end sends a PUT request to the background data interface. The request carries the unique identifier of the user to be modified and the updated information. The background interface will update the information of the corresponding user in the database according to the user identifier in the request; Step D4. Refresh the user list: After adding, deleting, and modifying user information, send a request to the background to obtain the latest user list data and update the user list on the interface.

[0025] The beneficial effects of the present invention are as follows: The user registers an account and completes identity authentication through the data interface platform to obtain a login credential. The user logs in by entering the login credential. The data interface platform performs user authentication and authorization. The authentication is to verify whether the user name and password match by entering the user name and password. The authorization is set according to the user's role and permissions. After the user authentication and authorization are completed, the administrator reviews the newly registered users. After passing the review, the user can use the data interface normally, and monitor the user's behavior and the usage of the data interface. For the users who have passed the review, use logging and monitoring technologies to track their behavior and the usage of the data interface, so as to detect anomalies in time and handle them. Interact with the background through the data interface, and the administrator performs management operations on the users, improving management efficiency and security. Description of the Drawings

[0026] Figure 1 It is the system flow chart of the present invention. Detailed Embodiments

[0027] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope of protection of the present application.

[0028] In the description of the present application, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include one or more of the described features. In the description of the present application, "a plurality" means two or more, unless otherwise specifically defined.

[0029] In the description of the present application, the term "for example" is used to mean "used as an example, illustration, or explanation". Any embodiment described as "for example" in the present application is not necessarily construed as being more preferred or having more advantages than other embodiments. In order for any person skilled in the art to implement and use the present invention, the following description is given. In the following description, details are set forth for the purpose of explanation. It should be understood that those of ordinary skill in the art can recognize that the present invention can be implemented without using these specific details. In other instances, well-known structures and processes are not elaborated in detail to avoid unnecessary details from obscuring the description of the present invention. Therefore, the present invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope that conforms to the principles and features disclosed in the present application.

[0030] Embodiment 1 This embodiment provides a Figure 1 user management method based on a data interface platform as shown, specifically including the following steps: Step 101: The user registers an account through the data interface platform and completes identity authentication to obtain a login credential. Further, the user registers an account through the data interface platform and completes identity authentication to obtain a login credential, including a username and a password. The specific steps are as follows: Step A1: The user accesses the registration page: The user accesses the registration page on the data interface platform and fills in the necessary registration information on the registration page, including the username, email address, and mobile phone number. Step A2: Verify the information: The data interface platform verifies the information provided by the user by verifying whether the email address is valid and whether the mobile phone number is correct, preventing malicious users from spamming and maliciously registering a large number of accounts, and maintaining the security and order of the platform. Step A3. Set login credentials: The user sets login credentials, requires the user to use a strong password, provides password strength tips, sets the minimum password length to 8 characters, and sets the password to include uppercase and lowercase letters, numbers, and special characters to increase the complexity of the password; Step A4. Complete registration: After the user submits the registration information, data verification and processing are performed, a user account is created, and the registration information is stored in the database.

[0031] Step 102. The user logs in by entering the login credentials, and the data interface platform authenticates and authorizes the user; Further, after the user logs in, user authentication and authorization are performed. The authentication is through entering the username and password to verify whether the username and password match, and multi-factor authentication is used to verify according to the dynamic verification code generated by the mobile application to enhance the security of user identity verification. The authorization is set according to the user's role and permissions to ensure that the user can only access the data interfaces within their authorized scope. The specific steps are as follows: Step B1. Authentication: After the user submits the login credentials username and password, the data interface platform verifies whether the credentials provided by the user are correct. The correctness of the password is verified by hashing the password and comparing it with the hashed password stored in the database. Let the input password be P, the hashed password stored in the database be H, and the generated authentication token be T. The specific steps include: Step 201. Hash the password. The specific calculation formula is as follows:

[0032] where, is the hash value obtained after the hash operation, P represents the input password, represents the hash function;

[0033] Step 202. Compare the hashed password: Compare the hash value obtained after the hash operation with the hashed password stored in the database. When the hash value is the same as the result of the hashed password stored in the database, it indicates successful verification. The specific calculation formula is as follows:

[0034] where, is the hash value obtained after the hash operation, H represents the hashed password stored in the database;

[0035] Step 203. Generate an authentication token: And use multi-factor authentication, require the user to perform a second verification, the dynamic verification code generated by the mobile application, to enhance the security of user identity verification. When the credential verification is successful, the data interface platform generates an authentication token and returns it to the user. The specific calculation formula is as follows:

[0036] Among them, T represents the generated authentication token, indicating the function for generating the token;

[0037] Step B2, Authorization: Set according to the user's role and permissions to ensure that the user can only access the data interfaces within their authorized scope. The specific steps include: Step 301, After the user obtains the authentication token, use this token for subsequent requests; Step 302, When the user requests a resource that requires authorization, the data interface platform verifies the user's authentication token and checks whether the user has the permission to access this resource; Step 303, When the user has sufficient permissions, the data interface platform will return the data of the requested resource; when the user does not have sufficient permissions, the data interface platform will reject the user's request.

[0038] Step 103, After the user authentication and authorization are completed, the administrator reviews the newly registered users and monitors the user's behavior and the usage of the data interfaces; Furthermore, after the user registers, set up an audit process to review the new users. After the review is passed, the user can use the data interfaces normally, and monitor the user's behavior and the usage of the data interfaces to detect anomalies in a timely manner and handle them. The specific steps are as follows: Step C1, Registration audit process: After the user registers, save the user's registration information to a pending review list in the database. The administrator logs in to the background, views the pending review list, and reviews each registered user; Step C2, Review users: After the administrator logs in to the background, views the pending review list, and reviews users one by one. By verifying the information submitted by the user, verifying the user's identity, and checking whether the user meets the registration conditions, according to the review results, the administrator marks different users as passed and not passed; Step C3, Monitor user behavior and data interface usage: For users who have passed the review, use logging and monitoring technologies to track their behavior and the usage of the data interfaces, including recording the user's login activities, the API paths and parameters of the requests, the access frequency, and the data transfer volume. Let u represent a user who has passed the review, and t represent the current time, indicating the behavior of user u logging in to the background at time t, indicating the behavior of user u requesting a data interface with API path p and parameters v at time t. The specific steps include:

[0039] Step 401, Record the user's login activities: Calculate the number of user logins. The specific calculation formula is as follows:

[0040] Among them, represents the total number of times user u has logged in. u represents a user who has passed the review, and t represents the current time. represents the login behavior of user u at time t;

[0041] Step 402, API path and parameters of the request: Calculate the number of API requests. The specific calculation formula is as follows:

[0042] Among them, represents the total number of times the data interface with API path p has been requested. means that when user u requests the data interface with API path p and parameter v at time t, the value of this expression is 1;

[0043] Step 403, User access frequency: Calculate the average access frequency of the user. The specific calculation formula is as follows:

[0044] Among them, represents the average access frequency of user u. represents the total number of times user u has logged in. is a time period. u represents a user who has passed the review, and t represents the current time;

[0045] Step 404, API data transfer volume: Calculate the API data transfer volume. The specific calculation formula is as follows:

[0046] Among them, represents the total data volume transferred by the data interface with API path p. represents the behavior of user u requesting the data interface with API path p and parameter v at time t;

[0047] Step C4, Abnormality detection and handling: After monitoring user behavior and data interface usage, set thresholds for abnormal behaviors. When the request frequency and data transfer volume of a certain user exceed the thresholds, it indicates that the user has abnormal behaviors, and an alarm is automatically sent to the administrator. The administrator conducts security management by suspending the user's access rights and contacting the user to verify the situation.

[0048] Step 104, Interact with the background through the data interface, and the administrator conducts management operations on the user; Furthermore, it interacts with the background through a data interface and provides a user management interface where an administrator can perform management operations on users, including adding new users, deleting users, and modifying user information. The specific steps are as follows: Step D1, adding a new user: It interacts with the background through a data interface. On the user management interface, a form is provided for adding a new user. After the administrator fills in the user information, the front end sends the user information to the background data interface in the form of a POST request. After receiving the request, the background interface saves the information of the new user into the database; Step D2, deleting a user: It interacts with the background through a data interface. On the user management interface, a form for deleting user information is displayed. After the administrator deletes the user information in the form, the front end sends a DELETE request to the background data interface, and the unique identifier of the user to be deleted, the user ID, is carried in the request. The background interface will delete the corresponding user information from the database according to the user identifier in the request; Step D3, modifying user information: It interacts with the background through a data interface. On the user management interface, a form for modifying user information is displayed. After the administrator modifies the user information in the form, the front end sends a PUT request to the background data interface, and the unique identifier of the user to be modified and the updated information are carried in the request. The background interface will update the information of the corresponding user in the database according to the user identifier in the request; Step D4, refreshing the user list: After adding, deleting, and modifying user information, a request is sent to the background to obtain the latest user list data and update the user list on the interface.

[0049] It should be noted that in the above embodiments, the descriptions of each embodiment have their own emphases. For parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0050] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0051] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present invention. It should be understood that each flow and / or block in the flowchart and / or block diagram, and the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate a means for implementing the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0052] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction means that implements the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0053] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0054] Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications that fall within the scope of the present invention.

[0055] Obviously, those skilled in the art can make various changes and variations to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

1. A user management method based on a data interface platform, characterized in that, Specifically, it includes the following steps: Step 101: The user registers an account through the data interface platform, completes identity authentication, and obtains a login credential; Step 102: The user performs a login operation by inputting the login credential, and the data interface platform conducts user authentication and authorization; Step 103: After the user authentication and authorization are completed, the administrator reviews the newly registered users and monitors the users' behaviors and the usage of the data interface; Step 104: Through interaction with the background via the data interface, the administrator performs management operations on the users.

2. The user management method based on a data interface platform according to claim 1, wherein: In step 101, when the user registers an account through the data interface platform, completes identity authentication, and obtains a login credential, which includes a username and a password, the specific steps are as follows: Step A1: Access the registration page: The user accesses the registration page on the data interface platform and fills in the registration information on the registration page, including the username, email address, and mobile phone number; Step A2: Verify the information: The data interface platform verifies the information provided by the user by verifying whether the email address is valid and whether the mobile phone number is correct; Step A3: Set the login credential: Set the login credential for the user, require the user to use a strong password, provide a password strength hint, set the minimum password length to 8 characters, and set the password to include uppercase and lowercase letters, numbers, and special characters to increase the password complexity; Step A4: Complete the registration: After the user submits the registration information, perform data verification and processing, create a user account, and store the registration information in the database.

3. A user management method based on a data interface platform according to claim 1, characterized in that, In step 102, after the user logs in, user authentication and authorization are performed. The authorization is set according to the user's role and permissions. The authentication is to verify whether the username and password match by inputting the username and password. The specific steps are as follows: Step B1: Authentication: After the user submits the login credential username and password, the data interface platform verifies whether the credential provided by the user is correct. Verify the correctness of the password by hashing and encrypting the password and comparing it with the hashed password stored in the database. Let the input password be P, the hashed password stored in the database be H, and the generated authentication token be T. The specific steps include: Step 201: Hash and encrypt the password. The specific calculation formula is as follows: Among them, the hash value obtained after the hash operation, where P represents the input password, represents the hash function; Step 202: Compare the hashed passwords: Compare the hashed value obtained after the hashing operation with the hashed password stored in the database. When the hashed value is the same as the result of the hashed password stored in the database, it indicates successful verification. The specific calculation formula is as follows: Among them, the hash value obtained after performing a hash operation, where H represents the hashed password stored in the database; Step 203: Generate an authentication token: When the credential verification is successful, the data interface platform generates an authentication token and returns it to the user. The specific calculation formula is as follows: Where T represents the generated authentication token, represents the function for generating the token.

4. The user management method based on a data interface platform according to claim 3, wherein The steps for setting the authorization according to the user's role and permissions include: Step 301: After the user obtains the authentication token, use this token for subsequent requests; Step 302: When the user requests a resource that requires authorization, the data interface platform verifies the user's authentication token and checks whether the user has the permission to access this resource; Step 303: When the user has the permission, the data interface platform will return the data of the requested resource; when the user does not have the permission, the data interface platform will reject the user's request.

5. A user management method based on a data interface platform according to claim 1, characterized in that, In step 103, after a user registers, an approval process is set up to approve new users. After successful approval, the user can use the data interface normally, and the behavior of the user and the usage of the data interface are monitored. The specific steps of the approval process are as follows: Step C1, Registration Approval Process: After a user registers, the user's registration information is saved to a pending approval list in the database. The administrator logs in to the backend, views the pending approval list, and approves each registered user; Step C2, Approve User: After the administrator logs in to the backend, views the pending approval list, and approves users one by one. By verifying the information submitted by the user, verifying the user's identity, and checking whether the user meets the registration conditions, the administrator marks different users as approved and unapproved according to the approval results. Step 401, Record User Login Activity: Calculate the number of user logins. The specific calculation formula is as follows: Among them, represents the total number of times user u has logged in. u represents a user who has passed the review, and t represents the current time. represents the login behavior of user u at time t; Step 402, Requested API Path and Parameters: Calculate the number of API requests. The specific calculation formula is as follows: Among them, represents the total number of times the data interface with the API path p is requested, means that when the user u requests the data interface with the API path p and the parameter v at time t, the value of this expression is 1; Step 403, User Access Frequency: Calculate the average access frequency of the user. The specific calculation formula is as follows: Among them, represents the average access frequency of user u, represents the total number of logins of user u, is a time period, u represents a user who has passed the review, and t represents the current time; Step 404, API Data Transfer Volume: Calculate the API data transfer volume. The specific calculation formula is as follows: Among them, represents the total amount of data transmitted by the data interface with the API path p, represents the behavior of user u requesting the data interface with the API path p and parameter v at time t. Step D1, Add New User: Interact with the backend through the data interface. On the user management interface, provide a form for adding new users. After the administrator fills in the user information, the front-end sends the user information to the backend data interface in the form of a POST request. After receiving the request, the backend interface saves the information of the new user to the database; Step D2, Delete User: Interact with the backend through the data interface. On the user management interface, display a form for deleting user information. After the administrator deletes the user information in the form, the front-end sends a DELETE request to the backend data interface. The request carries the unique identifier user ID of the user to be deleted. The backend interface deletes the corresponding user information from the database according to the user identifier in the request; Step D3, Modify User Information: Interact with the backend through the data interface. On the user management interface, display a form for modifying user information. After the administrator modifies the user information in the form, the front-end sends a PUT request to the backend data interface. The request carries the unique identifier of the user to be modified and the updated information. The backend interface updates the information of the corresponding user in the database according to the user identifier in the request; Step D4, Refresh User List: After adding, deleting, and modifying user information, send a request to the backend to obtain the latest user list data and update the user list on the interface.

Images