User login authentication method and system of collaborative office tool

Abstract

The invention belongs to the field of data communication, and provides a user login authentication method and system for a collaborative office tool, and the method comprises the steps that a network development platform receives a Cookie file and a web project website of a user side; whether the dynamic token exists in the Cookie file or not and whether the dynamic token is effective or not are judged; when the user dynamic token exists and the dynamic token is valid, sending a project page corresponding to the web project website to the user side; otherwise, generating a login two-dimensional code of the collaborative office tool and sending the login two-dimensional code to the user side, so that the user performs code scanning login and jumps to the project callback address; receiving a collaborative office tool return code in the project callback address to obtain a user ID; and creating a dynamic token by using the user ID and storing the dynamic token, and sending a project page corresponding to the web project website to the user side based on the dynamic token. According to the invention, the login authentication of the user is realized by utilizing data interaction among the network development platform, the user side and the collaborative office tool.

Description

Technical Field

[0001] The present invention belongs to the technical field of data communication, and in particular relates to a user login authentication method and system for collaborative office tools. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.

[0003] With the development of Internet technology and the increasing popularity of agile development concepts, many collaborative office tools have emerged (such as WeChat for Enterprise, Feishu, DingTalk, etc.). More and more companies and developers have chosen to use collaborative office tools for authorized login in the process of developing web projects. However, some projects do not have built-in login functions for various reasons, and users cannot authenticate their identities when accessing them, making it difficult to ensure project security or provide personalized user experience.

[0004] The traditional docking method usually requires the cooperation of the front-end and the back-end, which requires a major transformation of the project and involves a large number of code modifications. The cumbersome docking leads to increased labor costs; and the functions that have been written cannot be reused in other projects. At the same time, it increases the complexity of the code and causes compatibility problems with the update of the original project. Summary of the invention

[0005] In order to solve the above problems, the present invention proposes a user login authentication method and system for collaborative office tools. The present invention pre-places the user login authentication process of the entire collaborative office tool in the web hosting tool to make a pluggable module. It does not require the cooperation of the front-end and the back-end, and utilizes the data interaction between the network development platform, the user end and the collaborative office tool to realize user login authentication, thereby simplifying the process of developing web projects.

[0006] According to some embodiments, a first solution of the present invention provides a user login authentication method for a collaborative office tool, which adopts the following technical solution:

[0007] A user login authentication method for a collaborative office tool, comprising:

[0008] The web development platform receives the user's Cookie file and web project URL;

[0009] The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid;

[0010] When there is a user dynamic token and the dynamic token is valid, the network development platform sends a project page corresponding to the web project website to the user terminal;

[0011] Otherwise, generate a login QR code for the collaborative office tool and send it to the user end so that the user can scan the code to log in and jump to the project callback address;

[0012] The network development platform receives the collaborative office tool return code in the project callback address, and uses the collaborative office tool return code to obtain the user ID;

[0013] The network development platform creates and stores a dynamic token using the user ID, and sends a project page corresponding to the web project website to the user terminal based on the stored dynamic token.

[0014] Furthermore, the network development platform determines whether there is a dynamic token in the Cookie file and whether the dynamic token is valid, specifically:

[0015] If the dynamic token does not exist in the cookie file, the dynamic token is considered invalid;

[0016] If there is a dynamic token in the cookie, the dynamic token will be decrypted. If the decryption fails, the dynamic token will be considered invalid.

[0017] If the decryption is successful, the decrypted information is obtained, wherein the decrypted information includes a user ID field and an expiration time field;

[0018] According to the expiration time field in the decrypted information, determine whether the dynamic token has expired. If it has expired, the dynamic token is considered invalid;

[0019] If it has not expired, determine whether the user ID field in the decrypted information is empty. If it is empty, the dynamic token is deemed invalid. Otherwise, the dynamic token is deemed valid.

[0020] Furthermore, the generated collaborative office tool login QR code is sent to the user terminal so that the user scans the code to log in, specifically:

[0021] Get the initial URL of the collaborative office software;

[0022] The project callback address, project application number and collaborative office tool number in the configuration file are used to replace the initial callback address, initial project application number and initial collaborative office tool number in the initial URL of the collaborative office software, and a login QR code display URL of the collaborative office tool is generated;

[0023] The network development platform sends the login QR code display website of the collaborative office tool to the user terminal to display the login QR code.

[0024] Furthermore, the method of obtaining the user ID by using the return code of the collaborative office tool is as follows:

[0025] Calling the office tool background application programming interface through the collaborative office tool return code;

[0026] Get the user ID according to the office tool background application programming interface.

