Cross-item jump login-free method and device, storage medium and computer equipment

Abstract

The invention discloses a cross-item jump login-free method and device, a storage medium and computer equipment, relates to the technical field of webpage design, the medical field and the financial field, and mainly aims to solve the problem that existing cross-item jump login-free threatens system security. The method mainly comprises the following steps: in response to a project jump request for jumping to a target project, analyzing a source project carried by the project jump request; under the condition that the source project is a deployed project, actual project information corresponding to the source project is obtained, and the deployed project and the target project are deployed in the same server; verifying the authenticity of the source project according to the actual project information and the jump project verification strategy; and when the authenticity verification result is successful, obtaining login state information of the source project, and logging in the target project based on the login state information. The method is mainly used for login-free operation of cross-project jump.

Description

Technical Field

[0001] The present invention relates to the fields of web design, medical care and finance, and in particular to a login-free method and device for cross-project jumps, a storage medium and a computer device. Background Art

[0002] With the development of internet technology, the comprehensiveness of websites is constantly improving. This is particularly true for websites in the financial and medical fields. Due to the wide range of business branches involved in these fields, the services included on these websites are also more complex. User operations often need to span multiple projects. Therefore, cross-project login-free operation is of great significance for facilitating user operations across multiple projects.

[0003] Existing methods for achieving login-free cross-project login primarily rely on storing login information in a redirect link, which is then carried to the desired project. However, this method can easily lead to login information being leaked or stolen, potentially exposing the system to attacks and posing a serious threat to system security. Summary of the Invention

[0004] In view of this, the present invention provides a login-free method and device for cross-project jump, a storage medium, and a computer device, the main purpose of which is to solve the problem of low security of the existing cross-project login-free method.

[0005] According to one aspect of the present invention, a login-free method for jumping across projects is provided, comprising:

[0006] In response to a project jump request to jump to a target project, parsing a source project carried in the project jump request;

[0007] In the case where the source project is a deployed project, obtaining actual project information corresponding to the source project, wherein the deployed project and the target project are deployed on the same server;

[0008] Verify the authenticity of the source project based on the actual project information and the jump project verification strategy;

[0009] When the result of the authenticity verification is passed, the login status information of the source project is obtained, and the target project is logged in based on the login status information.

[0010] Furthermore, the redirection project verification strategy includes an address verification strategy, a device verification strategy, and a time verification strategy. The authenticity verification of the source project based on the actual project information and the redirection project verification strategy includes:

[0011] If the target project is an open project, authenticity verification is performed based on the actual project information and the address verification strategy or the device verification strategy;

[0012] In the case where the target project is a controlled project, authenticity verification is performed jointly based on the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy.

[0013] Furthermore, the authenticity verification is performed jointly based on the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy, including:

[0014] Retrieving user operation attributes of the source project, wherein the user operation attributes are determined based on historical user behavior data analysis results of the source project;

[0015] If the user operation attribute includes a continuous operation attribute, authenticity verification is performed according to the address verification strategy, the device verification strategy, and the time verification strategy in sequence based on the actual project information;

[0016] If the user operation attribute does not include a continuous operation attribute, authenticity verification is performed according to the actual project information, in accordance with the address verification strategy and the device verification strategy.

[0017] Furthermore, the authenticity verification is performed according to the address verification strategy, the device verification strategy, and the time verification strategy in sequence based on the actual project information, including:

[0018] Parsing the source address of the project jump request, and if the source address matches the page address in the actual project information, determining that the address verification is passed;

[0019] If the address verification result is passed, obtaining the network device identifier of the project jump request, and if the network device identifier is the same as the network device identifier in the actual project information, determining that the device verification is passed;

[0020] If the device verification result is passed, the last interface call time of the source project is obtained. If the interval between the last interface call time and the reception time of the project jump request is less than the preset time threshold, the authenticity verification result is determined to be passed.

[0021] Furthermore, the acquiring the login status information of the source project and logging into the target project based on the login status information includes:

[0022] Obtain the login state information of the source project through the login state information calling interface, wherein the login state information includes a previously generated token;

