Accounting service provider login management method, device, equipment and medium

Abstract

The present invention relates to the technical field of information security and access control. Specifically, it relates to a method, device, equipment and medium for managing the avatar login of an accounting service provider, wherein the method comprises obtaining the identity information of the accounting service provider, verifying the identity information of the accounting service provider with a preset identity authentication rule, obtaining an identity authentication result, and if the identity authentication result is a verification pass, then generating the accounting service provider session information, and obtaining the cooperation verification result according to the accounting service provider session information, and if the cooperation verification result is a verification pass, then generating the avatar operation request information, and generating the avatar token according to the avatar operation request information, and the accounting service provider uses the avatar token to enter the management end of the target enterprise, and the management end verifies the validity of the avatar token, and if the avatar token is verified, then loading the enterprise management end interface that meets the authority of the accounting service provider. The present invention has the effect of improving the security of enterprise information.

Description

Technical Field

[0001] The present invention relates to the technical field of information security and access control, and in particular to a method, device, equipment and medium for managing avatar login of an accounting service provider. Background Art

[0002] With the rapid development of information technology, corporate financial management has become increasingly complex and specialized. More and more companies tend to entrust financial management tasks to professional bookkeeping service providers. This entrustment model not only improves the efficiency of corporate financial management, but also helps companies reduce operating costs, allowing them to focus more on the development of core businesses. However, when bookkeeping service providers perform financial operations, how to ensure the security of corporate information has become an urgent problem to be solved. Summary of the invention

[0003] In order to improve the security of enterprise information, the present application provides a method, device, equipment and medium for managing in-person login of an accounting service provider.

[0004] The above-mentioned invention objective of the present application is achieved through the following technical solutions:

[0005] A method for managing a proxy bookkeeping service provider's avatar login, the method comprising:

[0006] Obtain the identity information of the bookkeeping service provider;

[0007] Verifying the identity information of the bookkeeping service provider with a preset identity verification rule to obtain an identity verification result, and if the identity verification result is a passed verification, generating bookkeeping service provider session information;

[0008] Verify the cooperation relationship between the accounting service provider and the target enterprise according to the accounting service provider session information, and obtain a cooperation verification result. If the cooperation verification result is qualified, generate an attachment operation request information;

[0009] Generate an attachment token according to the attachment operation request information, return the attachment token to the client of the agency bookkeeping service provider, and the agency bookkeeping service provider uses the attachment token to enter the management end of the target enterprise;

[0010] The management end verifies the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the accounting service provider is loaded.

[0011] By adopting the above technical solution, first, by obtaining the identity information of the bookkeeping service provider and performing strict identity authentication, it is ensured that only legitimate service providers can perform subsequent operations. After the verification is passed, session information will be generated to further verify the effective cooperation relationship between the bookkeeping service provider and the target enterprise, ensuring that the bookkeeping service provider can only access the enterprise management end within the authorized scope. If the cooperation relationship verification is passed, the attached operation request information will be generated and the attached token will be returned. The bookkeeping service provider can use this token to enter the target enterprise management end for operation. The technical solution also verifies the validity of the attached token to ensure the operation authority of the bookkeeping service provider within the validity period. If the attached token verification fails, the attached operation will be terminated and the bookkeeping service provider will be triggered to resubmit the request to avoid unauthorized access. During the validity period of the attached token, if the bookkeeping service provider exits the management end or the target enterprise terminates the cooperation, the attached token will be revoked in time to prevent any potential abuse of authority.

[0012] In a preferred example, the present application may be further configured as follows: the identity information of the bookkeeping service provider is verified with a preset identity authentication rule to obtain an identity authentication result, and if the identity authentication result is a passed authentication, the bookkeeping service provider session information is generated, and further includes:

[0013] If the identity authentication result is a verification failure, rejecting the login request of the bookkeeping service provider and sending a verification failure message to the bookkeeping service provider;

[0014] Based on the verification failure information, the bookkeeping service provider is allowed to resubmit the identity information for re-verification. If the bookkeeping service provider fails in verification continuously within a preset number of verification attempts, the login authority of the bookkeeping service provider is temporarily restricted.

[0015] By adopting the above technical solution, when the identity authentication of the accounting service provider fails, the login request will be rejected, and the verification failure information will be sent to the service provider immediately to ensure that all login operations are promptly fed back and processed. To prevent malicious attacks or repeated attempts, the accounting service provider can resubmit identity information for verification after receiving the verification failure information, but if the verification fails continuously within the preset number of times, its login permission will be automatically restricted. This mechanism can effectively prevent illegal users from entering through brute force cracking and other methods, and ensure the security of operations. By setting a reasonable number of verification retries and temporary restrictions, it can not only meet the convenience of user operations, but also ensure security needs, and avoid affecting normal operations due to frequent incorrect input.

[0016] In a preferred example, the present application may be further configured as follows: the verification of the cooperative relationship between the bookkeeping service provider and the target enterprise includes:

[0017] Obtaining the cooperation agreement between the bookkeeping service provider and the target enterprise, verifying the validity of the cooperation agreement through a cooperation agreement database, and obtaining a validity verification result;

[0018] According to the validity verification result, it is determined whether the bookkeeping service provider has the authority to access the target enterprise management terminal. If the verification is successful, it is determined that there is a valid cooperative relationship between the bookkeeping service provider and the target enterprise.

[0019] By adopting the above technical solution, the validity of the cooperation agreement is verified to ensure that there is a legal and effective cooperation relationship between the accounting service provider and the target enterprise. If the verification is successful, it will be confirmed that the accounting service provider has the authority to access the target enterprise's management terminal, thereby avoiding the abuse of authority caused by invalid or illegal cooperation relationships. This solution not only ensures the security and compliance of the accounting service provider and the target enterprise, but also reduces access problems caused by inaccurate or expired agreement information. Through this verification mechanism, the accounting service provider can only obtain the necessary operating permissions on the premise of ensuring the effectiveness of the cooperation between the two parties. This approach ensures the transparency and security of financial information.

