Automatic authentication method and device of subsystem, equipment and storage medium

Abstract

The embodiment of the invention provides an automatic authentication method and device of a subsystem, equipment and a storage medium, and the method comprises the steps: responding to a first operation of a user, popping up a login page window of the subsystem on a current page, the current page being a page displayed after the user logs in a main system according to authentication information; in response to a second operation of the user, obtaining port information input by the user on a login page window of the subsystem, and obtaining authentication information of the current page; and performing automatic authentication login of a target subsystem based on the port information and the authentication information of the current page, wherein the target subsystem is a subsystem corresponding to the port information. According to the embodiment of the invention, when the user wants to log in the subsystem, the authentication information of the main system can be actively acquired and used for automatic authentication login of the subsystem, cross-domain sharing of the authentication information between the main system and the subsystem is realized, errors caused by manual copying are avoided, and the development efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a method and device for automatically authenticating a subsystem, an apparatus and a storage medium. BACKGROUND

[0002] As the front end of a system is increasingly large and complex, micro-frontend technology is used in development to split the system by function modules, different functions are used as independent systems, and these systems are integrated in the main system. After successful login authentication in the main system, the user can enter each subsystem by clicking the corresponding subsystem portal. During system development, at least two systems need to be started, i.e., two local servers, the main system server and the subsystem server. The main system has a login interface, and the user can log in by inputting the account and password. The subsystem does not have a login page. Due to the cross-domain problem between the two servers, the authentication information of the main system cannot be directly shared in the subsystem. At this time, the user needs to open the console in the browser, copy the authentication information from the main system, open the console of the subsystem, and paste the authentication information into the corresponding position to realize the login authentication of the subsystem. If there is other authentication information, the user needs to repeat the operation of copying all the authentication information from the main system to the subsystem. The repeated manual copying operation is prone to cause the problem of missing paste of the authentication information, resulting in authentication failure of the subsystem. SUMMARY

[0003] Therefore, the present application provides a method and device for automatically authenticating a subsystem, an apparatus and a storage medium to solve the problem that the authentication information of the main system cannot be directly shared in the subsystem due to the cross-domain problem between the two servers, and the user needs to manually operate.

[0004] In a first aspect, the present application provides a method for automatically authenticating a subsystem, comprising:

[0005] In response to a first operation of the user, a login page window of the subsystem is popped up on a current page, wherein the current page is a page displayed after the user logs in the main system according to the authentication information;

[0006] In response to a second operation of the user, port information input by the user on the login page window of the subsystem is obtained, and authentication information of the current page is obtained;

[0007] The target subsystem is automatically authenticated and logged in based on the port information and the authentication information of the current page, wherein the target subsystem is a subsystem corresponding to the port information.

[0008] In a possible implementation, the obtaining of the port information input by the user on the login page window of the subsystem comprises:

[0009] The port information entered by the user on the login page window of the subsystem is obtained based on the pop-up database file.

[0010] Send the port information to the background script file.

[0011] In one possible implementation, obtaining the authentication information of the current page includes:

[0012] After receiving the port information, the background script file sends instruction information to the content script file of the webpage;

[0013] After receiving the instruction information, the content script file obtains the authentication information of the current page according to the instruction information, and returns the obtained authentication information of the current page to the background script file.

[0014] In one possible implementation, the automatic authentication login of the target subsystem based on the port information and the authentication information of the current page includes:

[0015] After receiving the port information, the background script file opens the authentication page of the target subsystem based on the port information.

[0016] After receiving the authentication information from the current page, the background script file saves the authentication information from the current page to the authentication page of the target subsystem for automatic authentication login of the target subsystem.

[0017] In one possible implementation, the method further includes:

[0018] After receiving the authentication information from the current page, the background script file also saves the authentication information of the current page to local data.

[0019] In one possible implementation, the response to the user's first action includes:

[0020] In response to a user clicking the plugin icon used for logging into the subsystem, the plugin icon is set in the browser's navigation bar.

[0021] In one possible implementation, the response to the user's second operation includes:

[0022] In response to the user clicking "Login" on the login page window of the subsystem.

[0023] In one possible implementation, sending the port information to the background script file includes:

[0024] The port information is sent to the background script file via postMessage.

[0025] In one possible implementation, after receiving the port information, the background script file sends instruction information to the webpage's content script file, including:

[0026] After receiving the port information via onMessage, the background script file sends instruction information to the content script file of the webpage via postMessage;

[0027] After receiving the instruction information, the content script file obtains the authentication information of the current page according to the instruction information, and returns the obtained authentication information of the current page to the background script file, including:

[0028] After receiving the instruction information via onMessage, the content script file obtains the authentication information of the current page based on the instruction information, and returns the obtained authentication information of the current page to the backend script file via postMessage.

[0029] Secondly, embodiments of this application provide an automatic authentication device for a subsystem, comprising:

[0030] A pop-up unit is used to respond to the user's first operation and pop up the login page window of the subsystem on the current page, which is the page displayed after the user logs into the main system according to the authentication information;

[0031] The acquisition unit is used to respond to the user's second operation by acquiring the port information entered by the user on the login page window of the subsystem, and acquiring the authentication information of the current page.

[0032] An automatic authentication login unit is used to perform automatic authentication login for a target subsystem based on the port information and the authentication information of the current page, wherein the target subsystem is the subsystem corresponding to the port information.

[0033] Thirdly, embodiments of this application provide an electronic device, including:

[0034] processor;

[0035] Memory;

[0036] The memory stores a computer program that, when executed, causes the electronic device to perform the method described in any of the first aspects.

[0037] Fourthly, embodiments of this application provide a computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the method described in any of the first aspects.

[0038] Compared with the prior art, the embodiments of this application can actively obtain the authentication information of the main system when a user wants to log in to the subsystem, and use it for automatic authentication login of the subsystem. This realizes cross-domain sharing of authentication information between the main system and the subsystem, avoids errors caused by manual copying, and improves development efficiency. Attached Figure Description

[0039] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 A flowchart illustrating an automatic authentication method for a subsystem provided in an embodiment of this application;

[0041] Figure 2 A schematic diagram illustrating the display of the main system page during browser login, provided as an embodiment of this application;

[0042] Figure 3 A schematic diagram showing the display of a login page window of a subsystem provided in an embodiment of this application;

[0043] Figure 4 A flowchart illustrating an automatic authentication method for another subsystem provided in this application embodiment;

[0044] Figure 5 A schematic diagram illustrating the display of a subsystem page during browser login, provided in an embodiment of this application.

[0045] Figure 6 A schematic diagram of the structure of an automatic authentication device for a subsystem provided in an embodiment of this application;

[0046] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0047] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0048] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0049] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0050] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0051] As the system front-end grows larger and more complex, micro-frontend technology is used during development to break down the system into functional modules. Different functions exist as independent systems, which are then integrated into a main system. After successful login authentication in the main system, users can access the corresponding subsystem by clicking its entry point. During system development, at least two systems need to be started, i.e., two local servers: a main system server and a subsystem server. The main system has a login interface where users can log in by entering their username and password. Subsystems do not have login pages. However, due to cross-domain issues between the two servers, authentication information from the main system cannot be directly shared to the subsystems. Therefore, it is necessary to open the console in the browser (F12), copy the authentication information from the main system, then open the subsystem's console (F12) and paste the authentication information to the corresponding location to achieve login authentication in the subsystem. If there is other authentication information, this process needs to be repeated, copying all authentication information from the main system to the subsystem. This leads to the following problems during system development:

[0052] 1. Each time a subsystem is developed, the main system needs to be opened, and then the F12 console of each subsystem needs to be opened to copy the authentication information from the main system to the subsystem. This process needs to be repeated multiple times when developing and maintaining multiple subsystems. The above operation also needs to be repeated when the authentication information of the main system expires.

[0053] 2. Manual copying and pasting is required each time, and due to the large amount of authentication information, omissions often occur, leading to subsystem authentication failures.

[0054] To address the aforementioned issues, this application proposes an automatic authentication method, apparatus, device, and storage medium for a subsystem. In embodiments of this application, when a user wants to log in to the subsystem, the authentication information from the main system can be actively obtained and used for automatic authentication login in the subsystem. This achieves cross-domain sharing of authentication information between the main system and the subsystem, avoiding errors caused by manual copying and improving development efficiency. The following description is in conjunction with the accompanying drawings.

[0055] See Figure 1This is a flowchart illustrating an automatic authentication method for a subsystem provided in an embodiment of this application. Figure 1 As shown, the automatic authentication method of this subsystem includes:

[0056] S101: In response to the user's first action, pop up the login page window of the subsystem on the current page, where the current page is the page displayed after the user logs into the main system based on the authentication information.

[0057] S102: In response to the user's second operation, obtain the port information entered by the user on the login page window of the subsystem, and obtain the authentication information of the current page;

[0058] S103: Perform automatic authentication login for the target subsystem based on port information and authentication information of the current page, where the target subsystem is the subsystem corresponding to the port information.