[0023] Performing validity verification on the token;

[0024] If the result of the validity check is passed, the login status of the target item is configured as logged in.

[0025] Furthermore, the login status information also includes an encrypted token, and the method further includes:

[0026] Retrieving the encrypted token key to decrypt the encrypted token to obtain a decrypted token;

[0027] Performing validity verification on the decrypted token;

[0028] If the result of the validity check is passed, the login status of the target item is configured as logged in.

[0029] Furthermore, the method further comprises:

[0030] If the result of the authenticity verification is failure, determining that the source project is a disguised project and the project jump request is a disguised jump request, generating prompt information for instructing the user to log in again, and monitoring the status information of the re-login;

[0031] If it is detected that the number of failed re-login attempts is greater than a preset login threshold, the project jump request is rejected.

[0032] According to another aspect of the present invention, a login-free device for jumping across projects is provided, comprising:

[0033] A parsing module, configured to respond to a project jump request to jump to a target project and parse a source project carried in the project jump request;

[0034] an acquisition module, configured to acquire actual project information corresponding to the source project if the source project is a deployed project, wherein the deployed project and the target project are deployed on the same server;

[0035] A verification module, configured to verify the authenticity of the source project based on the actual project information and the jump project verification strategy;

[0036] The login module is used to obtain the login status information of the source project when the result of the authenticity verification is passed, and log in to the target project based on the login status information.

[0037] Furthermore, the verification module includes:

[0038] A first verification unit is configured to perform authenticity verification based on the actual project information and the address verification strategy or the device verification strategy when the target project is an open project;

[0039] The second verification unit is used to jointly perform authenticity verification based on the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy when the target project is a controlled project.

[0040] Furthermore, in a specific application scenario, the second verification unit is specifically configured to retrieve user operation attributes of the source project, wherein the user operation attributes are determined based on historical user behavior data analysis results of the source project;

[0041] If the user operation attribute includes a continuous operation attribute, authenticity verification is performed according to the address verification strategy, the device verification strategy, and the time verification strategy in sequence based on the actual project information;

[0042] If the user operation attribute does not include a continuous operation attribute, authenticity verification is performed according to the actual project information, in accordance with the address verification strategy and the device verification strategy.

[0043] Furthermore, in a specific application scenario, the second verification unit is specifically configured to parse the source address of the project jump request, and determine that the address verification is passed if the source address matches the page address in the actual project information;

[0044] If the address verification result is passed, obtaining the network device identifier of the project jump request, and if the network device identifier is the same as the network device identifier in the actual project information, determining that the device verification is passed;

[0045] If the device verification result is passed, the last interface call time of the source project is obtained. If the interval between the last interface call time and the reception time of the project jump request is less than the preset time threshold, the authenticity verification result is determined to be passed.

[0046] Furthermore, the login module includes:

[0047] An acquiring unit, configured to acquire the login state information of the source project through a login state information calling interface, wherein the login state information includes a previously generated token;

[0048] A first verification unit, configured to verify the validity of the token;

[0049] A configuration unit is used to configure the login status of the target project to logged in if the result of the validity check is passed.

[0050] Furthermore, the device further comprises:

[0051] A decryption unit, configured to retrieve an encryption token key to decrypt the encrypted token to obtain a decrypted token;

[0052] A second verification unit, configured to verify the validity of the decrypted token;

[0053] The second configuration unit is configured to configure the login status of the target project to be logged in if the result of the validity check is passed.

[0054] Furthermore, the method further comprises:

[0055] If the result of the authenticity verification is failure, determining that the source project is a disguised project and the project jump request is a disguised jump request, generating prompt information for instructing the user to log in again, and monitoring the status information of the re-login;

[0056] If it is detected that the number of failed re-login attempts is greater than a preset login threshold, the project jump request is rejected.

[0057] According to another aspect of the present invention, a storage medium is provided, in which at least one executable instruction is stored. The executable instruction enables a processor to execute operations corresponding to the above-mentioned login-free method for jumping across projects.