[0020] In a preferred example, the present application may be further configured as follows: judging whether the bookkeeping service provider has the authority to access the target enterprise management terminal according to the validity verification result, and if the verification is successful, determining that there is a valid cooperative relationship between the bookkeeping service provider and the target enterprise, further comprising:

[0021] If the verification fails, the access request of the bookkeeping service provider is rejected, and a cooperation relationship verification failure message is sent to the bookkeeping service provider;

[0022] According to the partnership verification failure information, resubmission verification request information is provided to the bookkeeping service provider.

[0023] By adopting the above technical solution, when the verification of the cooperative relationship between the bookkeeping service provider and the target enterprise fails, the access request of the bookkeeping service provider can be rejected in time, thereby preventing unauthorized operations and information leakage. If the verification fails, the bookkeeping service provider will receive information that the verification of the cooperative relationship has failed, and can resubmit the verification request based on the information. This process ensures that the bookkeeping service provider can only obtain access rights when the cooperative relationship between the two parties is legal and valid. It not only protects the financial data security of the enterprise, but also improves the transparency and compliance of operations. After the verification fails, the bookkeeping service provider can promptly know the problem and resubmit the verification, avoiding access loopholes or misoperation caused by unverified cooperative relationships.

[0024] In a preferred example, the present application may be further configured as follows: generating an attachment token according to the attachment operation request information includes:

[0025] According to the attachment operation request information, the identity information of the accounting service provider, the target enterprise identifier and the attachment request timestamp are obtained, and the identity information, the target enterprise identifier and the request timestamp are concatenated to form the original information of the attachment token;

[0026] The original information of the attached token is hashed to generate a unique attached token identifier, and the unique attached token identifier is bound to the authority information of the bookkeeping service provider and the token validity period to generate the attached token.

[0027] By adopting the above technical solution, when the accounting service provider initiates a possession operation request, the original information of the possession token can be generated by splicing the identity information, the target enterprise identifier and the timestamp of the possession request, and hashing is performed to generate a unique possession token identifier. The possession token identifier is bound to the authority information and token validity period of the accounting service provider, ensuring the uniqueness and validity of the possession token during verification. This solution effectively enhances the security and accuracy of the possession login process. The hashed possession token ensures that the identifier of the possession operation cannot be forged or tampered with, preventing identity impersonation and unauthorized access. In addition, by binding the possession token to the authority information and token validity period of the accounting service provider, the effective range and validity period of the token are further controlled, avoiding the abuse or misuse of expired tokens.

[0028] In a preferred example, the present application can be further configured as follows: the management end verifies the validity of the attached token, and if the attached token passes the verification, loads the enterprise management end interface that complies with the authority of the bookkeeping service provider, and also includes:

[0029] If the attachment token verification fails, the attachment operation is terminated and the attachment token verification failure information is sent to the accounting service provider;

[0030] According to the verification failure information of the attachment token, the accounting service provider is triggered to re-initiate the attachment request. If the accounting service provider fails to re-submit the attachment request within a specified time, the access rights of the accounting service provider are temporarily frozen.

[0031] By adopting the above technical solution, the security and compliance of the accounting service provider in the possession operation can be effectively improved. When the possession token verification fails, the possession operation is immediately terminated, and the verification failure information is sent to the accounting service provider, thereby avoiding unauthorized access and ensuring the security of the target enterprise data. This measure can ensure that the accounting service provider can only obtain access to the target enterprise management terminal if the verification is passed, preventing potential risks caused by unauthorized or erroneous operations. In addition, by triggering the accounting service provider to re-initiate the possession request and freezing its access rights if the request is not resubmitted within the specified time, this measure enhances the monitoring and control of improper behavior and avoids system abuse due to frequent erroneous requests.

[0032] In a preferred example, the present application can be further configured as follows: the accounting service provider login management method further includes:

[0033] Acquire the validity period information of the attached token, compare the validity period information with the current time information, and if the validity period information has been reached, the attached token is invalid;

[0034] Acquire the exit operation information of the bookkeeping service provider, and based on the exit operation information, if the bookkeeping service provider exits the target enterprise management terminal, the attached token is destroyed and becomes invalid;

[0035] The enterprise cooperation termination information is obtained. According to the enterprise cooperation termination information, if the target enterprise terminates the cooperation relationship with the bookkeeping service provider, the attached token is revoked and becomes invalid.

[0036] By adopting the above technical solution, when the validity period of the attached token is reached, it will automatically become invalid, preventing the expired token from being used further, thus avoiding potential security risks. It can ensure that the access rights of the accounting service provider are only valid within a reasonable time frame, thereby effectively limiting unnecessary access. At the same time, when the accounting service provider exits the target enterprise management end, the attached token will be immediately destroyed to ensure that any operations after the exit cannot continue, which enhances the control over sensitive operations. In addition, if the enterprise terminates its cooperation with the accounting service provider, the attached token will be revoked, fundamentally protecting the security of corporate information and preventing the risk of information leakage caused by continued access rights after the termination of the cooperation.

[0037] The second object of the invention is achieved by the following technical solutions:

[0038] A device for managing a person's login to an agency bookkeeping service provider, the device comprising:

[0039] An identity information acquisition module is used to obtain the identity information of the bookkeeping service provider;

[0040] An identity authentication and session generation module, used to verify the identity information of the bookkeeping service provider with a preset identity authentication rule to obtain an identity authentication result, and if the identity authentication result is a passed authentication, generate session information of the bookkeeping service provider;

[0041] A cooperation relationship verification module, used to verify the cooperation relationship between the agency accounting service provider and the target enterprise according to the agency accounting service provider session information, obtain a cooperation verification result, and generate an attachment operation request information if the cooperation verification result is qualified;

[0042] An attachment token generation module, used to generate an attachment token according to the attachment operation request information, and return the attachment token to the client of the agency bookkeeping service provider, and the agency bookkeeping service provider uses the attachment token to enter the management end of the target enterprise;

[0043] The module for verifying the validity of the attached token and loading the interface is used by the management end to verify the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the accounting service provider is loaded.