[0059] This application embodiment can pop up a login page window for the subsystem on the main system's page, obtain the authentication information of the current page (i.e., the main system), and then automatically authenticate and log in to the target subsystem based on the port information of the target subsystem entered by the user in the login page window and the authentication information of the main system. Through this method, this application embodiment can automatically synchronize authentication information under different systems, so that during system development, users only need to log in to the main system and then fill in the port information of the target subsystem to automatically import the authentication information from the main system into the subsystem, thus achieving automatic authentication and login for the subsystem.

[0060] In practical applications, there are various ways to log in to a subsystem from the main system. For example, you can set up a login entry for the subsystem on the main system page, or set up a plugin icon for logging into the subsystem on the browser logged in from the main system. Using a plugin approach to combine the login of the subsystem with the main system makes it easier to update, modify and maintain the plugin content in the future. Moreover, the plugin approach can be based on the Chrome browser to develop plugins, thereby achieving cross-system sharing of local data through the browser's underlying functions. It is easy to develop and has wide applicability.

[0061] Specifically, the plugin development process includes: creating an `auto-auth` directory file, which is the directory file for automatic authentication by the subsystem; and within the `auto-auth` directory file, creating a background script file (`background.js`), a content script file (`contentScript.js`), a configuration file (`manifest.json`), a popup page file (`popup.html`), and a popup database file (`popup.js`), and writing the content of each file. The background script file is a script file that runs continuously in the background and is the communication center of the entire plugin, mainly responsible for event listening and message processing; the content script file is a script file automatically injected into each page by the browser plugin, which can access page elements and call browser APIs; the configuration file is the plugin's configuration file, mainly used to configure the plugin icon, plugin popup page, plugin permission requirements, entry point, etc. Here, the V3 version configuration file can be used to add the plugin's configuration list; the popup page file usually corresponds to the window content that pops up when the browser operation button is pressed, here corresponding to the subsystem's login page window displayed on the main system page after clicking the plugin icon; the popup database file is used to refresh the content of the popup page and to retrieve the information entered by the user on the popup page.

[0062] After completing the writing of all the documents in this application, you can open the browser extension, click to load the unzipped extension, and then select the auto-auth directory file to import. The plugin icon for subsystem login will then appear in the browser's navigation bar. Users can achieve automatic authentication login for the subsystem by clicking the plugin icon.

[0063] The following explains the process of users automatically authenticating and logging into the subsystem by clicking the plugin icon.

[0064] In practice, after logging into the main system, the first action a user can take is from the main system page, which is then used as the current page. The user can then click the plugin icon for logging into the subsystem on the browser's navigation bar, such as... Figure 2 As shown, the icon corresponding to the cursor is the plugin icon used to log in to the subsystem. In response to the user's first action, this embodiment of the application pops up the subsystem's login page window on the main system page, as shown... Figure 3 As shown. Specifically, the content displayed on the subsystem's login page window may include the port number, i.e., the port information of the target subsystem that the user needs to enter, and a login button.

[0065] In specific implementation, after a user enters the port number of the subsystem to be logged into on the subsystem's login page window, a second operation can be performed. This second operation can be clicking the login button on the subsystem's login page window. In response to the user's second operation, this embodiment obtains the port information entered by the user on the subsystem's login page window and the authentication information of the current page. Specifically, this embodiment can obtain the port information entered by the user on the subsystem's login page window based on a pop-up database file, obtain the authentication information of the current page based on a content script file, and after obtaining the port information and the authentication information of the current page, implement automatic authentication login of the subsystem based on a background script file. The data flow between the pop-up database file, the content script file, and the background script file is as follows: Figure 4 As shown.

[0066] See Figure 4 This is a flowchart illustrating an automatic authentication method for another subsystem provided in an embodiment of this application. Figure 4 As shown, the specific steps of the automatic authentication method of this subsystem include:

[0067] S401: Obtain the port information entered by the user on the login page window of the subsystem through the pop-up database file.

[0068] In the specific implementation, when the user clicks the login button, the pop-up database file is triggered to refresh the login page window of the subsystem, and during the refresh process, the port information entered by the user on the login page window of the subsystem is obtained.

[0069] S402: The pop-up database file sends the port information entered by the user on the login page window of the subsystem to the background script file.

[0070] In the actual implementation, the pop-up database file, acting as the information sender, can send the port information entered by the user on the login page window of the subsystem to the background script file via postMessage.

[0071] PostMessage, as a method of message passing, allows messages to be sent between open browser windows or tabs without having to bind them to the same domain or port.