[0058] According to another aspect of the present invention, there is provided a computer device comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus;

[0059] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute operations corresponding to the above-mentioned cross-project jump login-free method.

[0060] By means of the above technical solution, the technical solution provided by the embodiment of the present invention has at least the following advantages:

[0061] The present invention provides a method and device for cross-project jump without login. First, in response to a project jump request to jump to a target project, the source project carried by the project jump request is parsed; if the source project is a deployed project, the actual project information corresponding to the source project is obtained, wherein the deployed project and the target project are deployed on the same server; based on the actual project information and the jump project verification strategy, the authenticity of the source project is verified; if the result of the authenticity verification is passed, the login state information of the source project is obtained, and the target project is logged in based on the login state information. Compared with the prior art, the embodiment of the present invention verifies the authenticity of the jump source project through the actual project information and the jump project verification strategy, greatly reducing the threat posed by the login-free process to the login information security, greatly improving the shielding and interception probability of malicious impersonation of the source project, thereby improving the security of the cross-page jump without login process.

[0062] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0064] Figure 1 A flowchart of a login-free method for jumping between projects provided by an embodiment of the present invention is shown;

[0065] Figure 2 A flowchart of another method for jumping between projects without logging in provided by an embodiment of the present invention is shown;

[0066] Figure 3 A block diagram of a login-free device for jumping across projects provided by an embodiment of the present invention is shown;

[0067] Figure 4 A schematic structural diagram of a computer device provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0068] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0069] The embodiment of the present invention provides a login-free method for jumping across projects, such as Figure 1 As shown, the method includes:

[0070] 101. In response to a project jump request to jump to a target project, parse a source project carried in the project jump request.

[0071] In this embodiment of the present invention, the current execution entity is the backend server of the business system corresponding to the target project. This server supports multiple projects, and the domain names of each project can be the same or different, but this embodiment does not impose specific restrictions. For example, in the medical field, an internet hospital system includes multiple projects such as outpatient appointment registration, hospitalization processing, online payment, and laboratory testing. Another example is in the financial field, where a financial business system includes contract services, loan services, and order services. The current execution entity service can be a local server or a cloud server, but this embodiment does not impose specific restrictions. The source project is the project requesting a redirect to the target project. This project can be in the same system as the target project, i.e., deployed on the same server, or it can be a different project than the target project, i.e., deployed on a different server. Furthermore, a project redirect request can be an actual request generated by a user through an operation in the source project, or it can be a fake, malicious request generated by a hacker using the source project as a disguise, not originating from an operation in the actual source project.

[0072] 102. When the source project is a deployed project, obtain actual project information corresponding to the source project.

[0073] In an embodiment of the present invention, it is determined based on the identification information of the source project whether the current source project is a project deployed on the same server as the target project. If so, it is determined to be a deployed project. If deployed, the deployed project is deployed on the same server as the target project. If it is identified that the current source project is not on the same server as the target project, the login information cannot be shared, and login-free cannot be achieved. Therefore, a jump can be executed, but there is no need to retrieve the login status information for login-free execution. In the case of identifying that the source project is a deployed project that can be executed without login, the actual project information of this source project is obtained, that is, the current execution subject retrieves the actual information in the project system according to the identification information of the source project, such as the source address, network device address, the time of the last query to the server, and other information, so as to determine whether the current project is a project used by hackers for disguise based on the actual project information of the source information.

[0074] 103. Verify the authenticity of the source project based on the actual project information and the jump project verification strategy.

[0075] In this embodiment of the present invention, to determine whether a source project is genuine or a hacker's disguise, a redirection project verification strategy is used in conjunction with the actual project information. For example, the source address of the source project is checked to see if it matches the source address in the actual project information. If so, the source project is genuine and the authenticity verification result is a pass. If not, the source address is a hacker's disguise and the source project has no real need for redirection, resulting in a fail.

[0076] It should be noted that by obtaining the actual project information of the source project and verifying the authenticity based on the actual project information, it is possible to effectively identify jump requests disguised by hackers, avoid leaking user login information, and reduce the security of the system, thereby ensuring the security of login-free jumps across pages.