[0044] By adopting the above technical solution, first, by obtaining the identity information of the bookkeeping service provider and performing strict identity authentication, it is ensured that only legitimate service providers can perform subsequent operations. After the verification is passed, session information will be generated to further verify the effective cooperation relationship between the bookkeeping service provider and the target enterprise, ensuring that the bookkeeping service provider can only access the enterprise management end within the authorized scope. If the cooperation relationship verification is passed, the attached operation request information will be generated and the attached token will be returned. The bookkeeping service provider can use this token to enter the target enterprise management end for operation. The technical solution also verifies the validity of the attached token to ensure the operation authority of the bookkeeping service provider within the validity period. If the attached token verification fails, the attached operation will be terminated and the bookkeeping service provider will be triggered to resubmit the request to avoid unauthorized access. During the validity period of the attached token, if the bookkeeping service provider exits the management end or the target enterprise terminates the cooperation, the attached token will be revoked in time to prevent any potential abuse of authority.

[0045] The third objective of the present application is achieved through the following technical solutions:

[0046] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned method for managing the login of an agent bookkeeping service provider when executing the computer program.

[0047] The fourth objective of the present application is achieved through the following technical solutions:

[0048] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the above-mentioned method for managing the in-person login of an accounting service provider.

[0049] In summary, the present application includes at least one of the following beneficial technical effects:

[0050] 1. By obtaining the identity information of the accounting service provider and performing strict identity authentication, ensure that only legitimate service providers can perform subsequent operations. After the verification is passed, session information will be generated to further verify the effective cooperation relationship between the accounting service provider and the target enterprise, ensuring that the accounting service provider can only access the enterprise management end within the authorized scope. If the cooperation relationship verification is passed, the possession operation request information will be generated and the possession token will be returned. The accounting service provider can use this token to enter the target enterprise management end to perform operations. This technical solution also verifies the validity of the possession token to ensure the operating authority of the accounting service provider within the validity period. If the possession token verification fails, the possession operation will be terminated and the accounting service provider will be triggered to resubmit the request to avoid unauthorized access. During the validity period of the possession token, if the accounting service provider exits the management end or the target enterprise terminates the cooperation, the possession token will be revoked in time to prevent any potential abuse of authority;

[0051] 2. When the accounting service provider initiates a possession operation request, it can generate the original information of the possession token by splicing the identity information, the target enterprise identifier and the timestamp of the possession request, and perform hashing to generate a unique possession token identifier. The possession token identifier is bound to the authority information and token validity period of the accounting service provider, ensuring the uniqueness and validity of the possession token during verification. This solution effectively enhances the security and accuracy of the possession login process. The hashed possession token ensures that the identifier of the possession operation cannot be forged or tampered with, preventing identity impersonation and unauthorized access. In addition, by binding the possession token to the authority information and token validity period of the accounting service provider, the effective range and validity period of the token are further controlled, avoiding the abuse or misuse of expired tokens;

[0052] 3. It can effectively improve the security and compliance of accounting service providers in the possession operation. When the possession token verification fails, the possession operation is immediately terminated and the verification failure information is sent to the accounting service provider, thereby avoiding unauthorized access and ensuring the security of the target enterprise data. This can ensure that the accounting service provider can only obtain access to the target enterprise management terminal if the verification is passed, preventing potential risks caused by unauthorized or erroneous operations. In addition, by triggering the accounting service provider to re-initiate the possession request and freezing its access rights if the request is not resubmitted within the specified time, this measure enhances the monitoring and control of improper behavior and avoids system abuse due to frequent erroneous requests. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 This is a flow chart of a method for managing an account keeping service provider's avatar login in one embodiment of the present application;

[0054] Figure 2 This is a flowchart for implementing step S20 in the method for managing the in-person login of an accounting service provider in one embodiment of the present application;

[0055] Figure 3 This is a flowchart for implementing step S30 in the method for managing the in-person login of an accounting service provider in one embodiment of the present application;

[0056] Figure 4 This is a flowchart for implementing step S302 in the method for managing the in-person login of an accounting service provider in one embodiment of the present application;

[0057] Figure 5 This is a flowchart for implementing step S40 in the method for managing the in-person login of an accounting service provider in one embodiment of the present application;

[0058] Figure 6 This is a flowchart for implementing step S50 in the method for managing the in-person login of an accounting service provider in one embodiment of the present application;

[0059] Figure 7 This is a flowchart of the implementation after step S50 in the method for managing the in-person login of an accounting service provider in one embodiment of the present application;

[0060] Figure 8 This is a principle block diagram of a device for managing an in-person account keeping service provider login in one embodiment of the present application;

[0061] Fig. 9 It is a schematic diagram of a device in an embodiment of the present application. DETAILED DESCRIPTION

[0062] The present application is further described in detail below in conjunction with the accompanying drawings.

[0063] In one embodiment, if Figure 1 As shown, the present application discloses a method for managing the login of an accounting service provider, which specifically includes the following steps:

[0064] S10: Obtain the identity information of the bookkeeping service provider.

[0065] Specifically, when a bookkeeping service provider accesses the bookkeeping management terminal, it first authenticates its identity by entering its registered username and password. The system will encrypt the entered password (usually using a hash algorithm, such as SHA-256) and compare it with the encrypted password stored in the database. At this point, the system not only checks whether the username exists, but also verifies whether the password corresponding to the username is correct. If the verification is successful, the system will further verify whether the service provider has completed identity authentication (such as whether it has passed real-name authentication) and check whether the service provider is authorized to access the current platform. The system will also verify the account status of the service provider (whether it is frozen, expired, etc.) to ensure that subsequent operations can be performed normally. If the identity information is verified, the system will create session information for the service provider, including login identifier, login timestamp, and other security information to ensure the legitimacy and security of the login.

[0066] Furthermore, the system is used to provide an accounting service platform based on an avatar login mechanism, which aims to ensure that the accounting service provider can safely and compliantly access the enterprise management end and perform corresponding accounting operations in the process of providing services through effective authority management and identity authentication mechanisms. The system verifies the validity of the cooperation agreement with the target enterprise to ensure that the accounting service provider operates within the scope of legal cooperation, and monitors the management and verification of the avatar token throughout the process to ensure accurate control of the service provider's authority and avoid unauthorized operations. At the same time, the system also sets an expiration mechanism for the avatar token. Through multiple methods such as the token validity period, the accounting service provider's exit operation, and the company's termination of cooperation, it ensures that the accounting service provider's authority is revoked in a timely manner in various situations to protect the company's financial data security.

