Authorized login processing method and device, equipment and storage medium

Abstract

The invention discloses an authorized login processing method and device, equipment and a storage medium, and the method comprises the steps: a browser sends an authorization request to a third-party server according to a unified jump domain name, and the third-party server sends a first redirection response comprising an authorization parameter and the unified jump domain name to the browser based on the authorization request; the browser is redirected to a page of the unified jump domain name according to the unified jump domain name in the first redirection response, and the first server of the unified jump domain name analyzes a webpage address of the page to obtain an authorization parameter; the browser sends a redirection request to the first server according to the target domain name, and the first server sends a second redirection response containing the authorization parameter and the target domain name to the browser according to the redirection request; the browser is redirected to a page of the target domain name according to the target domain name in the second redirection response, a second server of the target domain name analyzes a webpage address of the page to obtain an authorization parameter, and the second server confirms that the browser logs in the target domain name according to the authorization parameter.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an authorized login processing method, device, equipment and storage medium. Background Art

[0002] Third-party authorized login allows users to log in to another website or application through an account on a third-party server without having to re-register an account and enter a password on the website or application. Through third-party authorized login, users do not need to register multiple accounts and remember multiple passwords on multiple websites or applications. They can log in using their existing third-party server accounts, which effectively improves the user experience. The account password will not be directly exposed to the corresponding login website or application, but access resources through authorization tokens, reducing the risk of password leakage and ensuring the security of the account.

[0003] In the prior art, for security reasons, third-party authorized login has strict whitelist restrictions on redirected domain names. Every time a new domain name is added for authorized login request, the new domain name must be manually configured into the whitelist in the background of the third-party server. This process is cumbersome and easy to forget, resulting in the new domain name being unable to use the third-party authorized login function normally. Summary of the invention

[0004] The present application provides an authorized login processing method, apparatus, device and storage medium, so as to redirect a browser to a unified jump domain name through a third-party server, and the server of the unified jump domain name redirects the browser to a target domain name, and the server of the target domain name confirms the browser login to the target domain name through the authorization parameters of the third-party server, so as to achieve that when the target domain name is not in the white list of the third-party server, the login authorization of the third-party server can also be obtained through the unified jump domain name, and the problem in the prior art that the domain name requesting authorized login needs to be configured into the white list in the background of the third-party server is solved, the configuration process of the third-party authorized login is simplified, and the configuration efficiency of the third-party authorized login is improved.

[0005] In a first aspect, the present application provides an authorized login processing method, which is applied to a browser, comprising:

[0006] Determine the target domain name to be logged in and the third-party server authorized to log in according to the detected authorized login operation, and use the preset unified jump domain name as the first redirection address;

[0007] Sending an authorization request to the third-party server according to the first redirection address, so that the third-party server generates an authorization parameter based on the authorization request, generates a first redirection response according to the authorization parameter and the first redirection address, and sends the first redirection response to the browser;

[0008] redirecting to the first page of the unified jump domain name according to the first redirection address in the first redirection response, so that the first server of the unified jump domain name resolves the webpage address of the first page to obtain the authorization parameter;

[0009] Using the target domain name as a second redirection address, sending a redirection request to the first server of the unified jump domain name according to the second redirection address, so that the first server generates a second redirection response according to the authorization parameter and the second redirection address in the redirection request, and sending the second redirection response to the browser;

[0010] Redirect to the second page of the target domain name according to the second redirect address in the second redirect response, so that the second server of the second target domain name parses the web address of the second page to obtain the authorization parameters, and confirms that the browser logs in to the target domain name according to the authorization parameters.

[0011] In a second aspect, the present application provides an authorized login processing device, which is applied to a browser, comprising:

[0012] A login operation response module is configured to determine a target domain name to be logged in and a third-party server authorized to log in according to the detected authorized login operation, and use a preset unified jump domain name as a first redirection address;

[0013] an authorization request sending module, configured to send an authorization request to the third-party server according to the first redirection address, so that the third-party server generates an authorization parameter based on the authorization request, generates a first redirection response according to the authorization parameter and the first redirection address, and sends the first redirection response to the browser;

[0014] A first redirection module is configured to redirect to a first page of the unified jump domain name according to a first redirection address in the first redirection response, so that the first server of the unified jump domain name resolves the webpage address of the first page to obtain the authorization parameter;

[0015] a redirection request sending module, configured to use the target domain name as a second redirection address, and send a redirection request to the first server of the unified jump domain name according to the second redirection address, so that the first server generates a second redirection response according to the authorization parameter and the second redirection address in the redirection request, and sends the second redirection response to the browser;

[0016] The second redirection module is configured to redirect to the second page of the target domain name according to the second redirection address in the second redirection response, so that the second server of the second target domain name parses the web page address of the second page to obtain the authorization parameters, and confirms that the browser logs in to the target domain name according to the authorization parameters.

[0017] In a third aspect, the present application provides an authorization login processing device, including:

[0018] one or more processors;

[0019] A memory stores one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the authorized login processing method as described in the first aspect.

[0020] In a fourth aspect, the present application provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute the authorized login processing method as described in the first aspect.