[0077] In one embodiment of the present invention, for further explanation and limitation, as Figure 2 As shown, the authenticity verification of the source project based on the actual project information and the jump project verification strategy includes:

[0078] 201. When the target project is an open project, authenticity verification is performed based on the actual project information and the address verification strategy or the device verification strategy.

[0079] 202. When the target project is a managed project, authenticity verification is performed jointly based on the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy.

[0080] In this embodiment of the present invention, target projects include open projects and managed projects. Open projects are publicly accessible and have a lower security control level. For example, outpatient appointment registration projects and online diagnosis and treatment projects in an internet hospital system are accessible to any registered user and can be viewed. Managed projects are accessible to specific groups and have a higher security control level. For example, diagnosis and prescription entry projects and laboratory data entry projects in an internet hospital system are accessible only to internal hospital personnel. Jump project verification policies include address verification, device verification, and time verification. For open projects, only one verification policy can be used for authenticity verification. Specifically, one verification policy can be selected from either the address verification policy or the device verification policy based on the specific application scenario. For managed projects, any two of the three verification policies can be combined for authenticity verification. For example, the address verification policy can be combined with the device verification policy, the address verification policy can be combined with the time verification policy, or the device verification policy can be combined with the time verification policy. Alternatively, all three verification policies can be combined for authenticity verification. The address verification strategy verifies the authenticity of the source item based on the source address. The source address can be a URL or link in a network layer protocol, used to locate the resource in a web browser. The device verification strategy verifies the authenticity of the source item based on the MAC address, which is the physical address of the network device at the data link layer. The time verification strategy verifies the authenticity of the source item based on the actual time when the source item calls the interface.

[0081] It's important to note that by configuring a source project's network layer protocol URL or link, the physical address of the network device, and a time-based verification strategy to verify the authenticity of the source project, we can effectively identify spoofed sources and ensure the accuracy of authenticity verification. Furthermore, by using a different number of verification strategies for projects with different security requirements, we can reduce resource consumption while ensuring the accuracy of authenticity verification.

[0082] In one embodiment of the present invention, for further explanation and limitation, the authenticity verification based on the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy includes:

[0083] Retrieve user operation attributes of the source item;

[0084] If the user operation attribute includes a continuous operation attribute, authenticity verification is performed according to the address verification strategy, the device verification strategy, and the time verification strategy in sequence based on the actual project information;

[0085] If the user operation attribute does not include a continuous operation attribute, authenticity verification is performed according to the actual project information, in accordance with the address verification strategy and the device verification strategy.

[0086] In an embodiment of the present invention, in addition to authenticity verification based on the address verification strategy and the device verification strategy, a time limit is also added. If the time interval between the last operation on the source project and the issuance of the project jump request is too long, it is difficult to ensure that the issuance of the project jump request and the actual operation of the source project are the same user operation, that is, the source project is likely to be disguised, and therefore, the verification fails. To improve the accuracy of the time verification strategy, it is necessary to determine whether the current user's operation in the source project has the continuous operation attribute based on the user operation attributes of the source project. If the current user's operation in the source project has the continuous operation attribute, the accuracy of applying the time verification strategy will be higher. However, if the current user's operation in the source project does not have the continuous operation attribute, the recognition accuracy of the time verification strategy will be greatly reduced, and verification will be performed only based on the address verification strategy and the device verification strategy. If the user operation attribute includes the continuous operation attribute, that is, the time interval between each operation of the currently logged-in user is small, the authenticity of the source information can be verified based on the time interval between the time of the project jump request to jump to the target project and the last operation time in the actual project information.

[0087] Among them, the continuous operation attribute is used to characterize the operations performed by the user in the source project, which has a high degree of continuity in time. The user operation attribute is determined based on the analysis results of the historical user behavior data of the source project. Specifically, it can be obtained through the user portrait model, classified and identified according to the historical user behavior data. It can also be obtained through the clustering results of historical user behavior data. For example, in the case where the continuous operation attribute is determined based on the time interval of the interface call, the user's interface call time interval is clustered, and the time interval corresponding to the largest number of clusters is determined to be the interface call time interval of the current user. If this interface call time interval is less than the interface call time interval threshold, it is determined that the user operation attribute of this user includes the continuous operation attribute.