[0067] S20: Verify the identity information of the bookkeeping service provider with the preset identity authentication rules to obtain an identity authentication result. If the identity authentication result is that the authentication is passed, generate the bookkeeping service provider session information.

[0068] Specifically, the system performs multiple verifications based on the identity information of the bookkeeping service provider. First, the system will compare the ID number of the bookkeeping service provider with the platform database to ensure that the service provider is a registered and authenticated legal user. Next, the system will verify whether the service provider meets the platform's business rules, such as whether it has sufficient credit or whether there is a record of violations in past transactions. At the same time, the system will also check the cooperation status between the service provider and the platform (such as whether there is a valid service contract, whether the fees are paid on time, etc.) to ensure that the service provider is in a compliant state. If all verifications are passed, the system will create a bookkeeping service provider session information, record the service provider's ID, login status, login time, permission level and other information, and encrypt and store it in the session cache. The encryption process of the session information ensures the security of the data and ensures that it will automatically expire at the end of the session to prevent the session information from being maliciously used.

[0069] S30: Verify the cooperation relationship between the accounting service provider and the target enterprise according to the accounting service provider session information, and obtain a cooperation verification result. If the cooperation verification result is qualified, generate a possession operation request information.

[0070] Specifically, the system will compare the session information of the bookkeeping service provider with the contract database of the target enterprise, and first confirm whether the bookkeeping service provider has established an effective cooperative relationship with the enterprise. The verification process includes checking whether the service contract between the bookkeeping service provider and the target enterprise has been signed, whether the contract is within the validity period (such as the service start date and end date), and whether the service provider has fulfilled the relevant terms in accordance with the contract (such as payment of fees, provision of services, etc.). If the cooperation verification between the bookkeeping service provider and the target enterprise is passed, the system will continue to generate the possession operation request information. The possession operation request includes the identity of the bookkeeping service provider, the basic information of the target enterprise, the cooperation status, and the specific operation permissions authorized. If the cooperation verification fails, the system will refuse to generate the possession request and return an error message (such as the invalid cooperation relationship).

[0071] S40: Generate an attachment token based on the attachment operation request information, and return the attachment token to the client of the accounting service provider. The accounting service provider uses the attachment token to enter the management end of the target enterprise.

[0072] Specifically, after confirming that the partnership is valid, the system will generate a unique attachment token for the accounting service provider based on the attachment operation request information. The generation process of the attachment token includes: First, the system will select a standard encryption algorithm to generate a token containing the following information: accounting service provider ID, target enterprise ID, scope of authority, token validity period (usually 30 minutes or variable according to the platform settings), and other relevant authentication information. The generated attachment token will be returned to the client of the accounting service provider in an encrypted format. The data part of the token is encrypted to ensure that the token content will not be tampered with during transmission. After the client of the accounting service provider receives the token, it can send the token to the management end of the target enterprise through an HTTP request. After verifying the legitimacy of the token, the system will automatically authorize the accounting service provider to enter the management end and simulate the role of the enterprise administrator to perform accounting operations.

[0073] S50: The management end verifies the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the accounting service provider is loaded.

[0074] Specifically, when the target enterprise's management end receives the attached token of the accounting service provider, it will first decrypt the token to ensure that the information in the token has not been tampered with. The system will parse the information in the attached token and check the following key points: first, verify whether the token is within the validity period to ensure that the current request is issued within the validity period of the token; second, verify whether the accounting service provider ID matches the target enterprise ID to ensure that the accounting service provider is an authorized service provider; then, verify whether the operation permissions contained in the token are in line with the authority scope of the accounting service provider to prevent access or operation of unauthorized functions. If the verification is successful, the management end will load the operation interface that meets the authority of the accounting service provider, which usually includes functions such as accounting operations, financial report generation, and data entry, and will not display management modules that are not authorized by the enterprise. The system will dynamically adjust the display content of the interface based on predefined authority control rules, such as hiding certain management functions or limiting access rights to certain sensitive data, to ensure that the accounting service provider can only operate within the authorized scope to avoid abuse or misoperation of enterprise data.

[0075] In one embodiment, if Figure 2 As shown, in step S20, the identity information of the bookkeeping service provider is verified with the preset identity authentication rules to obtain an identity authentication result. If the identity authentication result is that the authentication is passed, the bookkeeping service provider session information is generated, which also includes:

[0076] S201: If the identity authentication result is that the authentication fails, the login request of the accounting service provider is rejected, and a verification failure message is sent to the accounting service provider.

[0077] Specifically, when a bookkeeping service provider attempts to log in, the system will first verify the submitted identity information (such as username and password). If the verification fails, the system will immediately reject the login request, stop further identity authentication operations on the bookkeeping service provider, and return it to the bookkeeping service provider through a response message. The verification failure information contains detailed reasons for failure, such as incorrect username or password, frozen account, identity verification failure, etc., so that the service provider can understand the specific reasons for the verification failure. The system will adopt appropriate error handling mechanisms, such as recording the number of failures and timestamping failed attempts for subsequent processing.

[0078] S201: Based on the verification failure information, the bookkeeping service provider is allowed to resubmit identity information for re-verification. If the bookkeeping service provider fails to verify continuously within a preset number of verification attempts, the login authority of the bookkeeping service provider is temporarily restricted.

[0079] Specifically, the system allows the accounting service provider to continue to try to resubmit identity information for verification after the first verification fails. During this period, the accounting service provider can change the password, check whether the username is correct, or make other corrections according to the verification failure information prompt. To ensure the security of the system, the system will limit the number of retries of the accounting service provider, and usually set a preset maximum number of retries (such as 3 times). If the accounting service provider fails to verify continuously within the specified number of verifications, the system will temporarily limit the login permission to prevent brute force attacks. The duration of the login restriction can be dynamically adjusted according to the system settings, usually 10 minutes, 30 minutes or longer, during which the service provider cannot resubmit identity information for verification. The system will also send a notification to the accounting service provider, informing it that the account has been temporarily locked due to continuous verification failures, and provide steps to restore login, such as resetting the password through email or mobile phone, or manual verification and recovery through customer service.