[0027] Furthermore, before being called, the collaborative office tool is configured, specifically:

[0028] Create a project application entry corresponding to the web project in the background of the collaborative office tool;

[0029] Based on the created project application entry, obtain project application information;

[0030] Set corresponding login methods based on different collaborative office tools;

[0031] Set the project callback address according to the web project URL;

[0032] Set the key and validity period of the token and generate token information;

[0033] Generate a configuration file based on the project application information, project callback address, login method, and token information.

[0034] Furthermore, the project application information includes an organization ID, an application key, and an application ID;

[0035] The organization ID is the number of the collaborative office tool;

[0036] Application ID is the ID of the created project application entry;

[0037] The application key is an interface access key randomly generated by the collaborative office tool when the project application portal is created.

[0038] Furthermore, the token information includes a token key and a token validity period.

[0039] According to some embodiments, a second solution of the present invention provides a user login authentication system for collaborative office tools, which adopts the following technical solution:

[0040] A user login authentication system for collaborative office tools, comprising a user terminal, a network development platform and a collaborative office tool; wherein:

[0041] The user terminal receives the web project URL logged in by the user;

[0042] The web development platform receives the user's Cookie file and web project URL;

[0043] The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid;

[0044] When there is a user dynamic token and the dynamic token is valid, the network development platform sends a project page corresponding to the web project website to the user terminal;

[0045] Otherwise, generate a login QR code for the collaborative office tool and send it to the user end so that the user can scan the code to log in and jump to the project callback address;

[0046] The network development platform receives the collaborative office tool return code in the project callback address, and uses the collaborative office tool return code to obtain the user ID;

[0047] The network development platform creates and stores a dynamic token using the user ID, and sends a project page corresponding to the web project website to the user terminal based on the stored dynamic token.

[0048] According to some embodiments, a third aspect of the present invention provides a computer-readable storage medium.

[0049] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps in a user login authentication method for a collaborative office tool as described in the first aspect above.

[0050] According to some embodiments, a fourth aspect of the present invention provides a computer device.

[0051] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor. When the processor executes the program, the steps in the user login authentication method for a collaborative office tool as described in the first aspect above are implemented.

[0052] Compared with the prior art, the present invention has the following beneficial effects:

[0053] The present invention can achieve faster docking. In the traditional docking method, at least the front-end and back-end codes need to be updated during the docking process, which increases the complexity of the docking. The program of the present invention is a static code, which can achieve fast deployment docking. The entire deployment process only requires changing the parameters in the configuration file, which has zero impact on the business.

[0054] The project compatibility of the present invention is good and can be quickly reused. In the traditional docking method, different projects need to develop different codes to dock with collaborative office tools. The "pluggable" design of this method brings better compatibility and can be quickly reused in multiple projects. In theory, it can be compatible with all web systems without repeated development.

[0055] The present invention does not need to invade the original project code, and has lower labor costs. In the traditional docking method, front-end engineers and back-end engineers are usually required to cooperate in code development, which requires a lot of labor costs and increases the complexity of the code. The "pluggable" design of this method does not require changing the project code. During the entire deployment process, only one person is required to operate to complete the rapid docking and launch of the project.

[0056] The present invention can realize logic more simply, with higher operation efficiency and high scalability. In the traditional docking mode, the front-end and back-end programs need to be coordinated and realized, and the realization logic is complex. The present method is realized based on Openresty and Lua structure, without the intervention of the front-end and back-end programs, and the logic is simpler. Thanks to the characteristics of Openresty supporting load balancing, the present method can be quickly expanded horizontally, further improving the operation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0058] Figure 1 The present invention is a flowchart of a user login authentication method for a collaborative office tool in an embodiment of the present invention. DETAILED DESCRIPTION

[0059] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0060] It should be noted that the following detailed descriptions are all illustrative and intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present invention belongs.

[0061] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit exemplary embodiments according to the present invention. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprising" and / or "including" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0062] In the absence of conflict, the embodiments of the present invention and the features of the embodiments may be combined with each other.

[0063] Terminology explanation:

[0064] OpenResty: OpenResty is a high-performance Web platform based on Nginx and Lua, which integrates a large number of sophisticated Lua libraries, third-party modules, and most dependencies. It is used to easily build dynamic Web applications, Web services, and dynamic gateways that can handle ultra-high concurrency and high scalability.

[0065] Embodiment 1

[0066] This embodiment provides a user login authentication method for a collaborative office tool. In this embodiment, the method includes the following steps:

[0067] The web development platform receives the user's Cookie file and web project URL;

[0068] The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid;

[0069] When there is a user dynamic token and the dynamic token is valid, the network development platform sends a project page corresponding to the web project website to the user terminal;