[0088] In one embodiment of the present invention, for further explanation and limitation, performing authenticity verification according to the address verification strategy, the device verification strategy, and the time verification strategy in sequence based on the actual project information includes:

[0089] Parsing the source address of the project jump request, and if the source address matches the page address in the actual project information, determining that the address verification is passed;

[0090] If the address verification result is passed, obtaining the network device identifier of the project jump request, and if the network device identifier is the same as the network device identifier in the actual project information, determining that the device verification is passed;

[0091] If the device verification result is passed, the last interface call time of the source project is obtained. If the interval between the last interface call time and the reception time of the project jump request is less than the preset time threshold, the authenticity verification result is determined to be passed.

[0092] In an embodiment of the present invention, verification is performed based on an address verification strategy, including parsing the source address carried in the project jump request (this address may be a hacker's disguised address) and matching this address with the page address in the actual project information. If they match, the source address is correct, and the address verification is determined to have passed. If they do not match, the source address is disguised, and the address verification is determined to have passed. Furthermore, verification is performed based on a device verification strategy, including obtaining the data link layer identifier of the network device corresponding to the project jump request, i.e., the network device identifier. If this network device identifier is the same as the network device identifier in the actual project information, since each MAC address is unique, if the MAC address in the actual project information is consistent with the MAC address that issued the project jump request, it is highly likely that the project jump request originated from the real source project and was operated by the same user, not a disguised one. Furthermore, the time interval between the time of the project jump request to jump to the target project and the time of the last operation in the actual project information is calculated. If the time interval between the two is less than a preset time interval threshold, the authenticity verification of the source information is determined to have passed. If the time interval between the two is greater than or equal to the preset time interval threshold, the authenticity verification of the source information is determined to have failed. The preset time interval threshold may be configured as 30 seconds, 1 minute, etc., or may be customized according to actual application scenario requirements, and is not specifically limited in the embodiment of the present invention.

[0093] 104. When the result of the authenticity verification is passed, obtain the login status information of the source project, and log in to the target project based on the login status information.

[0094] In an embodiment of the present invention, after authenticity verification, the current execution subject obtains the latest login status information of the source project through the interface and stores it in the target project, then the target project can realize user-side login-free based on this login status information. Compared with storing the token in a cookie or storage, the above technical solution has restrictions on the domain name of the jump project (limited to the same domain name), and can be applied to jump-free login scenarios between more projects with different domain names, and the applicability of the scenarios is more extensive. Especially for complex multi-level systems such as the medical field and the financial field, due to the existence of multi-level domain names, the consistency of the domain names between the jump projects cannot be guaranteed. This application can realize cross-project login-free between projects with different domain names. Compared with the method of storing the login token on the link and bringing it to the target project through the project jump (easy to leak information, be attacked or have information stolen), this application can greatly improve the security of information and avoid the login process from posing a threat to system security.

[0095] In one embodiment of the present invention, for further explanation and limitation, obtaining the login status information of the source project and logging into the target project based on the login status information includes:

[0096] Obtain the login status information of the source project through the login status information calling interface;

[0097] Performing validity verification on the token;

[0098] If the result of the validity check is passed, the login status of the target item is configured as logged in.

[0099] In an embodiment of the present invention, after the source project passes the authenticity verification, the authenticity and security of the source information can be determined, and a login-free operation can be performed. Specifically, through a pre-configured interface for calling the source project login status information, the login status information calling interface obtains the login status information generated by the current operating user after logging into the source project. The login status information includes a previously generated token. In order to ensure the success rate of login-free operation, the validity of the token is verified before logging into the target project, such as checking whether the token has timed out. If the token is valid, the target project is logged in based on the token, and the login status of the target project is configured to be logged in. If the token verification result is failed, information is generated to instruct the user to re-login to the target project.

[0100] In one embodiment of the present invention, for further illustration and limitation, the method further includes:

[0101] Retrieving the encrypted token key to decrypt the encrypted token to obtain a decrypted token;

[0102] Performing validity verification on the decrypted token;

[0103] If the result of the validity check is passed, the login status of the target item is configured as logged in.

[0104] In an embodiment of the present invention, to further ensure information security during the login-free process, after a user logs in to a source project and generates a token, the token is encrypted and the corresponding key is stored. This means that the login state information also includes the encrypted token. After obtaining the login state information of the source project through the login state information call interface, the encrypted token key is obtained to decrypt the encrypted token in order to perform subsequent login-free operations. By encrypting the token, hacker attacks can be further prevented, ensuring system security.

[0105] In one embodiment of the present invention, for further illustration and limitation, the method further includes:

[0106] If the result of the authenticity verification is failure, determining that the source project is a disguised project and the project jump request is a disguised jump request, generating prompt information for instructing the user to log in again, and monitoring the status information of the re-login;

[0107] If it is detected that the number of failed re-login attempts is greater than a preset login threshold, the project jump request is rejected.

[0108] In an embodiment of the present invention, if any one of the address verification strategy, device verification strategy, and time verification strategy performed on the source project fails, the project jump request is determined to be a disguised jump request, and the source project carried in the request is a project used as a disguise by hackers. At this time, a prompt message is generated to instruct the user to re-login, so as to intercept malicious attacks by requesting re-login, and monitor the status information of re-login. If it is monitored that the re-login has experienced multiple failures, and the number of failures is greater than the preset login threshold, indicating that the current source information is a malicious attack, the project jump request is rejected to ensure system security. Among them, the preset login threshold can be 3 times, 5 times, or can be customized according to application requirements, and the embodiment of the present invention does not make specific limitations.

[0109] The present invention provides a login-free method for cross-project jumps. First, in response to a project jump request to jump to a target project, the source project carried by the project jump request is parsed; if the source project is a deployed project, the actual project information corresponding to the source project is obtained, wherein the deployed project and the target project are deployed on the same server; based on the actual project information and the jump project verification strategy, the authenticity of the source project is verified; if the result of the authenticity verification is passed, the login state information of the source project is obtained, and the target project is logged in based on the login state information. Compared with the prior art, the embodiment of the present invention verifies the authenticity of the jump source project through the actual project information and the jump project verification strategy, greatly reducing the threat posed by the login-free process to the login information security, greatly improving the shielding and interception probability of malicious impersonation of the source project, thereby improving the security of the cross-page jump login-free process.

[0110] Furthermore, as a response to the above Figure 1 The embodiment of the present invention provides a login-free device for jumping across projects, such as Figure 3 As shown, the device includes:

[0111] The parsing module 31 is configured to respond to a project jump request to jump to a target project and parse a source project carried in the project jump request;

[0112] An acquisition module 32 is configured to acquire actual project information corresponding to the source project when the source project is a deployed project, wherein the deployed project and the target project are deployed on the same server;

[0113] A verification module 33 is configured to verify the authenticity of the source project based on the actual project information and the jump project verification strategy;

[0114] The login module 34 is configured to obtain login status information of the source project and log in to the target project based on the login status information when the authenticity verification result is passed.

[0115] Furthermore, the verification module 33 includes:

[0116] A first verification unit is configured to perform authenticity verification based on the actual project information and the address verification strategy or the device verification strategy when the target project is an open project;

[0117] The second verification unit is used to jointly perform authenticity verification based on the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy when the target project is a controlled project.

[0118] Furthermore, in a specific application scenario, the second verification unit is specifically configured to retrieve user operation attributes of the source project, wherein the user operation attributes are determined based on historical user behavior data analysis results of the source project;

[0119] If the user operation attribute includes a continuous operation attribute, authenticity verification is performed according to the address verification strategy, the device verification strategy, and the time verification strategy in sequence based on the actual project information;

[0120] If the user operation attribute does not include a continuous operation attribute, authenticity verification is performed according to the actual project information, in accordance with the address verification strategy and the device verification strategy.

[0121] Furthermore, in a specific application scenario, the second verification unit is specifically configured to parse the source address of the project jump request, and determine that the address verification is passed if the source address matches the page address in the actual project information;

[0122] If the address verification result is passed, obtaining the network device identifier of the project jump request, and if the network device identifier is the same as the network device identifier in the actual project information, determining that the device verification is passed;

[0123] If the device verification result is passed, the last interface call time of the source project is obtained. If the interval between the last interface call time and the reception time of the project jump request is less than the preset time threshold, the authenticity verification result is determined to be passed.

[0124] Furthermore, the login module 34 includes:

[0125] An acquiring unit, configured to acquire the login state information of the source project through a login state information calling interface, wherein the login state information includes a previously generated token;

[0126] A first verification unit, configured to verify the validity of the token;

[0127] A configuration unit is used to configure the login status of the target project to logged in if the result of the validity check is passed.

[0128] Furthermore, the device further comprises:

[0129] A decryption unit, configured to retrieve an encryption token key to decrypt the encrypted token to obtain a decrypted token;

[0130] A second verification unit, configured to verify the validity of the decrypted token;

[0131] The second configuration unit is configured to configure the login status of the target project to be logged in if the result of the validity check is passed.

[0132] Furthermore, the method further comprises:

[0133] If the result of the authenticity verification is failure, determining that the source project is a disguised project and the project jump request is a disguised jump request, generating prompt information for instructing the user to log in again, and monitoring the status information of the re-login;

[0134] If it is detected that the number of failed re-login attempts is greater than a preset login threshold, the project jump request is rejected.

[0135] The present invention provides a login-free device for cross-project jumps. First, in response to a project jump request to jump to a target project, the source project carried by the project jump request is parsed; if the source project is a deployed project, the actual project information corresponding to the source project is obtained, wherein the deployed project and the target project are deployed on the same server; based on the actual project information and the jump project verification strategy, the authenticity of the source project is verified; if the result of the authenticity verification is passed, the login state information of the source project is obtained, and the target project is logged in based on the login state information. Compared with the prior art, the embodiment of the present invention verifies the authenticity of the jump source project through the actual project information and the jump project verification strategy, greatly reducing the threat posed by the login-free process to the login information security, greatly improving the shielding and interception probability of malicious impersonation of the source project, thereby improving the security of the cross-page jump login-free process.

[0136] According to one embodiment of the present invention, a storage medium is provided, wherein the storage medium stores at least one executable instruction, and the computer executable instruction can execute the login-free method for jumping across projects in any of the above method embodiments.

[0137] Figure 4 A schematic structural diagram of a computer device provided according to an embodiment of the present invention is shown. The specific embodiment of the present invention does not limit the specific implementation of the computer device.

[0138] like Figure 4 As shown, the computer device may include: a processor 402 , a communications interface 404 , a memory 406 , and a communication bus 408 .

[0139] The processor 402 , the communication interface 404 , and the memory 406 communicate with each other via a communication bus 408 .

[0140] The communication interface 404 is used to communicate with other devices such as clients or other servers.

[0141] The processor 402 is used to execute the program 410, and specifically can execute the relevant steps in the above-mentioned embodiment of the login-free method for jumping across projects.

[0142] Specifically, the program 410 may include program codes, which include computer operation instructions.

[0143] Processor 402 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The one or more processors included in a computer device may be of the same type, such as one or more CPUs, or may be of different types, such as one or more CPUs and one or more ASICs.

[0144] The memory 406 is used to store the program 410. The memory 406 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0145] The program 410 may be specifically configured to cause the processor 402 to perform the following operations:

[0146] In response to a project jump request to jump to a target project, parsing a source project carried in the project jump request;

[0147] In the case where the source project is a deployed project, obtaining actual project information corresponding to the source project, wherein the deployed project and the target project are deployed on the same server;

[0148] Verify the authenticity of the source project based on the actual project information and the jump project verification strategy;

[0149] When the result of the authenticity verification is passed, the login status information of the source project is obtained, and the target project is logged in based on the login status information.

[0150] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, centralized on a single computing device, or distributed across a network of multiple computing devices. Alternatively, they can be implemented using program code executable by a computing device, which can then be stored in a storage device and executed by the computing device. In some cases, the steps shown or described can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0151] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A login-free method for jumping across projects, characterized in that: include: In response to a project jump request to jump to a target project, parsing a source project carried in the project jump request; In the case where the source project is a deployed project, obtaining actual project information corresponding to the source project, wherein the deployed project and the target project are deployed on the same server; Verify the authenticity of the source project based on the actual project information and the jump project verification strategy; When the result of the authenticity verification is passed, the login status information of the source project is obtained, and the target project is logged in based on the login status information.

2. The method according to claim 1, characterized in that The jump project verification strategy includes an address verification strategy, a device verification strategy, and a time verification strategy. The authenticity verification of the source project based on the actual project information and the jump project verification strategy includes: If the target project is an open project, authenticity verification is performed based on the actual project information and the address verification strategy or the device verification strategy; In the case where the target project is a controlled project, authenticity verification is performed jointly based on the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy.