[0021] In the present application, by sending an authorization request to a third-party server using a unified jump domain name as a redirection address, the third-party server appends the authorization parameter to the query parameter of the redirection address and redirects the browser to the unified jump domain name page, so that the server of the unified jump domain name resolves the web address of the unified jump domain name page to obtain the authorization parameter. The browser sends a redirection request to the server of the unified jump domain name using the target domain name as a redirection address, the server of the unified jump domain name appends the authorization parameter to the query parameter of the redirection address and redirects the browser to the target domain name page, so that the server of the target domain name resolves the web address of the target domain name page to obtain the authorization parameter, and the server of the target domain name confirms that the browser has successfully logged in to the target domain name based on the authorization parameter. Through the above technical means, it is achieved that when the target domain name is not in the whitelist of the third-party server, the login authorization of the third-party server can also be obtained through the unified jump domain name, which solves the problem in the prior art that the domain name for requesting authorization login needs to be configured to the whitelist in the background of the third-party server, simplifies the configuration process of third-party authorized login, and improves the configuration efficiency of third-party authorized login. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a flowchart of an authorized login processing method provided by an embodiment of the present application;

[0023] Figure 2 This is a first schematic diagram of a display interface of a browser provided in an embodiment of the present application;

[0024] Figure 3This is a flowchart of a browser sending an authorization request to a third-party server provided in an embodiment of the present application;

[0025] Figure 4 This is a flowchart of a third-party server generating authorization parameters based on an authorization request provided by an embodiment of the present application;

[0026] Figure 5 is a second schematic diagram of a display interface of a browser provided in an embodiment of the present application;

[0027] Figure 6 This is a flowchart of the first server obtaining authorization parameters provided by an embodiment of the present application;

[0028] Figure 7 This is a flow chart of the second server obtaining authorization parameters provided by an embodiment of the present application;

[0029] Figure 8 It is a structural diagram of an authorized login processing device provided in an embodiment of the present application;

[0030] Fig. 9 It is a structural diagram of an authorized login processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all the contents are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.

[0032] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0033] In the more common existing implementation methods, third-party authorized login has strict whitelist restrictions on redirected domain names. Every time a new domain name is added to request authorized login, the new domain name must be manually configured into the whitelist in the background of the third-party server. This process is cumbersome and easy to forget, resulting in the new domain name being unable to use the third-party authorized login function normally.

[0034] To solve the above problem, this embodiment provides an authorized login processing method, which redirects the browser to a unified jump domain name through a third-party server, and the server of the unified jump domain name redirects the browser to the target domain name. The server of the target domain name confirms the browser login to the target domain name through the authorization parameters of the third-party server. This achieves that when the target domain name is not in the whitelist of the third-party server, the login authorization of the third-party server can be obtained through the unified jump domain name, which simplifies the configuration process of third-party authorized login and improves the configuration efficiency of third-party authorized login.

[0035] The authorization login processing method provided in this embodiment can be executed by an authorization login processing device, which can be implemented by software and / or hardware, and can be composed of two or more physical entities or one physical entity. For example, the authorization login processing device can be a browser.

[0036] The authorized login processing device is installed with at least one type of operating system, wherein the operating system includes but is not limited to Android system, Linux system and Windows system. The authorized login processing device can install at least one application based on the operating system, and the application can be an application that comes with the operating system or an application downloaded from a third-party device or server. In this embodiment, the authorized login processing device has at least an application that can execute the authorized login processing method.

[0037] For ease of understanding, this embodiment is described by taking a browser as an example of a subject that executes the authorized login processing method.

[0038] Figure 1A flowchart of an authorized login processing method provided by an embodiment of the present application is given. Figure 1 , the authorization login processing method specifically includes:

[0039] S110: Determine the target domain name to be logged in and the third-party server authorized for login according to the detected authorized login operation, and use the preset unified jump domain name as the first redirection address.

[0040] The authorized login operation is an operation triggered by the user through the authorized login control, and the target domain name is the domain name that the user wants to log in through the account of the third-party server. Exemplarily, after the user opens the login page of the target domain name through the browser, the login page of the target domain name displays the authorized login control, and the user clicks the authorized login control to trigger the authorized login operation. After the browser detects the authorized login operation, it parses the webpage address of the page where the authorized login control is located to obtain the target domain name, and determines the third-party server that opens the right to log in the corresponding account to the target domain name according to the authorized login control.

[0041] Figure 2 is a first schematic diagram of a display interface of a browser provided in an embodiment of the present application. Figure 2 As shown, after the display interface 11 of the browser opens the login page of the target domain name, the display interface 11 displays a URL box 11, an account input box 12, a password input box 13, a login control 14, an authorized login control 15 of a third-party server A, an authorized login control 16 of a third-party server B, an authorized login control 17 of a third-party server C, and a remember account and password control 18. The URL box 11 displays the web address of the page opened by the display interface 11. When the user wants to log in to the target domain name based on the account and password registered in advance in the target domain name, the user can fill in the account in the account input box 12 and the password in the password input box 13, and then click the login control 14 to trigger the login operation. When the browser detects the login operation, it can generate a login request based on the account and password, and send the login request to the second server of the target domain name, so that the second server verifies the account and password, confirms that the browser has successfully logged in to the target domain name after the verification is passed, and provides the browser with the business functions after the login. When the user wants to log in the target domain name through the account of the third-party server, the user can click any one of the authorized login control 15 of the third-party server A, the authorized login control 16 of the third-party server B, and the authorized login control 17 of the third-party server C to log in the target domain name using the account of the third-party server A, the third-party server B, or the third-party server C. Assuming that the user clicks the authorized login control 15 of the third-party server A to trigger the authorized login operation, when the browser detects the authorized login operation, it can parse the webpage address in the URL box 11 to obtain the target domain name to be logged in, and determine that the third-party server corresponding to the authorized login is the third-party server A according to the authorized login operation.