[0072] S403: The background script file sends instruction information to the content script file of the webpage.

[0073] In the actual implementation, the background script file, acting as the information receiver, can receive port information via `onMessage`. After confirming that the received information is indeed port information, it acts as the information sender, sending instruction information to the webpage's content script file via `postMessage`.

[0074] onMessage is the message receiving method corresponding to postMessage, used for receiving messages between open browser windows or tabs.

[0075] S404: The content script file obtains the authentication information of the current page based on the instruction information.

[0076] In the actual implementation, the content script files injected into each page act as message receivers. They can receive instruction information sent by the backend script files through onMessage and obtain the authentication information of the current page, i.e., the main system, based on the instruction information. At this time, the authentication information of the main system is stored in the browser as local data.

[0077] It should be noted that, in this embodiment of the application, local data refers to data stored by the business system on the browser side, such as localStorage, sessionStorage, and Cookie data.

[0078] S405: The background script file opens the authentication page of the target subsystem based on the port information.

[0079] In the actual implementation, after the background script confirms that the received information is port information, it opens the authentication page of the target subsystem based on the received port information. Specifically, the background script can create a new tab using tabs.create and the received port information; this tab is the authentication page of the target subsystem.

[0080] It should be noted that in the embodiments of this application, S403 and S405 can occur simultaneously or sequentially, and the embodiments of this application do not make specific requirements in this regard.

[0081] S406: The content script file returns the authentication information of the current page obtained to the backend script file.

[0082] In practice, after the content script file obtains the authentication information of the current page, it can return the obtained authentication information of the current page to the backend script file through postMessage.

[0083] S407: The background script file saves the authentication information of the current page to the authentication page of the target subsystem for automatic authentication login of the target subsystem.

[0084] In the specific implementation, the backend script file can receive the authentication information of the current page sent by the content script file via `onMessage`, and save the authentication information of the current page to the authentication page of the target subsystem to achieve automatic synchronization of authentication information. After receiving the authentication information, the authentication page of the target subsystem performs automatic authentication and login based on the authentication information. The logged-in subsystem page is as follows: Figure 5 As shown.

[0085] Meanwhile, the background script file also saves the authentication information received from the current page to local data.

[0086] Understandable Figure 4 The steps listed are all performed in the browser background after the user clicks login. For the user, clicking login directly takes them to... Figure 5 The target subsystem shown.

[0087] Unlike the method of manually copying authentication information from the main system and pasting it into the subsystem for login in multi-system development, this application embodiment provides a plugin for subsystem login. This plugin uses Chrome's postMessage and onMessage functions to forward and receive messages multiple times, thereby achieving local data sharing across systems. This allows this application embodiment to automatically synchronize data across different systems. During system development, users only need to log in to the main system, click the plugin, fill in the subsystem port number, and click login to automatically open the subsystem page and automatically import the main system authentication information into the subsystem for login. This improves development efficiency and avoids errors that occur with manual copying.

[0088] It should be noted that, Figure 2 , Figure 3 and Figure 5 The content displayed on the page is merely an illustrative example and is not intended to limit the scope of protection of this application.

[0089] Corresponding to the above embodiments, this application also provides an automatic authentication device for a subsystem.

[0090] See Figure 6 This is a schematic diagram of the structure of an automatic authentication device for a subsystem provided in an embodiment of this application. Figure 6As shown, the automatic authentication device 600 includes: a pop-up unit 601, used to pop up a login page window of a subsystem on the current page in response to a first user operation, wherein the current page is the page displayed after the user logs into the main system based on authentication information; an acquisition unit 602, used to acquire the port information entered by the user on the login page window of the subsystem and the authentication information of the current page in response to a second user operation; and an automatic authentication login unit 603, used to perform automatic authentication login of a target subsystem based on the port information and the authentication information of the current page, wherein the target subsystem is the subsystem corresponding to the port information.

[0091] For details of the embodiments of this application, please refer to the description of the above method embodiments. For the sake of brevity, it will not be repeated here.

[0092] Corresponding to the above embodiments, this application also provides an electronic device.

[0093] See Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 As shown, the electronic device 700 may include a processor 701, a memory 702, and a communication unit 703. These components communicate via one or more buses. Those skilled in the art will understand that the electronic device structure shown in the figures does not constitute a limitation on the embodiments of this application. It may be a bus topology or a star topology, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0094] The communication unit 703 is used to establish a communication channel, thereby enabling the electronic device to communicate with other devices.