[0080] In one embodiment, if Figure 3 As shown, in step S30, the cooperation relationship between the bookkeeping service provider and the target enterprise is verified, including:

[0081] S301: Obtain the cooperation agreement between the bookkeeping service provider and the target enterprise, verify the validity of the cooperation agreement through the cooperation agreement database, and obtain the validity verification result.

[0082] Specifically, based on the request submitted by the bookkeeping service provider, the system will first query the cooperation agreement information related to the target enterprise from the cooperation agreement database. These cooperation agreements will contain key information such as the cooperation terms, service content, agreement period, payment method, etc. of both parties. The system will verify the validity of these agreement data, mainly to verify whether the agreement is within the validity period, whether it meets the compliance requirements signed by both parties, and whether there are any records of breach or cancellation. Validity verification can be completed by checking the signing time of the agreement, the status of the agreement (such as valid, terminated, pending activation, etc.), and any supplementary agreements or change records. If there is an abnormality in the agreement (such as expiration, cancellation, incomplete signing, etc.), the system will return a verification failure result and prevent the bookkeeping service provider from continuing the attachment operation.

[0083] S302: judging whether the bookkeeping service provider has the authority to access the target enterprise management terminal according to the validity verification result; if the verification is successful, it is determined that there is a valid cooperative relationship between the bookkeeping service provider and the target enterprise.

[0084] Specifically, the system will determine whether the accounting service provider has sufficient authority to access the target enterprise's management terminal based on the validity verification results. If the cooperation agreement passes the validity verification, the system will further confirm the operating permissions obtained by the accounting service provider in the agreement, especially whether the accounting service provider is authorized to access the enterprise's financial data and perform accounting operations. The system will check the permission clauses in the cooperation agreement, such as accounting permissions, data query permissions, audit permissions, etc., and verify whether the accounting service provider has clearly obtained these permissions in the agreement. If the accounting service provider has the right to enter the enterprise's management terminal, the system will mark the cooperation relationship as valid and allow the accounting service provider to continue to perform related operations, such as initiating a login request. If the verification fails, the system will return an error message of insufficient permissions and refuse the accounting service provider to perform further operations.

[0085] In one embodiment, if Figure 4 As shown, in step S302, that is, according to the validity verification result, it is determined whether the bookkeeping service provider has the authority to access the target enterprise management terminal. If the verification is successful, it is determined that there is a valid cooperative relationship between the bookkeeping service provider and the target enterprise, and it also includes:

[0086] S3021: If the verification fails, the access request of the bookkeeping service provider is rejected, and a cooperation relationship verification failure message is sent to the bookkeeping service provider.

[0087] Specifically, if the cooperation agreement between the accounting service provider and the target enterprise fails to pass the validity verification, the access request of the accounting service provider will be rejected immediately. At this time, the system will send a cooperation relationship verification failure message to the terminal of the accounting service provider, prompting the accounting service provider that it cannot currently access the management end of the target enterprise. The information will include the specific reasons for the failure, such as the expiration of the cooperation agreement, the failure to sign the cooperation agreement, insufficient authority of the service provider, etc., and provide certain suggestions or explanations to help the accounting service provider understand the cause of the error. The system may also mark the request of the accounting service provider as a failure to avoid continuing to initiate invalid avatar login requests. This step ensures that only accounting service providers under a valid cooperation relationship can continue to access the enterprise management end to avoid unauthorized access or operation.

[0088] S3022: Based on the partnership verification failure information, provide the bookkeeping service provider with resubmission verification request information.

[0089] Specifically, the system will provide the accounting service provider with the function of resubmitting the verification request based on the information of failed verification of the partnership. The system will allow the accounting service provider to make necessary modifications or additions (such as updating the agreement, resubmitting the cooperation agreement, providing more certification materials, etc.) based on the verification failure information received, and then re-initiate the verification request. For the convenience of service providers, the system will list specific operation steps and requirements in the failure information, such as providing new agreement documents, reconfirming the terms of cooperation, etc. The service provider can submit the verification again within the specified time. After receiving the new request, the system will process the verification request according to the same verification process as before. If the verification still fails within the preset number of verifications, the system may restrict the accounting service provider from continuing to initiate verification requests, or take more stringent security measures (such as manual review).

[0090] In one embodiment, if Figure 5 As shown, in step S40, the attachment token is generated according to the attachment operation request information, including:

[0091] S401: According to the attachment operation request information, the identity information of the bookkeeping service provider, the target enterprise identifier and the attachment request timestamp are obtained, and the identity information, the target enterprise identifier and the request timestamp are concatenated to form the original information of the attachment token.

[0092] Specifically, according to the attachment operation request of the accounting service provider, the system first extracts the identity information of the accounting service provider, the identifier of the target enterprise, and the timestamp information of the attachment request. This information is the basis for the generation of the attachment token. The identity information is used to verify the identity of the accounting service provider to ensure that the accounting service provider has legal operating authority. The target enterprise identifier indicates the enterprise involved in the request to ensure that the token is limited to the target enterprise. The timestamp records the specific time of the attachment operation to prevent the token from being abused after it expires. The system splices this information into the original information of the attachment token in a predetermined format to ensure the uniqueness and non-tamperability of the original information of each attachment token. This step ensures that the attachment token can contain all necessary authentication and access control information, and the structure after the information splicing is convenient for subsequent encryption and verification operations.

[0093] S402: Hash the original information of the attached token to generate a unique attached token identifier, bind the unique attached token identifier with the authority information of the bookkeeping service provider and the token validity period, and generate the attached token.