[0042] After determining the target domain name and the third-party server, since the target domain name may not be in the whitelist of the third-party server, this embodiment proposes to use the preset unified jump domain name as the first redirection address, and the unified jump domain name is in the whitelist of the third-party server, so the third-party server can redirect the browser to the page of the unified jump domain name, so that the browser can parse the authorization parameters of the third-party server through the page of the unified jump domain name. Under the premise that the target domain name is not configured in the whitelist of the third-party server, the third-party server can also implement authorized login to the target domain name, thereby improving the flexibility of third-party authorized login. Among them, the first redirection address is the webpage address to which the browser redirects after the third-party browser is authorized.

[0043] In one embodiment, a unified jump domain name can be configured for all domain names, that is, when logging in to any domain name through third-party authorization, the unified jump domain name is used as the first redirection address, so that the browser obtains the authorization parameters of the third-party server through the unified jump domain name.

[0044] In another embodiment, for a target domain name that is already in the whitelist of a third-party server, the unified jump domain name may not be used as the first redirection address but the target domain name may be used as the first redirection address. The third-party server redirects the browser to the target domain name, and the browser obtains the authorization parameters of the third-party server through the target domain name. The browser does not need to redirect from the unified jump domain name to the target domain name, which is conducive to improving the efficiency of third-party authorized login. For a target domain name that is not in the whitelist of the third-party server, the unified jump domain name is used as the first redirection address, so that the browser obtains the authorization parameters of the third-party server through the unified jump domain name, and then redirects from the unified jump domain name to the target domain name. The specific implementation process is: according to the target domain name and the third-party server, determine whether the target domain name is in the whitelist of the third-party server; if the target domain name is not in the whitelist of the third-party server, use the preset unified jump domain name as the first redirection address; if the target domain name is in the whitelist of the third-party server, use the target domain name as the first redirection address. Exemplarily, the corresponding whitelist is obtained according to the third-party server, and the target domain name is compared with each domain name in the whitelist to determine whether the target domain name is in the whitelist of the third-party server. If the target domain name is not in the whitelist, the third-party server will not authorize the target domain name to log in to the corresponding account, so the unified jump domain name pre-configured in the whitelist of the third-party server can be used as the first redirection address to indirectly obtain the authorization parameters of the third-party server through the unified jump domain name. If the target domain name is in the whitelist, the third-party server will authorize the target domain name to log in to the corresponding account, so the target domain name can be used as the first redirection address to directly obtain the authorization parameters of the third-party server through the target domain name.

[0045] It should be noted that when the target domain name is used as the first redirection address, the process of the browser authorizing the target domain name to log in through the third-party server is the same as the existing third-party authorization login method (such as using OAuth 2.0 for login authorization), and this embodiment will not be repeated. This embodiment is intended to describe the process of third-party authorization login using the unified jump domain name as the first redirection address.

[0046] S120. Send an authorization request to the third-party server according to the first redirection address, so that the third-party server generates authorization parameters based on the authorization request, generates a first redirection response according to the authorization parameters and the first redirection address, and sends the first redirection response to the browser.

[0047] Among them, the authorization request is an instruction to request the third-party server to authorize the browser to use the account of the third-party server to log in to other domain names. The first redirection response is an instruction for the third-party server to reply to the browser in response to the authorization request, and the first redirection response can be used to redirect the browser to the first redirection address corresponding to the authorization request. Exemplarily, the browser generates an authorization request based on the first redirection address and the domain name of the third-party server, and sends the authorization request to the third-party server. The third-party server obtains the unified jump domain name based on the first redirection address carried in the authorization request, confirms that the unified jump domain name is in the corresponding configured whitelist, and then generates authorization parameters, adds the authorization parameters and the first redirection address to the response header of the first redirection response, and sends the first redirection response to the browser. The browser redirects to the unified jump domain name based on the first redirection response.

[0048] In this embodiment, Figure 3 1 is a flowchart of a browser sending an authorization request to a third-party server provided by an embodiment of the present application. Figure 3 As shown, the step of the browser sending an authorization request to the third-party server specifically includes S1201-S1203:

[0049] S1201. Obtain the authorization endpoint address, authorization response type, and access permission scope of the third-party server.

[0050] S1202: Append the authorization response type, access permission, and the first redirection address to the query parameters of the authorization endpoint address to construct an authorization request address.

[0051] S1203: Load the authorization request address to send an authorization request to the third-party server according to the authorization endpoint address, where the authorization request includes a query parameter of the authorization endpoint address.

[0052] Among them, the authorization endpoint address is the web address of the authorization login service of the third-party server; the authorization response type is used to specify the type of authorization parameters, and the authorization response type includes an authorization code and an access token. If the authorization response type is an authorization code, the third-party server generates an authorization code based on the authorization request, and if the authorization response type is an access token, the third-party server generates an access token based on the authorization request. The access permission scope is used to limit the scope of resources accessed by the authorization request. The authorization response type, access permission scope, and the first redirection address are added to the query parameters of the authorization endpoint address in the form of a string to construct the authorization request address. The browser can load the authorization request address to send an authorization request to the authorization login service of the third-party server according to the authorization endpoint address, so that the authorization login service can parse the authorization response type, access permission scope, and the first redirection address according to the query parameters corresponding to the authorization login address in the authorization request, and then generate the first redirection response of the authorization request according to the authorization response type, access permission scope, and the first redirection address.