[0095] The processor 701, serving as the control center of the electronic device, connects various parts of the image forming application compliance detection device via various interfaces and lines. It executes software programs and / or modules stored in the memory 702, and calls data stored in the memory, to perform various functions of the electronic device and / or process data. The processor may be composed of integrated circuits (ICs), such as a single packaged IC or multiple packaged ICs with the same or different functions connected together. For example, the processor 701 may consist only of a central processing unit (CPU). In this embodiment, the CPU may have a single processing core or include multiple processing cores.

[0096] Memory 702 is used to store the execution instructions of processor 701. Memory 702 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0097] When the execution instructions in memory 702 are executed by processor 701, the electronic device 700 is able to perform some or all of the steps in the above method embodiments.

[0098] In a specific implementation, this application embodiment also provides a computer storage medium, wherein the computer storage medium may store a program, and when the program is executed, it may include some or all of the steps of the automatic authentication method of the subsystem provided in this application embodiment. The storage medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0099] In a specific implementation, this application also provides a computer program product, wherein the computer program product includes executable instructions, which, when executed on a computer, cause the computer to perform some or all of the steps of the automatic authentication method of the subsystem provided in this application.

[0100] Those skilled in the art will clearly understand that the techniques in the embodiments of this application can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of this application, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application or some parts of the embodiments.

[0101] The same or similar parts between the various embodiments in this specification can be referred to mutually. In particular, the device embodiments and terminal embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the description in the method embodiments.

Claims

1. An automatic authentication method for a subsystem, characterized in that, include: In response to the user's first action, the login page window of the subsystem pops up on the current page, which is the page displayed after the user logs into the main system based on the authentication information; In response to the user's second operation, the system obtains the port information entered by the user on the login page window of the subsystem, and obtains the authentication information of the current page. Automatic authentication login for the target subsystem is performed based on the port information and the authentication information of the current page. The target subsystem is the subsystem corresponding to the port information.

2. The automatic authentication method according to claim 1, characterized in that, The step of obtaining the port information entered by the user on the login page window of the subsystem includes: The port information entered by the user on the login page window of the subsystem is obtained based on the pop-up database file. Send the port information to the background script file.

3. The automatic authentication method according to claim 2, characterized in that, The step of obtaining the authentication information of the current page includes: After receiving the port information, the background script file sends instruction information to the content script file of the webpage; After receiving the instruction information, the content script file obtains the authentication information of the current page according to the instruction information, and returns the obtained authentication information of the current page to the background script file.

4. The automatic authentication method according to claim 3, characterized in that, The automatic authentication login of the target subsystem based on the port information and the authentication information of the current page includes: After receiving the port information, the background script file opens the authentication page of the target subsystem based on the port information. After receiving the authentication information from the current page, the background script file saves the authentication information from the current page to the authentication page of the target subsystem for automatic authentication login of the target subsystem.

5. The automatic authentication method according to claim 4, characterized in that, The method further includes: After receiving the authentication information from the current page, the background script file also saves the authentication information of the current page to local data.

6. The automatic authentication method according to claim 1, characterized in that, The response to the user's first action includes: In response to a user clicking the plugin icon used for logging into the subsystem, the plugin icon is set in the browser's navigation bar.

7. The automatic authentication method according to claim 1, characterized in that, The second action in response to the user includes: In response to the user clicking "Login" on the login page window of the subsystem.

8. The automatic authentication method according to claim 3, characterized in that, Sending the port information to the background script file includes: The port information is sent to the background script file via postMessage; After receiving the port information, the background script file sends instruction information to the webpage's content script file, including: After receiving the port information via onMessage, the background script file sends instruction information to the content script file of the webpage via postMessage; After receiving the instruction information, the content script file obtains the authentication information of the current page according to the instruction information, and returns the obtained authentication information of the current page to the background script file, including: After receiving the instruction information via onMessage, the content script file obtains the authentication information of the current page based on the instruction information, and returns the obtained authentication information of the current page to the backend script file via postMessage.

9. An automatic authentication device for a subsystem, characterized in that, include: A pop-up unit is used to respond to the user's first operation and pop up the login page window of the subsystem on the current page, which is the page displayed after the user logs into the main system according to the authentication information; The acquisition unit is used to respond to the user's second operation by acquiring the port information entered by the user on the login page window of the subsystem, and acquiring the authentication information of the current page. An automatic authentication login unit is used to perform automatic authentication login for a target subsystem based on the port information and the authentication information of the current page, wherein the target subsystem is the subsystem corresponding to the port information.

10. An electronic device, characterized in that, include: processor; Memory; The memory stores a computer program that, when executed, causes the electronic device to perform the method described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1-8.

Images