[0070] Otherwise, generate a login QR code for the collaborative office tool and send it to the user end so that the user can scan the code to log in and jump to the project callback address;

[0071] The network development platform receives the collaborative office tool return code in the project callback address, and uses the collaborative office tool return code to obtain the user ID;

[0072] The network development platform creates and stores a dynamic token using the user ID, and sends a project page corresponding to the web project website to the user terminal based on the stored dynamic token.

[0073] The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid, specifically:

[0074] If the dynamic token does not exist in the cookie file, the dynamic token is considered invalid;

[0075] If there is a dynamic token in the cookie, the dynamic token will be decrypted. If the decryption fails, the dynamic token will be considered invalid.

[0076] If the decryption is successful, the decrypted information is obtained, wherein the decrypted information includes a user ID field and an expiration time field;

[0077] According to the expiration time field in the decrypted information, determine whether the dynamic token has expired. If it has expired, the dynamic token is considered invalid;

[0078] If it has not expired, determine whether the user ID field in the decrypted information is empty. If it is empty, the dynamic token is deemed invalid. Otherwise, the dynamic token is deemed valid.

[0079] The generating of the collaborative office tool login QR code and sending it to the user terminal so that the user can scan the code to log in is specifically as follows:

[0080] Get the initial URL of the collaborative office software;

[0081] The project callback address, project application number and collaborative office tool number in the configuration file are used to replace the initial callback address, initial project application number and initial collaborative office tool number in the initial URL of the collaborative office software, and a login QR code display URL of the collaborative office tool is generated;

[0082] The network development platform sends the login QR code display website of the collaborative office tool to the user terminal to display the login QR code.

[0083] The method of obtaining the user ID by using the return code of the collaborative office tool is as follows:

[0084] Calling the office tool background application programming interface through the collaborative office tool return code;

[0085] Get the user ID according to the office tool background application programming interface.

[0086] Before being called, the collaborative office tool is configured, specifically:

[0087] Create a project application entry corresponding to the web project in the background of the collaborative office tool;

[0088] Based on the created project application entry, obtain project application information;

[0089] Set corresponding login methods based on different collaborative office tools;

[0090] Set the project callback address according to the web project URL;

[0091] Set the key and validity period of the token and generate token information;

[0092] Generate a configuration file based on the project application information, project callback address, login method, and token information.

[0093] This embodiment aims to realize user identity authentication based on the high-performance processing capabilities of OpenResty and Lua, combined with JWT (JSON WebToken). Through the OAuth 2.0 protocol, it connects to collaborative office tools such as WeChat for Enterprise, Feishu and DingTalk to realize the Oauth login authentication function. This solution is suitable for fields such as information construction.

[0094] Before logging in and authenticating, you need to configure the collaborative office tool and generate a configuration file, specifically:

[0095] 1) Create a project application entry corresponding to the web project in the background of the collaborative office tool;

[0096] In order to enable users to connect with the office tool background based on the application when logging in to the web project on the user side, each web project that is connected to the collaborative office tool login needs to create a corresponding project application entrance in the collaborative office tool background;

[0097] 2) Based on the created project application portal, obtain project application information;

[0098] Among them, the project application information includes AppId (organization ID), Secret (application key), AgentId (application ID); it can be understood that the project application information is obtained in the background of the collaborative office tool;

[0099] AppId (Organization ID): is the ID of the collaborative office tool. Each organization (enterprise) has a unique ID. Collaborative office tools include but are not limited to WeChat for Enterprise, Feishu, DingTalk and other office software.

[0100] AgentId (application ID): is the ID of the created project application entry;

[0101] Secret (application key): It is the interface access key randomly generated by the collaborative office tool when the project application portal is created;

[0102] 3) Set different login methods based on different collaborative office tools;

[0103] Among them, login methods (login_methods) include but are not limited to wecom-Enterprise WeChat, feishu-Feishu, dingding-DingTalk;

[0104] 4) Set the project callback address (REDIRECT_URI) according to the web project website;

[0105] That is to say, the project callback address (web project URL + / oauth) corresponding to the web project is set in the background of the collaborative office tool, so that the user end can jump to the project callback address after obtaining the user's scan code information;

[0106] 5) Set the key and validity period of the token and generate token information;

[0107] The key and validity period configuration required for JWT Token generation;

[0108] Token key-Secret_Token: is the encryption and decryption key of JWT Token;

[0109] Token validity period - Token_life_time: is the validity period of the token;

[0110] 6) Generate a configuration file based on project application information, project callback address, login method and token information;