[0053] Furthermore, Figure 4 FIG. 1 is a flowchart of a third-party server generating authorization parameters based on an authorization request provided by an embodiment of the present application. Figure 4 As shown, the step of generating authorization parameters based on the authorization request by the third-party server specifically includes S1204-S1205:

[0054] S1204: Send an authorization request to a third-party server according to the first redirection address, so that the third-party server performs a whitelist verification on the first redirection address in the authorization request, and after the verification is passed, send a third redirection response to the browser according to the webpage address of the authorization page.

[0055] Exemplarily, after the browser loads the authorization request address to send an authorization request to the third-party server, the third-party server parses the query parameters of the authorization login address of the authorization request to obtain the authorization response type, access permission scope, and the first redirection address. The third-party server compares the first redirection address with the domain name in the whitelist, and if the first redirection address exists in the whitelist, the third-party server adds the authorization page of the authorization login service to the response header of the third redirection response, and sends the third redirection response to the browser. The third redirection response is used to redirect the browser to the authorization page of the third-party server after receiving the authorization request.

[0056] S1205: redirect to the authorization page of the third-party server according to the web page address in the third redirection response, and send an authorization message to the third-party server in response to a click operation of the authorization control in the authorization page, so that the third-party server generates authorization parameters based on the authorization message.

[0057] For example, Figure 5is a second schematic diagram of the display interface of the browser provided in the embodiment of the present application. Figure 5 As shown, after the browser receives the third redirection response, the web address of the authorization page is obtained in the response header of the third redirection response, and the web address is loaded to redirect to the authorization page of the third-party server. At this time, the display interface 10 of the browser displays the authorization page of the third-party server. The authorization page displays the account of the user who previously logged into the third-party browser through the browser, as well as the authorization control 19 and the authorization rejection control 20. When the user clicks the authorization control 19, the browser responds to the click operation of the authorization control 19 and sends an authorization message to the third-party server. The third-party server confirms that the user uses the account of the third-party server to log in to other domain names based on the authorization message, and then generates authorization parameters according to the authorization response type and access permission range previously obtained through the authorization request. When the user clicks the authorization rejection control 20, the browser responds to the click operation of the authorization rejection control 20 and sends an authorization rejection message to the third-party server. The third-party server sends a response to the browser that the user refuses to authorize the login based on the authorization rejection message.

[0058] After generating the authorization parameters, the third-party server appends the authorization parameters to the query parameters of the first redirection address, adds the first redirection address to the response header of the first redirection response, and sends the first redirection response to the browser so that the browser is redirected to the page of the unified jump domain name based on the first redirection address in the first redirection response.

[0059] S130: redirect to the first page of the unified jump domain name according to the first redirect address in the first redirect response, so that the first server of the unified jump domain name resolves the webpage address of the first page to obtain authorization parameters.

[0060] Exemplarily, after receiving the first redirection response sent by the third-party server, the browser parses the first redirection address in the response header of the first redirection response, loads the first redirection address to redirect to the first page of the unified jump domain name. The first server of the unified jump domain name parses the query parameters of the webpage address of the first page to obtain the authorization parameters transmitted by the third-party server. Among them, the first page is the access page of the unified jump domain name, and the content of the first page can be designed according to actual needs, which is not specifically limited here.

[0061] In this embodiment, Figure 6 1 is a flow chart of the first server obtaining authorization parameters provided by the embodiment of the present application. Figure 6 As shown, the step of the first server acquiring the authorization parameter specifically includes S1301-S1302:

[0062] S1301. Obtain a first redirection address in a response header of a first redirection response, load the first redirection address to send a first access request to a first server with a unified jump domain name, so that the first server sends a first access response to the browser based on the first access request.

[0063] S1302: redirect to a first page of a unified jump domain name according to the first access response, so that the first server parses the query parameters of the webpage address of the first page to obtain the authorization parameters.

[0064] Exemplarily, after receiving the first redirection response sent by the third-party server, the browser obtains the first redirection address in the Location field of the response header of the first redirection response, loads the first redirection address to send a first access request (GET request) to the first server of the unified jump domain name. The first server sends a first access response to the browser based on the first access request, and the first access response is used to confirm that the browser jumps to the first page of the unified jump domain name. After receiving the first access response, the browser redirects to the first page of the unified jump domain name based on the first access response. At this time, the browser's display page displays the first page, and the user can see the web address of the first page in the browser's URL box. The first page is also the front-end page of the first server of the unified jump domain name. The first server can parse the query parameters of the web address of the first page, and extract the authorization parameters generated by the third-party server based on the authorization request.

[0065] S140. Use the target domain name as the second redirection address, and send a redirection request to the first server of the unified jump domain name according to the second redirection address, so that the first server generates a second redirection response according to the authorization parameters and the second redirection address in the redirection request, and sends the second redirection response to the browser.

[0066] Exemplarily, after the authorization parameter is transmitted to the first server of the unified jump domain name, the browser may send a redirect request to the first server to instruct the first server to redirect the browser to the second page of the target domain name through the redirect request, so that the second server of the target domain name obtains the authorization parameter by parsing the webpage address of the second page, and realizes the redirection transmission of the authorization parameter from the third-party server to the first server and then to the second server. When sending the redirect request, the second redirect address may be attached to the query parameter of the unified jump domain name, the redirect request address may be constructed, and the redirect request address may be loaded to send the redirect request to the first server according to the unified jump domain name. After receiving the redirect request, the first server attaches the authorization parameter to the query parameter of the second redirect address, adds the second redirect address to the response header of the second redirect response, and sends the second redirect response to the browser, so that the browser is redirected to the second page of the target domain name based on the second redirect response. Among them, the second redirect response is the instruction of the first server to reply to the browser in response to the redirect request, and the second redirect response can be used to redirect the browser to the second redirect address corresponding to the redirect request.