[0094] Specifically: First, the system extracts the following elements from the original information of the attached token obtained in the previous step: the identity information of the bookkeeping service provider, the identifier of the target enterprise, and the timestamp of the attachment request. Next, the system performs hash processing on the extracted original information of the attached token. An irreversible hash algorithm (such as SHA-256 or SHA-512) is usually used, which can convert data of any length into a hash value of fixed length, ensuring that the generated attached token identifier is unique and irreversible. The hash processing process includes: calculating the hash value of the spliced ​​information. The corresponding hash value is generated by the hash algorithm, and the spliced ​​original information of the attached token is converted into a hash value string. The hash value string ensures the immutability and uniqueness of the attached token. Even if there is any slight change in the original information, the generated hash value will change, thereby ensuring that the attached token accurately matches the input data. The result of the hash processing is the unique identifier of the attached token. This identifier usually consists of characters of a fixed length and does not contain any plaintext information, thus avoiding the risk of data leakage. The system generates a unique and encrypted token identifier through the hash result. The system binds the authority information of the accounting service provider to the avatar token identifier. The authority information includes the specific operation scope of the management end of the target enterprise that the accounting service provider is authorized to access, such as account viewing, account entry, financial report generation, etc. The system extracts the authority scope of the accounting service provider by consulting the preset authority table and associates this information with the avatar token identifier. For example, if the accounting service provider is only authorized to view bills and report data, this information will be recorded in the avatar token. Next, the system sets the validity period for the generated avatar token. Setting the token validity period is a key step to ensure system security and prevent the token from being abused after the authorization expires. The validity period is generally controlled by setting a specific timestamp, such as the token is valid for 24 hours from the time it is generated. This timestamp will be bound to the avatar token identifier to ensure that the token is only available within a predetermined time range. If it expires, the system will automatically reject the access request of the accounting service provider. Finally, the system combines the avatar token identifier, the authority information of the accounting service provider, and the token validity period to form a complete avatar token.

[0095] In one embodiment, if Figure 6 As shown, in step S50, the management end verifies the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the bookkeeping service provider is loaded, which also includes:

[0096] S501: If the attachment token verification fails, the attachment operation is terminated and the attachment token verification failure information is sent to the accounting service provider.

[0097] Specifically, in the process of verifying the attached token, the system will perform a legitimacy check on the attached token, such as verifying the validity of the attached token and whether it meets the permission requirements. If the attached token does not comply with the regulations (such as the token has expired, the identity information in the token does not match, etc.), the system will immediately terminate the attached operation and prevent the accounting service provider from continuing to access the management end of the target enterprise. At the same time, the system will generate a verification failure message and promptly notify the accounting service provider of the specific reason for the failure of the attached token verification through message push or interface feedback. For example, the system can prompt that the attached token has expired or the token is invalid, ensuring that the accounting service provider understands why the attached operation cannot continue. This step ensures that the system can terminate illegal operations in a timely and secure manner when the attached token verification fails to prevent unauthorized access.

[0098] S502: According to the authentication failure information of the attachment token, the accounting service provider is triggered to re-initiate the attachment request. If the accounting service provider fails to re-submit the attachment request within a specified time, the access rights of the accounting service provider are temporarily frozen.

[0099] Specifically, when the authentication of the attachment token fails, the system will not only send an error message to the accounting service provider, but also trigger an automated process to allow the accounting service provider to re-initiate the attachment request within a certain period of time. The system will set a specified time limit (for example, 30 minutes, 1 hour, etc.), during which the accounting service provider needs to resubmit the attachment request through the correct identity authentication and token acquisition process. If the accounting service provider fails to re-initiate the request or fails to pass the authentication within the specified time, the system will take temporary measures to freeze the access rights of the accounting service provider. During the freezing period, the accounting service provider will not be able to perform the attachment operation or access the management end of the target enterprise again until the identity information and authorization request of the accounting service provider are re-verified.

[0100] In one embodiment, if Figure 7 As shown, after step S50, the accounting service provider login management method further includes:

[0101] S60: Acquire the validity period information of the attached token, and compare the validity period information with the current time information. If the validity period information has been reached, the attached token is invalid.

[0102] Specifically, the system will extract the validity period information from the attached token, which is usually generated by the back-end server according to a predetermined rule or protocol when the attached token is generated, such as set to 1 hour, 24 hours or other time periods. When the accounting service provider attempts to use the attached token, the system will obtain the current time information in real time and compare it with the validity period information stored in the attached token. If it is found that the current time is beyond the validity period, the system will immediately mark the attached token as invalid and prevent the accounting service provider from continuing to use the token for attachment operations. At this point, the accounting service provider will not be able to access the management end of the target enterprise until a valid attached token is obtained again.

[0103] S70: Obtain the exit operation information of the bookkeeping service provider. Based on the exit operation information, if the bookkeeping service provider exits the target enterprise management terminal, the attached token is destroyed and becomes invalid.

[0104] Specifically, after the accounting service provider completes the attachment operation, if it chooses to exit the target enterprise's management terminal, the system will capture the exit operation information. The exit operation is usually triggered by the accounting service provider clicking the exit button or other related operations. When the exit operation is detected, the system will automatically destroy the attachment token associated with the session to ensure that the token is invalid. During the destruction of the attachment token, all identity information, permission information and access records related to the token will be cleared to ensure that the accounting service provider cannot continue to access the target enterprise's management terminal or perform any further operations after the exit.

[0105] S80: Acquire the information on the termination of cooperation by the enterprise. According to the information on the termination of cooperation by the enterprise, if the target enterprise terminates the cooperation relationship with the bookkeeping service provider, the attached token is revoked and becomes invalid.

[0106] Specifically, when the target enterprise decides to terminate its cooperation with the bookkeeping service provider, the system will receive the enterprise's notice or request for termination of cooperation. The termination request may be initiated by the enterprise, or it may be automatically triggered by the system based on the expiration of the contract or other conditions. After receiving the information of termination of cooperation, the system will immediately revoke the relevant avatar token to ensure that the token is invalid. The revocation operation includes deleting the permission identification, timestamp and other information in the avatar token, and marking it as invalid to prevent the bookkeeping service provider from continuing to use the original avatar token to access the enterprise management end.

[0107] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0108] In one embodiment, a billing service provider avatar login management device is provided, and the billing service provider avatar login management device corresponds to the billing service provider avatar login management method in the above embodiment. Figure 8 As shown, the attached login management device for bookkeeping service providers includes an identity information acquisition module, an identity authentication and session generation module, a partnership verification module, an attached token generation module, and an attached token validity verification and interface loading module. The detailed description of each functional module is as follows:

[0109] An identity information acquisition module is used to obtain the identity information of the bookkeeping service provider;

[0110] The identity authentication and session generation module is used to verify the identity information of the bookkeeping service provider with the preset identity authentication rules to obtain the identity authentication result. If the identity authentication result is that the authentication is passed, the session information of the bookkeeping service provider is generated;

[0111] The cooperation relationship verification module is used to verify the cooperation relationship between the bookkeeping service provider and the target enterprise according to the bookkeeping service provider session information, and obtain the cooperation verification result. If the cooperation verification result is qualified, the attachment operation request information is generated;

[0112] The attachment token generation module is used to generate an attachment token according to the attachment operation request information, and return the attachment token to the client of the agency bookkeeping service provider. The agency bookkeeping service provider uses the attachment token to enter the management end of the target enterprise;

[0113] The module for verifying the validity of the attached token and loading the interface is used by the management side to verify the validity of the attached token. If the attached token is verified, the enterprise management side interface that complies with the authority of the accounting service provider is loaded.

[0114] Optionally, the authentication and session generation module also includes:

[0115] The identity authentication failure processing submodule is used to reject the login request of the bookkeeping service provider if the identity authentication result is that the authentication fails, and send a verification failure message to the bookkeeping service provider;

[0116] The verification retry and access restriction submodule is used to allow the bookkeeping service provider to resubmit identity information for re-verification based on the verification failure information. If the bookkeeping service provider fails to verify continuously within a preset number of verifications, the login authority of the bookkeeping service provider will be temporarily restricted.

[0117] Optional partnership verification modules include:

[0118] The attachment token verification failure submodule is used to terminate the attachment operation and send the attachment token verification failure information to the accounting service provider if the attachment token verification fails;

[0119] The access permission control submodule is used to trigger the bookkeeping service provider to re-initiate the attachment request according to the attachment token verification failure information. If the bookkeeping service provider fails to re-submit the attachment request within the specified time, the access permission of the bookkeeping service provider will be temporarily frozen.

[0120] The cooperation agreement validity verification submodule is used to obtain the cooperation agreement between the bookkeeping service provider and the target enterprise, verify the validity of the cooperation agreement through the cooperation agreement database, and obtain the validity verification result;

[0121] The access authority judgment and cooperation relationship confirmation submodule is used to judge whether the bookkeeping service provider has the authority to access the target enterprise management terminal based on the validity verification result. If the verification is successful, it is determined that there is a valid cooperation relationship between the bookkeeping service provider and the target enterprise.

[0122] Optionally, the access rights determination and partnership confirmation submodule also includes:

[0123] A cooperation relationship verification failure processing unit, used to reject the access request of the bookkeeping service provider if the verification fails, and send a cooperation relationship verification failure message to the bookkeeping service provider;

[0124] The re-verification request processing unit is used to provide re-submission verification request information to the bookkeeping service provider according to the cooperation relationship verification failure information.

[0125] Optionally, the attachment token generation module includes:

[0126] The attachment token original information generation submodule is used to obtain the identity information of the bookkeeping service provider, the target enterprise identifier and the attachment request timestamp according to the attachment operation request information, and to concatenate the identity information, the target enterprise identifier and the request timestamp to form the attachment token original information;

[0127] The avatar token generation and binding submodule is used to hash the original information of the avatar token to generate a unique avatar token identifier, bind the unique avatar token identifier with the authority information of the bookkeeping service provider and the token validity period, and generate the avatar token.

[0128] Optionally, the attachment token validity verification and interface loading module also includes:

[0129] The attachment token verification and failure processing submodule is used to terminate the attachment operation and send the attachment token verification failure information to the accounting service provider if the attachment token verification fails;

[0130] The attachment request retry and access rights freezing submodule is used to trigger the accounting service provider to re-initiate the attachment request based on the attachment token verification failure information. If the accounting service provider fails to resubmit the attachment request within the specified time, the access rights of the accounting service provider will be temporarily frozen.

[0131] Optionally, the validation of the attached token and the interface loading module also include:

[0132] The attachment token validity period management module is used to obtain the validity period information of the attachment token and compare the validity period information with the current time information. If the validity period information has been reached, the attachment token is invalid;

[0133] The accounting service provider exit operation processing module is used to obtain the exit operation information of the accounting service provider. Based on the exit operation information, if the accounting service provider exits the target enterprise management terminal, the attached token is destroyed and becomes invalid;

[0134] The enterprise cooperation termination and attached token revocation module is used to obtain the enterprise cooperation termination information. According to the enterprise cooperation termination information, if the target enterprise terminates the cooperation relationship with the bookkeeping service provider, the attached token will be revoked and become invalid.

[0135] The specific definition of the attached login management device for the accounting service provider can be found in the definition of the attached login management method for the accounting service provider mentioned above, which will not be repeated here. Each module in the above-mentioned attached login management device for the accounting service provider can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0136] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used for a cooperation agreement database. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for managing the login of an accounting service provider is implemented.

[0137] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0138] Obtain the identity information of the bookkeeping service provider;

[0139] Verify the identity information of the bookkeeping service provider with the preset identity authentication rules to obtain the identity authentication result. If the identity authentication result is that the authentication is passed, generate the bookkeeping service provider session information;

[0140] According to the session information of the bookkeeping service provider, the cooperation relationship between the bookkeeping service provider and the target enterprise is verified, and the cooperation verification result is obtained. If the cooperation verification result is qualified, the attachment operation request information is generated;

[0141] Generate an attachment token based on the attachment operation request information, and return the attachment token to the client of the agency bookkeeping service provider. The agency bookkeeping service provider uses the attachment token to enter the management end of the target enterprise;

[0142] The management end verifies the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the accounting service provider is loaded.

[0143] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0144] Obtain the identity information of the bookkeeping service provider;

[0145] Verify the identity information of the bookkeeping service provider with the preset identity authentication rules to obtain the identity authentication result. If the identity authentication result is that the authentication is passed, generate the bookkeeping service provider session information;

[0146] According to the session information of the bookkeeping service provider, the cooperation relationship between the bookkeeping service provider and the target enterprise is verified, and the cooperation verification result is obtained. If the cooperation verification result is qualified, the attachment operation request information is generated;