[0111] By saving the constructed configuration file in the network development platform, it can be called and read at any time.

[0112] like Figure 1 As shown, the access process is applied in the network development platform and specifically includes:

[0113] 1) Get the user's Cookie file and web project URL.

[0114] When the user enters the URL of the web development project in the browser on the user side, the browser will automatically send the cookie file to the web development platform;

[0115] 2) The network development platform determines whether the dynamic token in the Cookie file is valid.

[0116] The Lua script of OpenResty in the network development platform detects whether there is JWT Token login information in the cookie and determines whether it is valid (whether it has expired, whether it can be decrypted to obtain the user ID). The specific judgment process is:

[0117] If the dynamic token JWT (JSON Web Token) does not exist in the cookie, the dynamic token is considered invalid;

[0118] If there is a dynamic token in the cookie, the dynamic token JWT (JSON Web Token) will be decrypted. If the decryption fails, the dynamic token is considered invalid;

[0119] If the decryption is successful, the decrypted information is obtained. According to the exp (expiration time) field in the decrypted information, it is determined whether the dynamic token has expired. If it has expired, the dynamic token is considered invalid; wherein the decrypted information includes the user ID field and the expiration time field;

[0120] If it has not expired, determine whether the user ID field in the decrypted information is empty. If it is empty, the dynamic token is deemed invalid. Otherwise, the dynamic token is deemed valid.

[0121] 3) If the JWT Token exists and is valid, the network development platform sends the page corresponding to the web project URL to the user.

[0122] 4) If the JWT Token is invalid or does not exist, obtain the initial URL of the collaborative office software according to the collaborative office tool documentation, replace the initial callback address, initial project application number and initial collaborative office tool number in the initial URL of the collaborative office software with the project callback address, project application number and collaborative office tool number in the configuration file, generate the collaborative office tool login QR code display URL, and send it to the user end to display the login QR code.

[0123] Take WeChat for Enterprise as an example:

[0124] Use the AppId, AgentId and REDIRECT_URI in the configuration file to replace the AppId, AgentId and REDIRECT_URI in the following URL;

[0125] https: / / login.work.weixin.qq.com / wwlogin / sso / login? login_type=CorpApp&app id=AppId&agentid=AgentId&redirect_uri=REDIRECT_URI&state=STATE.

[0126] Return the above QR code URL to the user through Openresty and display the QR code;

[0127] Users scan the QR code through mobile collaborative office tools;

[0128] After scanning the code, the page jumps to the project callback address;

[0129] Lua gets the code returned by the collaborative office tool, and calls the collaborative office backend application programming interface (API) through the code to obtain the unique user ID;

[0130] Lua creates a JWT Token using the user ID and the Secret in the configuration file;

[0131] Lua injects the JWT Token into the Cookie file and sends the page corresponding to the web project URL to the user for viewing;

[0132] The user continues to browse the web project page.

[0133] This embodiment implements OAuth authentication based on Openresty and Lua, abandons the traditional solution of implementing it through the front-end and back-end, avoids code intrusion, and greatly improves compatibility.

[0134] This embodiment supports mainstream collaboration tools, such as WeChat for Enterprise, Feishu, DingTalk, etc., and provides development specifications for quick connection with other collaboration tools.

[0135] The pluggable authentication module of this embodiment is a standardized pluggable authentication module, which can achieve rapid connection and offline.

[0136] Embodiment 2

[0137] This embodiment provides a user login authentication system for collaborative office tools, including a user terminal, a network development platform, and a collaborative office tool; wherein:

[0138] The user terminal receives the web project URL logged in by the user;

[0139] The web development platform receives the user's Cookie file and web project URL;

[0140] The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid;

[0141] When there is a user dynamic token and the dynamic token is valid, the network development platform sends a project page corresponding to the web project website to the user terminal;

[0142] Otherwise, generate a login QR code for the collaborative office tool and send it to the user end so that the user can scan the code to log in and jump to the project callback address;

[0143] The network development platform receives the collaborative office tool return code in the project callback address, and uses the collaborative office tool return code to obtain the user ID;

[0144] The network development platform creates and stores a dynamic token using the user ID, and sends a project page corresponding to the web project website to the user terminal based on the stored dynamic token.

[0145] The examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiment 1. It should be noted that the above modules as part of the system can be executed in a computer system such as a set of computer executable instructions.

[0146] The description of each embodiment in the above embodiments has different emphases. For parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0147] The proposed system can be implemented in other ways. For example, the system embodiment described above is only illustrative, and the division of the modules is only a logical function division. In actual implementation, there may be other division methods, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed.

[0148] Embodiment 3