[0067] S150, redirecting to the second page of the target domain name according to the second redirection address in the second redirection response, so that the second server of the second target domain name resolves the web page address of the second page to obtain authorization parameters, and confirming that the browser logs in to the target domain name according to the authorization parameters.

[0068] Exemplarily, after receiving the second redirection response sent by the first server, the browser parses the second redirection address in the response header of the second redirection response, loads the second redirection address to redirect to the second page of the target domain name. The second server of the target domain name parses the query parameters of the webpage address of the second page to obtain the authorization parameters transmitted by the third-party server. The second page is the access page of the target domain name, which can be the main page of the target domain name.

[0069] In this embodiment, Figure 7 1 is a flow chart of the second server obtaining authorization parameters provided by the embodiment of the present application. Figure 7 As shown, the step of the second server acquiring the authorization parameter specifically includes S1501-S1502:

[0070] S1501. Obtain a second redirection address in a response header of a second redirection response, load the second redirection address to send a second access request to a second server of a target domain name, so that the second server sends a second access response to the browser based on the second access request.

[0071] S1502: Redirect to a second page of the target domain name according to the second access response, so that the second server parses the query parameters of the webpage address of the second page to obtain the authorization parameters.

[0072] Exemplarily, after receiving the second redirection response sent by the first server, the browser obtains the second redirection address in the Location field of the response header of the second redirection response, loads the second redirection address to send a second access request (GET request) to the second server of the target domain name. The second server sends a second access response to the browser based on the second access request, and the second access response is used to confirm that the browser jumps to the second page of the target domain name. After receiving the second access response, the browser redirects to the second page of the target domain name based on the second access response. At this time, the browser's display page shows the second page, and the user can see the web address of the second page in the browser's URL box. The second page is also the front-end page of the second server of the target domain name. The second server can parse the query parameters of the web address of the second page, and extract the authorization parameters generated by the third-party server based on the authorization request, thereby realizing the transmission of the authorization parameters to the first server and then to the second server.

[0073] It should be noted that in this embodiment, the display interface of the browser will first open the login page of the target domain name, then jump to the authorization page of the third-party server, then jump to the first page of the unified jump domain name, and finally jump to the second page of the target domain name. With multiple redirections of the browser, the authorization parameters generated by the third-party server based on the authorization request are transmitted to the first server and then to the second server.

[0074] After obtaining the authorization parameters, the second server can request the third-party server to send user information based on the authorization parameters, confirm the browser login target domain name based on the user information sent by the third-party server, and provide corresponding business functions to the browser. Among them, when the authorization parameter is an authorization code, the second server generates a token acquisition request based on the authorization code, and sends the token acquisition request to the authorization login service of the third-party server. The authorization login service verifies based on the authorization code in the token acquisition request, and sends an access token to the second server after the verification is passed. After the second server obtains the access token, it generates a user information acquisition request based on the access token, and sends the user information acquisition request to the resource service of the third-party server. The resource service verifies based on the access token in the user information acquisition request, and sends the corresponding user information to the second server after the verification is passed. The second server confirms the browser login target domain name based on the obtained user information.

[0075] In one embodiment, when the browser successfully logs in to the target domain name, the small text file (Cookie) of the target domain name can be saved, so that the target domain name can be directly logged in based on the small text file of the target domain name in the future, without obtaining the authorization of the third method server, thereby improving the login efficiency. The specific implementation process is that after the second server confirms that the browser logs in to the target domain name, a small text file is generated according to the identity authentication information in the user information, a login response is generated according to the small text file, and the login response is sent to the browser. The login response sent by the second server is received, the small text file is obtained in the login response, and the small text file is locally associated with the target domain name and saved; wherein the small text file contains the identity authentication information; in the case of receiving the login operation of logging in to the target domain name, a login request is generated according to the small text file locally associated with the target domain name and saved, and the login request is sent to the second server, so that the second server verifies the identity authentication information in the small text file based on the login request, and confirms that the browser logs in to the target domain name after the verification is passed. wherein, the login response is a response instruction that the second server informs the browser that it has successfully logged in to the target domain name after confirming that the browser has logged in to the target domain name, and the login response is an HTTP response. The identity authentication information includes information such as user ID, session ID and token, and the identity authentication information is used to verify the identity and status of the user. The browser obtains the small text file of the target domain name according to the response instruction, and associates the small text file with the target domain name and saves it locally. Figure 2 If the user selects the remember account and password control 18 when logging into the target domain name for the first time, the second server sends a login response containing a small text file to the browser. When the user reopens the login page of the target domain name, the browser obtains the corresponding small text file locally based on the target domain name, obtains the user ID in the small text file and automatically fills it into the account input box 12 of the login page. When the user clicks the login control 14 to trigger the login operation, the browser responds to the login operation to generate a login request based on the small text file, and sends the login request to the second server. The second server parses the small text file in the login request, verifies the user's identity and status based on the identity authentication information in the small text file, and confirms that the browser has logged in to the target domain name after the verification is passed.