[0147] Generate an attachment token based on the attachment operation request information, and return the attachment token to the client of the agency bookkeeping service provider. The agency bookkeeping service provider uses the attachment token to enter the management end of the target enterprise;

[0148] The management end verifies the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the accounting service provider is loaded.

[0149] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0150] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0151] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for managing the in-person login of an accounting service provider, characterized in that: The accounting service provider login management method includes: Obtain the identity information of the bookkeeping service provider; Verifying the identity information of the bookkeeping service provider with a preset identity verification rule to obtain an identity verification result, and if the identity verification result is a passed verification, generating bookkeeping service provider session information; Verify the cooperation relationship between the accounting service provider and the target enterprise according to the accounting service provider session information, and obtain a cooperation verification result. If the cooperation verification result is qualified, generate an attachment operation request information; Generate an attachment token according to the attachment operation request information, return the attachment token to the client of the agency bookkeeping service provider, and the agency bookkeeping service provider uses the attachment token to enter the management end of the target enterprise; The management end verifies the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the bookkeeping service provider is loaded; The step of generating an attachment token according to the attachment operation request information includes: According to the attachment operation request information, the identity information of the accounting service provider, the target enterprise identifier and the attachment request timestamp are obtained, and the identity information, the target enterprise identifier and the request timestamp are concatenated to form the original information of the attachment token; The original information of the attached token is hashed to generate a unique attached token identifier, and the unique attached token identifier is bound to the authority information of the bookkeeping service provider and the token validity period to generate the attached token.

2. The method for managing the avatar login of an accounting service provider according to claim 1, characterized in that: The step of verifying the identity information of the bookkeeping service provider with a preset identity authentication rule to obtain an identity authentication result, and if the identity authentication result is a passed authentication, generating the bookkeeping service provider session information, further includes: If the identity authentication result is a verification failure, rejecting the login request of the bookkeeping service provider and sending a verification failure message to the bookkeeping service provider; Based on the verification failure information, the bookkeeping service provider is allowed to resubmit the identity information for re-verification. If the bookkeeping service provider fails in verification continuously within a preset number of verification attempts, the login authority of the bookkeeping service provider is temporarily restricted.

3. The method for managing the avatar login of an accounting service provider according to claim 1, characterized in that: The verification of the cooperative relationship between the bookkeeping service provider and the target enterprise includes: Obtaining the cooperation agreement between the bookkeeping service provider and the target enterprise, verifying the validity of the cooperation agreement through a cooperation agreement database, and obtaining a validity verification result; According to the validity verification result, it is determined whether the bookkeeping service provider has the authority to access the target enterprise management terminal. If the verification is successful, it is determined that there is a valid cooperative relationship between the bookkeeping service provider and the target enterprise.

4. The method for managing the avatar login of an accounting service provider according to claim 3, characterized in that: The step of judging whether the bookkeeping service provider has the authority to access the target enterprise management terminal according to the validity verification result, and if the verification is successful, determining that there is a valid cooperative relationship between the bookkeeping service provider and the target enterprise, further includes: If the verification fails, the access request of the bookkeeping service provider is rejected, and a cooperation relationship verification failure message is sent to the bookkeeping service provider; According to the partnership verification failure information, resubmission verification request information is provided to the bookkeeping service provider.

5. The method for managing the avatar login of an accounting service provider according to claim 1, characterized in that: The management end verifies the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the bookkeeping service provider is loaded, and further includes: If the attachment token verification fails, the attachment operation is terminated and the attachment token verification failure information is sent to the accounting service provider; According to the verification failure information of the attachment token, the accounting service provider is triggered to re-initiate the attachment request. If the accounting service provider fails to re-submit the attachment request within a specified time, the access rights of the accounting service provider are temporarily frozen.

6. The method for managing the avatar login of an accounting service provider according to claim 1, characterized in that: The accounting service provider login management method further includes: Acquire the validity period information of the attached token, compare the validity period information with the current time information, and if the validity period information has been reached, the attached token is invalid; Acquire the exit operation information of the bookkeeping service provider, and based on the exit operation information, if the bookkeeping service provider exits the target enterprise management terminal, the attached token is destroyed and becomes invalid; The enterprise cooperation termination information is obtained. According to the enterprise cooperation termination information, if the target enterprise terminates the cooperation relationship with the bookkeeping service provider, the attached token is revoked and becomes invalid.

7. A device for managing the in-person login of an accounting service provider, characterized in that: The accounting service provider login management device comprises: An identity information acquisition module is used to obtain the identity information of the bookkeeping service provider; An identity authentication and session generation module, used to verify the identity information of the bookkeeping service provider with a preset identity authentication rule to obtain an identity authentication result, and if the identity authentication result is a passed authentication, generate session information of the bookkeeping service provider; A cooperation relationship verification module, used to verify the cooperation relationship between the agency accounting service provider and the target enterprise according to the agency accounting service provider session information, obtain a cooperation verification result, and generate an attachment operation request information if the cooperation verification result is qualified; An attachment token generation module, used to generate an attachment token according to the attachment operation request information, and return the attachment token to the client of the agency bookkeeping service provider, and the agency bookkeeping service provider uses the attachment token to enter the management end of the target enterprise; The module for verifying the validity of the attached token and loading the interface is used by the management end to verify the validity of the attached token. If the attached token passes the verification, the enterprise management end interface that complies with the authority of the bookkeeping service provider is loaded; The attachment token generation module includes: The attachment token original information generation submodule is used to obtain the identity information, target enterprise identifier and attachment request timestamp of the accounting service provider according to the attachment operation request information, and to concatenate the identity information, the target enterprise identifier and the request timestamp to form the attachment token original information; The attached token generation and binding submodule is used to perform hash processing on the original information of the attached token to generate a unique attached token identifier, bind the unique attached token identifier with the authority information of the accounting service provider and the token validity period, and generate the attached token.

8. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method for managing the avatar login of an accounting service provider as claimed in any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method for managing the avatar login of an accounting service provider as claimed in any one of claims 1 to 6 are implemented.

Images