[0149] This embodiment provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps in the user login authentication method for a collaborative office tool as described in the first embodiment above are implemented.

[0150] Embodiment 4

[0151] This embodiment provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the steps in the user login authentication method for a collaborative office tool as described in the first embodiment above are implemented.

[0152] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0153] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes 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 a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0154] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0155] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0156] A person skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0157] Although the above describes the specific implementation mode of the present invention in conjunction with the accompanying drawings, it is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art on the basis of the technical solution of the present invention without creative work are still within the scope of protection of the present invention.

Claims

1. A user login authentication method for a collaborative office tool, characterized in that: include: The web development platform receives the user's Cookie file and web project URL; The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid; When there is a user dynamic token and the dynamic token is valid, the network development platform sends a project page corresponding to the web project website to the user terminal; Otherwise, generate a login QR code for the collaborative office tool and send it to the user end so that the user can scan the code to log in and jump to the project callback address; The network development platform receives the collaborative office tool return code in the project callback address, and uses the collaborative office tool return code to obtain the user ID; The network development platform creates and stores a dynamic token using the user ID, and sends a project page corresponding to the web project URL to the user terminal based on the stored dynamic token.

2. A user login authentication method for a collaborative office tool as claimed in claim 1, characterized in that: The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid, specifically: If the dynamic token does not exist in the cookie file, the dynamic token is considered invalid; If there is a dynamic token in the cookie, the dynamic token will be decrypted. If the decryption fails, the dynamic token will be considered invalid. If the decryption is successful, the decrypted information is obtained, wherein the decrypted information includes a user ID field and an expiration time field; According to the expiration time field in the decrypted information, determine whether the dynamic token has expired. If it has expired, the dynamic token is considered invalid; If it has not expired, determine whether the user ID field in the decrypted information is empty. If it is empty, the dynamic token is deemed invalid. Otherwise, the dynamic token is deemed valid.

3. A user login authentication method for a collaborative office tool as claimed in claim 1, characterized in that: The generating of the collaborative office tool login QR code and sending it to the user terminal so that the user can scan the code to log in is specifically as follows: Get the initial URL of the collaborative office software; The project callback address, project application number and collaborative office tool number in the configuration file are used to replace the initial callback address, initial project application number and initial collaborative office tool number in the initial URL of the collaborative office software, and a login QR code display URL of the collaborative office tool is generated; The network development platform sends the login QR code display website of the collaborative office tool to the user terminal to display the login QR code.

4. A user login authentication method for a collaborative office tool as claimed in claim 1, characterized in that: The method of obtaining the user ID by using the return code of the collaborative office tool is as follows: Calling the office tool background application programming interface through the collaborative office tool return code; Get the user ID according to the office tool background application programming interface.

5. A user login authentication method for collaborative office tools as claimed in claim 4, characterized in that: Before being called, the collaborative office tool is configured, specifically: Create a project application entry corresponding to the web project in the background of the collaborative office tool; Based on the created project application entry, obtain project application information; Set corresponding login methods based on different collaborative office tools; Set the project callback address according to the web project URL; Set the key and validity period of the token and generate token information; Generate a configuration file based on the project application information, project callback address, login method, and token information.

6. A user login authentication method for collaborative office tools as claimed in claim 5, characterized in that: The project application information includes organization ID, application key, and application ID; The organization ID is the number of the collaborative office tool; Application ID is the ID of the created project application entry; The application key is an interface access key randomly generated by the collaborative office tool when the project application portal is created.

7. A user login authentication method for collaborative office tools as claimed in claim 5, characterized in that: The token information includes a token key and a token validity period.

8. A user login authentication system for collaborative office tools, characterized in that: Including user end, network development platform and collaborative office tools; among them, The user terminal receives the web project URL logged in by the user; The web development platform receives the user's Cookie file and web project URL; The network development platform determines whether there is a dynamic token in the cookie file and whether the dynamic token is valid; When there is a user dynamic token and the dynamic token is valid, the network development platform sends a project page corresponding to the web project website to the user terminal; Otherwise, generate a login QR code for the collaborative office tool and send it to the user end so that the user can scan the code to log in and jump to the project callback address; The network development platform receives the collaborative office tool return code in the project callback address, and uses the collaborative office tool return code to obtain the user ID; The network development platform creates and stores a dynamic token using the user ID, and sends a project page corresponding to the web project URL to the user terminal based on the stored dynamic token.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps in the user login authentication method for a collaborative office tool as described in any one of claims 1 to 7 are implemented.

10. 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 program, the steps of the user login authentication method for a collaborative office tool as described in any one of claims 1-7 are implemented.

Images