[0076] It should be noted that the reason why the browser can save the small text file of the target domain name is that the browser redirects from the first page of the unified jump domain name back to the second page of the target domain name, so that the second server of the target domain name can send an HTTP response containing the small text file to the browser. Therefore, the browser redirects from the first page of the unified jump domain name to the second page of the target domain name, which not only ensures that the second server obtains the authorization parameters, but also ensures that the browser obtains the small text file of the target domain name.

[0077] In summary, the authorization login processing method provided by the embodiment of the present application, by sending an authorization request to a third-party server using a unified jump domain name as a redirection address, the third-party server appends the authorization parameter to the query parameter of the redirection address and redirects the browser to the unified jump domain name page, so that the server of the unified jump domain name resolves the web address of the unified jump domain name page to obtain the authorization parameter. The browser sends a redirection request to the server of the unified jump domain name using the target domain name as a redirection address, the server of the unified jump domain name appends the authorization parameter to the query parameter of the redirection address and redirects the browser to the target domain name page, so that the server of the target domain name resolves the web address of the target domain name page to obtain the authorization parameter, and the server of the target domain name confirms that the browser has successfully logged in to the target domain name based on the authorization parameter. Through the above technical means, it is achieved that when the target domain name is not in the white list of the third-party server, the login authorization of the third-party server can also be obtained through the unified jump domain name, which solves the problem in the prior art that the domain name for requesting authorization login needs to be configured to the white list in the background of the third-party server, simplifies the configuration process of third-party authorized login, and improves the configuration efficiency of third-party authorized login.

[0078] Based on the above embodiments, Figure 8 This is a schematic diagram of the structure of an authorized login processing device provided in an embodiment of the present application. Figure 8 The authorized login processing device provided in this embodiment specifically includes: a login operation response module 31, an authorization request sending module 32, a first redirection module 33, a redirection request sending module 34 and a second redirection module 35.

[0079] The login operation response module 31 is configured to determine the target domain name to be logged in and the third-party server authorized to log in according to the detected authorized login operation, and use the preset unified jump domain name as the first redirection address;

[0080] The authorization request sending module 32 is configured to send an authorization request to the third-party server according to the first redirection address, so that the third-party server generates an authorization parameter based on the authorization request, generates a first redirection response according to the authorization parameter and the first redirection address, and sends the first redirection response to the browser;

[0081] A first redirection module 33 is configured to redirect to a first page of a unified jump domain name according to a first redirection address in a first redirection response, so that a first server of the unified jump domain name resolves a webpage address of the first page to obtain an authorization parameter;

[0082] The redirection request sending module 34 is configured to use the target domain name as the second redirection address, and send a redirection request to the first server of the unified jump domain name according to the second redirection address, so that the first server generates a second redirection response according to the authorization parameter and the second redirection address in the redirection request, and sends the second redirection response to the browser;

[0083] The second redirection module 35 is configured to redirect to the second page of the target domain name according to the second redirection address in the second redirection response, so that the second server of the second target domain name parses the web page address of the second page to obtain authorization parameters, and confirms the browser login to the target domain name according to the authorization parameters.

[0084] Based on the above embodiment, the authorization request sending module 32 includes: a request information acquisition unit, configured to obtain the authorization endpoint address, authorization response type and access permission scope of the third-party server; a request address construction unit, configured to append the authorization response type, access permission scope and the first redirection address to the query parameters of the authorization endpoint address to construct the authorization request address; an authorization request sending unit, configured to load the authorization request address to send an authorization request to the third-party server according to the authorization endpoint address, and the authorization request includes the query parameters of the authorization endpoint address.

[0085] Based on the above embodiment, the authorization request sending module 32 includes: a first response sending unit, configured to send an authorization request to a third-party server according to a first redirection address, so that the third-party server performs a whitelist verification on the first redirection address in the authorization request, and sends a third redirection response to the browser according to the web page address of the authorization page after the verification is passed; a first response receiving unit, configured to redirect to the authorization page of the third-party server according to the web page address in the third redirection response, and send an authorization message to the third-party server in response to a click operation of the authorization control in the authorization page, so that the third-party server generates authorization parameters based on the authorization message.

[0086] On the basis of the above embodiment, the authorization parameter is attached to the query parameter of the first redirection address, and the first redirection address is added to the response header of the first redirection response; accordingly, the first redirection module 23 includes: a first request access unit, configured to obtain the first redirection address in the response header of the first redirection response, load the first redirection address to send a first access request to the first server of the unified jump domain name, so that the first server sends a first access response to the browser based on the first access request; the first redirection unit, configured to redirect to the first page of the unified jump domain name according to the first access response, so that the first server parses the query parameter of the web page address of the first page to obtain the authorization parameter.

[0087] Based on the above embodiment, the authorization parameter is attached to the query parameter of the second redirection address, and the second redirection address is added to the response header of the second redirection response; accordingly, the first redirection module 25 includes: a second request access unit, configured to obtain the second redirection address in the response header of the second redirection response, load the second redirection address to send a second access request to the second server of the target domain name, so that the second server sends a second access response to the browser based on the second access request; a second redirection unit, configured to redirect to the second page of the target domain name according to the second access response, so that the second server parses the query parameter of the web page address of the second page to obtain the authorization parameter.