3. The method according to claim 2, characterized in that The authenticity verification is performed in combination with the actual project information and at least two of the address verification strategy, the device verification strategy, and the time verification strategy, including: Retrieving user operation attributes of the source project, wherein the user operation attributes are determined based on historical user behavior data analysis results of the source project; If the user operation attribute includes a continuous operation attribute, authenticity verification is performed according to the address verification strategy, the device verification strategy, and the time verification strategy in sequence based on the actual project information; If the user operation attribute does not include a continuous operation attribute, authenticity verification is performed according to the actual project information, in accordance with the address verification strategy and the device verification strategy.

4. The method according to claim 3, characterized in that The authenticity verification is performed according to the address verification strategy, the device verification strategy, and the time verification strategy based on the actual project information, including: Parsing the source address of the project jump request, and if the source address matches the page address in the actual project information, determining that the address verification is passed; If the address verification result is passed, obtaining the network device identifier of the project jump request, and if the network device identifier is the same as the network device identifier in the actual project information, determining that the device verification is passed; If the device verification result is passed, the last interface call time of the source project is obtained. If the interval between the last interface call time and the reception time of the project jump request is less than the preset time threshold, the authenticity verification result is determined to be passed.

5. The method according to claim 1, wherein The acquiring the login status information of the source project and logging into the target project based on the login status information includes: Obtain the login state information of the source project through the login state information calling interface, wherein the login state information includes a previously generated token; Performing validity verification on the token; If the result of the validity check is passed, the login status of the target item is configured as logged in.

6. The method according to claim 5, characterized in that The login status information also includes an encrypted token, and the method further includes: Retrieving the encrypted token key to decrypt the encrypted token to obtain a decrypted token; Performing validity verification on the decrypted token; If the result of the validity check is passed, the login status of the target item is configured as logged in.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: If the result of the authenticity verification is failure, determining that the source project is a disguised project and the project jump request is a disguised jump request, generating prompt information for instructing the user to log in again, and monitoring the status information of the re-login; If it is detected that the number of failed re-login attempts is greater than a preset login threshold, the project jump request is rejected.

8. A login-free device for jumping across projects, characterized in that: include: A parsing module, configured to respond to a project jump request to jump to a target project and parse a source project carried in the project jump request; an acquisition module, configured to acquire actual project information corresponding to the source project if the source project is a deployed project, wherein the deployed project and the target project are deployed on the same server; A verification module, configured to verify the authenticity of the source project based on the actual project information and the jump project verification strategy; The login module is used to obtain the login status information of the source project when the result of the authenticity verification is passed, and log in to the target project based on the login status information.

9. A storage medium storing at least one executable instruction, wherein the executable instruction enables a processor to execute an operation corresponding to the login-free method for cross-project jump according to any one of claims 1 to 7.

10. A computer device comprising: A processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the login-free method for cross-project jump according to any one of claims 1-7.

Images