[0088] On the basis of the above embodiment, the authorized login processing device includes a small text file processing module, and the small text file processing module includes: a file saving unit, which is configured to receive a login response sent by the second server after the second server confirms the browser login target domain name according to the authorization parameters, obtain the small text file in the login response, and locally associate the small text file with the target domain name and save it; wherein the small text file contains identity authentication information; a login request sending unit, which is configured to generate a login request according to the small text file locally associated with the target domain name when receiving a login operation for logging in to the target domain name, and send the login request to the second server, so that the second server verifies the identity authentication information in the small text file based on the login request, and confirms that the browser has logged in to the target domain name after the verification is passed.

[0089] Based on the above embodiment, the login operation response module 21 includes: a whitelist query unit, configured to determine whether the target domain name is in the whitelist of the third-party server based on the target domain name and the third-party server; a redirection address setting unit, configured to use a preset unified jump domain name as the first redirection address when the target domain name is not in the whitelist of the third-party server.

[0090] As mentioned above, the authorization login processing device provided by the embodiment of the present application sends an authorization request to a third-party server by using a unified jump domain name as a redirection address, and the third-party server appends the authorization parameter to the query parameter of the redirection address and redirects the browser to the unified jump domain name page, so that the server of the unified jump domain name resolves the web address of the unified jump domain name page to obtain the authorization parameter. The browser sends a redirection request to the server of the unified jump domain name by using the target domain name as a redirection address, and the server of the unified jump domain name appends the authorization parameter to the query parameter of the redirection address and redirects the browser to the target domain name page, so that the server of the target domain name resolves the web address of the target domain name page to obtain the authorization parameter, and the server of the target domain name confirms that the browser successfully logs in to the target domain name according to the authorization parameter. Through the above technical means, it is achieved that when the target domain name is not in the white list of the third-party server, the login authorization of the third-party server can also be obtained through the unified jump domain name, which solves the problem in the prior art that the domain name for requesting authorization login needs to be configured to the white list in the background of the third-party server, simplifies the configuration process of third-party authorized login, and improves the configuration efficiency of third-party authorized login.

[0091] The authorization login processing device provided in the embodiment of the present application can be used to execute the authorization login processing method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0092] Fig. 9 This is a schematic diagram of the structure of an authorization login processing device provided in an embodiment of the present application, with reference to Fig. 9 The authorization login processing device includes: a processor 41, a memory 42, a communication device 43, an input device 44 and an output device 45. The number of processors 41 in the authorization login processing device can be one or more, and the number of memories 42 in the authorization login processing device can be one or more. The processor 41, memory 42, communication device 43, input device 44 and output device 45 of the authorization login processing device can be connected through a bus or other methods.

[0093] The memory 42, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the authorized login processing method of any embodiment of the present application (for example, the login operation response module 31, the authorization request sending module 32, the first redirection module 33 and the redirection request sending module 34 and the second redirection module 35 in the authorized login processing device). The memory 42 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 42 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0094] The communication device 43 is used for data transmission.

[0095] The processor 41 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 42, that is, implements the above-mentioned authorized login processing method.

[0096] The input device 44 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the device. The output device 45 may include a display device such as a display screen.

[0097] The authorized login processing device provided above can be used to execute the authorized login processing method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0098] The embodiment of the present application also provides a storage medium containing computer executable instructions, which are used to execute an authorized login processing method when executed by a computer processor. The authorized login processing method includes: determining a target domain name to be logged in and a third-party server for authorized login according to a detected authorized login operation, and using a preset unified jump domain name as a first redirection address; sending an authorization request to the third-party server according to the first redirection address, so that the third-party server generates an authorization parameter based on the authorization request, generates a first redirection response according to the authorization parameter and the first redirection address, and sends the first redirection response to a browser; redirecting to a first page of the unified jump domain name according to the first redirection address in the first redirection response, so that the first server of the unified jump domain name resolves the web page address of the first page to obtain the authorization parameter; using the target domain name as a second redirection address, sending a redirection request to the first server of the unified jump domain name according to the second redirection address, so that the first server generates a second redirection response according to the authorization parameter and the second redirection address in the redirection request, and sending the second redirection response to the browser; redirecting to a second page of the target domain name according to the second redirection address in the second redirection response, so that the second server of the second target domain name resolves the web page address of the second page to obtain the authorization parameter, and confirming the browser login target domain name according to the authorization parameter.

[0099] Storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system, which is connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (for example, in different computer systems connected by a network). The storage medium may store program instructions (for example, embodied as a computer program) that can be executed by one or more processors.

[0100] Of course, the storage medium containing computer executable instructions provided in the embodiment of the present application, whose computer executable instructions are not limited to the above-mentioned authorization login processing method, can also execute related operations in the authorization login processing method provided in any embodiment of the present application.

[0101] The authorization login processing device, storage medium and authorization login processing equipment provided in the above embodiments can execute the authorization login processing method provided in any embodiment of the present application. For technical details not described in detail in the above embodiments, please refer to the authorization login processing method provided in any embodiment of the present application.

[0102] The above are only preferred embodiments of the present application and the technical principles used. The present application is not limited to the specific embodiments herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not deviate from the protection scope of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.

Claims

1. An authorized login processing method, characterized in that: Applies to browsers, including: Determine the target domain name to be logged in and the third-party server authorized to log in according to the detected authorized login operation, and use the preset unified jump domain name as the first redirection address; Sending an authorization request to the third-party server according to the first redirection address, so that the third-party server generates an authorization parameter based on the authorization request, generates a first redirection response according to the authorization parameter and the first redirection address, and sends the first redirection response to the browser; redirecting to the first page of the unified jump domain name according to the first redirection address in the first redirection response, so that the first server of the unified jump domain name resolves the webpage address of the first page to obtain the authorization parameter; Using the target domain name as a second redirection address, sending a redirection request to the first server of the unified jump domain name according to the second redirection address, so that the first server generates a second redirection response according to the authorization parameter and the second redirection address in the redirection request, and sending the second redirection response to the browser; Redirect to the second page of the target domain name according to the second redirect address in the second redirect response, so that the second server of the second target domain name parses the web address of the second page to obtain the authorization parameters, and confirms that the browser logs in to the target domain name according to the authorization parameters.

2. The authorized login processing method according to claim 1, characterized in that: The sending the authorization request to the third-party server according to the first redirection address includes: Obtain the authorization endpoint address, authorization response type, and access permission scope of the third-party server; Appending the authorization response type, the access permission and the first redirection address to the query parameters of the authorization endpoint address to construct an authorization request address; The authorization request address is loaded to send an authorization request to the third-party server according to the authorization endpoint address, wherein the authorization request includes a query parameter of the authorization endpoint address.

3. The authorized login processing method according to claim 1, characterized in that: The sending an authorization request to the third-party server according to the first redirection address, so that the third-party server generates an authorization parameter based on the authorization request, includes: Sending an authorization request to the third-party server according to the first redirection address, so that the third-party server performs a whitelist verification on the first redirection address in the authorization request, and sending a third redirection response to the browser according to the webpage address of the authorization page after the verification is passed; Redirect to the authorization page of the third-party server according to the web page address in the third redirection response, and send an authorization message to the third-party server in response to a click operation of the authorization control in the authorization page, so that the third-party server generates authorization parameters based on the authorization message.

4. The authorized login processing method according to claim 1, characterized in that: The authorization parameter is attached to the query parameter of the first redirection address, and the first redirection address is added to the response header of the first redirection response; Correspondingly, redirecting to the first page of the unified jump domain name according to the first redirect address in the first redirect response, so that the first server of the unified jump domain name resolves the webpage address of the first page to obtain the authorization parameter, includes: Obtaining a first redirection address in a response header of the first redirection response, loading the first redirection address to send a first access request to a first server of the unified jump domain name, so that the first server sends a first access response to the browser based on the first access request; Redirect to the first page of the unified jump domain name according to the first access response, so that the first server parses the query parameters of the web page address of the first page to obtain the authorization parameters.

5. The authorized login processing method according to claim 1, characterized in that: The authorization parameter is appended to the query parameter of the second redirection address, and the second redirection address is added to the response header of the second redirection response; Correspondingly, redirecting to the second page of the target domain name according to the second redirection address in the second redirection response so that the second server of the second target domain name resolves the webpage address of the second page to obtain the authorization parameter includes: Obtaining a second redirection address in a response header of the second redirection response, loading the second redirection address to send a second access request to a second server of the target domain name, so that the second server sends a second access response to the browser based on the second access request; Redirect to the second page of the target domain name according to the second access response, so that the second server parses the query parameter of the web page address of the second page to obtain the authorization parameter.

6. The authorized login processing method according to claim 1, characterized in that: After the second server confirms that the browser logs in to the target domain name according to the authorization parameter, the method further includes: receiving a login response sent by the second server, obtaining a small text file in the login response, and locally associating the small text file with the target domain name and saving the small text file; wherein the small text file contains identity authentication information; When a login operation to log in to the target domain name is received, a login request is generated based on a small text file locally stored in association with the target domain name, and the login request is sent to the second server, so that the second server verifies the identity authentication information in the small text file based on the login request, and confirms that the browser has logged in to the target domain name after the verification is passed.

7. The authorized login processing method according to claim 1, characterized in that: The method of using the preset unified jump domain name as the first redirection address includes: Determining, according to the target domain name and the third-party server, whether the target domain name is in a whitelist of the third-party server; When the target domain name is not in the whitelist of the third-party server, a preset unified jump domain name is used as the first redirection address.

8. An authorized login processing device, characterized in that: Applies to browsers, including: A login operation response module is configured to determine a target domain name to be logged in and a third-party server authorized to log in according to the detected authorized login operation, and use a preset unified jump domain name as a first redirection address; an authorization request sending module, configured to send an authorization request to the third-party server according to the first redirection address, so that the third-party server generates an authorization parameter based on the authorization request, generates a first redirection response according to the authorization parameter and the first redirection address, and sends the first redirection response to the browser; A first redirection module is configured to redirect to a first page of the unified jump domain name according to a first redirection address in the first redirection response, so that the first server of the unified jump domain name resolves the webpage address of the first page to obtain the authorization parameter; a redirection request sending module, configured to use the target domain name as a second redirection address, and send a redirection request to the first server of the unified jump domain name according to the second redirection address, so that the first server generates a second redirection response according to the authorization parameter and the second redirection address in the redirection request, and sends the second redirection response to the browser; The second redirection module is configured to redirect to the second page of the target domain name according to the second redirection address in the second redirection response, so that the second server of the second target domain name parses the web page address of the second page to obtain the authorization parameters, and confirms that the browser logs in to the target domain name according to the authorization parameters.

9. An authorized login processing device, characterized in that: include: one or more processors; A memory stores one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the authorized login processing method as described in any one of claims 1-7.

10. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are used to execute the authorization login processing method as described in any one of claims 1-7 when executed by a computer processor.

Images