Cross-system login processing method and device under same domain name, intelligent terminal and medium

By calling the login interface in the background and returning cookies during cross-system login, the problem of username and password transmission in the existing technology is solved, and cross-system login with high security and flexible operation is achieved, improving user experience and system security .

CN119046925APending Publication Date: 2024-11-29SHENZHEN COOCAA NETWORK TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411050442.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-01
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

When logging in across systems in the prior art, the user name and password need to be written on the front-end page to submit, which is poor in security and is not flexible enough, making it inconvenient for users to use.

Method used

By calling the login interface of the second system in the backend of the first system, passing the user name and password, and returning cookies with login information, accessing after the front-end configuration is avoided, and the user name and password are clearly transmitted, and security and operational flexibility are improved.

Benefits of technology

It realizes cross-system login with high security and flexible operation, and users do not need to enter login information frequently, improving user experience and system security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119046925A_ABST
    Figure CN119046925A_ABST
Patent Text Reader

Abstract

The invention discloses a cross-system login processing method and device under the same domain name, an intelligent terminal and a medium, and the method comprises the steps: controlling to call a first login interface of a first system background when an operation request of skipping to a second system is detected through a skipping function menu, and calling a second login interface of the second system through the first login interface; the first login interface transmits the second user name and the second password to the second login interface; the second system verifies a second user name and a second password, and returns an information storage small file cookie with login information of the second user name and the second password to the first login interface; sending the data to the first system front end for configuration; and the first system accesses the second system through the configured information storage small file cookie with the second user name and the second password login information when the permission verification of the second system is successful. According to the invention, the system security is improved; moreover, login is carried out in the background, so that the user authority control is more flexible.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a method, device, intelligent terminal and storage medium for processing cross-system login under the same domain name. Background Art

[0002] When working on Internet projects, there may often be scenarios where you need to log in across systems, such as logging in from system A to system B. However, system B is a mature product and has no ability to be maintained. In this case, the code of system B cannot be modified. This is the scenario we will mainly discuss.

[0003] One of the existing cross-system login methods is to embed the login page of system B through iframe and then submit it automatically (iframe is an HTML tag used to display another web page in one web page). This method is a relatively common solution. Users can basically use it without any perception, but the disadvantage of the existing cross-system login is that the user name and password must be written in the front-end page for submission, which has poor security, is not flexible enough, and is not convenient for users to use.

[0004] Therefore, the existing technology still needs to be improved and developed. Summary of the invention

[0005] The technical problem to be solved by the present invention is that, in view of the above-mentioned defects of the prior art, a method, device, intelligent terminal and storage medium for processing cross-system login under the same domain name are provided. The present invention realizes cross-system login under the same domain name, and the username and password used for login do not need to be written in the front-end page for submission. It has good security and flexible operation, which provides convenience for users.

[0006] The technical solution adopted by the present invention to solve the problem is as follows:

[0007] A method for processing cross-system login under the same domain name, comprising:

[0008] When a cross-system login is required under the same domain name, a first user name and a password registered in a first system are obtained, and the first system is logged in using the first user name and the first password;

[0009] When an operation request to jump to the second system is detected through the jump function menu, the first login interface of the first system background is controlled to be called, and the second login interface of the second system is called through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface;

[0010] The second system verifies the second user name and the second password, and returns a small information storage file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the small information storage file cookie to the first system front end and configures it;

[0011] The first system accesses the second system by configuring a small information storage file cookie with the second user name and second password login information and successfully verifying the authority of the second system.

[0012] The method for processing cross-system login under the same domain name, wherein when cross-system login under the same domain name is required, the step of obtaining a first user name and password registered in a first system and logging in to the first system using the first user name and the first password includes:

[0013] A first user name and password pre-registered in the first system for allowing login to the first system;

[0014] And a second user name and password are pre-registered in the second system for allowing login to the second system.

[0015] The method for processing cross-system login under the same domain name, wherein when cross-system login under the same domain name is required, the step of obtaining a first user name and password registered in a first system and logging in to the first system using the first user name and the first password includes:

[0016] A jump function menu for jumping from the first system to the second system is preset.

[0017] The method for processing cross-system login under the same domain name, wherein when cross-system login under the same domain name is required, the step of obtaining a first user name and password entered for registration in a first system, and logging into the first system using the first user name and first password includes:

[0018] When cross-system login is required under the same domain name, the first user name userA and password pwdA registered in the first system are obtained through the login interface of the first system, and the first system is logged in with the first user name and the first password.

[0019] The method for processing cross-system login under the same domain name, wherein when an operation request to jump to the second system is detected through the jump function menu, the first login interface of the first system background is controlled to be called, and the second login interface of the second system is called through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface. The step includes:

[0020] Detecting whether the jump function menu receives an operation instruction to jump to the second system;

[0021] When an operation request to jump to the second system is detected through the jump function menu, the control calls the first login interface of the first system background, and calls the second login interface of the second system through the first login interface; the first login interface transmits the second user name and second password of the second system to the second login interface.

[0022] The method for processing cross-system login under the same domain name, wherein the second system verifies the second user name and the second password, and returns an information storage small file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the information storage small file cookie to the first system front end and configures the steps including:

[0023] After the second system successfully verifies the second user name and the second password, it returns a small information storage file cookie with the second user name and the second password login information to the first login interface;

[0024] The first login interface sends a small information storage file cookie with the second user name and second password login information to the first system front end and configures it to verify whether the user is logged in when jumping to the second system.

[0025] The method for processing cross-system login under the same domain name, wherein the step of the first login interface sending the small file cookie with the information storage to the first system front end and configuring it includes:

[0026] The first system front end obtains the information storage small file cookie containing the second user name and second password login information returned by the first login interface A1, and sets the cookie returned by the second login interface of the second system on the first system front end.

[0027] The method for processing cross-system login under the same domain name, wherein the first system accesses the second system by using a configured information storage small file cookie with the second user name and the second password login information and successfully checking the authority of the second system, including:

[0028] The first system front end obtains the information storage small file cookie with the second user name and second password login information returned by the first login interface A1 and is successfully set. The first system initiates an access permission verification request to the second system through the configured information storage small file cookie with the second user name and second password login information;

[0029] The first system is allowed to access the second system through authority verification.

[0030] A device for processing cross-system login under the same domain name, wherein the device comprises:

[0031] A presetting module is used to pre-register a first user name and password in the first system for allowing login to the first system; and to pre-register a second user name and password in the second system for allowing login to the second system; and to pre-set a jump function menu for jumping from the first system to the second system;

[0032] A first system login processing module, used for obtaining a first user name and password registered in the first system when a cross-system login under the same domain name is required, and logging into the first system using the first user name and the first password;

[0033] A jump login processing module, for controlling the calling of a first login interface of the first system background when an operation request for jumping to the second system is detected through the jump function menu, and calling a second login interface of the second system through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface;

[0034] A configuration processing module is used to control the second system to verify the second user name and the second password, and return an information storage small file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the information storage small file cookie to the first system front end and performs configuration;

[0035] The jump login verification module is used to control the first system to access the second system through a configured information storage small file cookie with the second user name and second password login information and successful permission verification in the second system.

[0036] An intelligent terminal includes a memory and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by one or more processors, including the method for executing any one of the methods described above.

[0037] A non-transitory computer-readable storage medium, wherein when the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute any one of the methods described above.

[0038] Beneficial effects of the present invention: The present invention provides a method, device, intelligent terminal and storage medium for processing cross-system login under the same domain name. When the present invention implements cross-system login under the same domain name, a background interface can be requested first when jumping from system A, and this interface requests the login interface of system B. After successful login, system B will return cookie information. The background interface then returns this cookie information to the front end. After the front end is successfully set, system B can be directly accessed. The present invention implements cross-system login under the same domain name, and the user name and password used for login do not need to be written in the front-end page for submission, which has good security and flexible operation, providing convenience for users. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 It is a flowchart of a method for processing cross-system login under the same domain name provided by an embodiment of the present invention.

[0041] Figure 2 It is a schematic diagram of the abnormal facial expression recognition model processing of the cross-system login processing method under the same domain name provided by an embodiment of the present invention.

[0042] Figure 3 It is a principle block diagram of an embodiment of a cross-system login processing device under the same domain name provided by the present invention.

[0043] Figure 4 It is a block diagram of the internal structure principle of the intelligent terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and advantages of the present invention clearer and more specific, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0045] It should be noted that if the embodiments of the present invention involve directional indications (such as up, down, left, right, front, back, etc.), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0046] The disadvantage of the cross-system login in the prior art is that the user name and password must be written in the front-end page for submission, which has poor security, is not flexible enough, and is not convenient for users to use.

[0047] The present invention provides a cross-system login processing method under the same domain name, which mainly adopts cookie jump login. When jumping from system A, a backend interface is first requested, and this interface requests the login interface of system B. After successful login, system B will return cookie information. The backend interface then returns this cookie information to the front end. After the front end is successfully set, system B can be directly accessed.

[0048] Among them, in the embodiment of the present invention, the system is jumped to the login page by using a cookie, which is used to set a cookie containing login information when jumping to the login system to realize the function of automatic login or jumping to the login page. When a user logs in to the system for the first time, a cookie with the user's login information is generated and stored in the user's browser. When the user accesses the system again, the system checks whether the cookie exists in the user's browser. If it exists, the user is automatically logged in to his account without the user having to manually enter the user name and password.

[0049] If the cookie does not exist in the user's browser, it may trigger a jump login, that is, the system will detect that the user is not logged in, and automatically jump to the login page, requiring the user to enter the username and password for verification. Once the user successfully logs in, the system will set the login information cookie to the user's browser again, so that the user can automatically log in the next time they visit the system.

[0050] Login redirection through cookies can improve user experience, reduce the tediousness of users frequently entering login information, and increase system security. However, it should be noted that for systems involving user privacy and security, cookies must be set with caution to ensure the security and privacy of user data.

[0051] The "cookie" in "Login by cookie jump" refers to a small file that the system sends to the user's browser when the user accesses the system, which is used to store the user's login information or other related data. When the user successfully logs in, the server will set a cookie containing the login information in the user's browser, so that when the user browses other pages or performs other operations, the user's identity can be verified through the cookie, thereby jumping to the login state without the user having to enter the user name and password again to log in. Login by cookie jump can improve the user experience and avoid users frequently entering login credentials.

[0052] When implementing it, Figure 1 As shown, a method for processing cross-system login under the same domain name in embodiment 1 of the present invention includes the following steps:

[0053] Step S100: when a cross-system login is required under the same domain name, a first user name and a password registered in a first system are obtained, and the first system is logged in using the first user name and the first password;

[0054] The specific embodiment of the present invention is described by taking the cross-system login application scenario under the same domain name as an example, and the first system and the second system of the cross-system login are both deployed under the same Tomcat, so there is no cross-domain problem. Among them, Tomcat is an open source Java Servlet container and also a web server.

[0055] The first system A and the second system B are deployed under the same tomcat: This is achieved by creating different web applications in the webapps directory of Tomcat, each of which represents a different AB system implementation. This deployment method allows different AB systems to run independently, isolating each other, while sharing the resources of the same Tomcat server. When A / B testing is required, the corresponding AB system can be called by accessing different URLs or setting different request parameters. This deployment method facilitates the management and maintenance of the AB system and can provide a certain degree of flexibility and scalability.

[0056] In the specific implementation of the present invention, it is necessary to pre-register a first user name and password in the first system for allowing login to the first system; and pre-register a second user name and password in the second system for allowing login to the second system. A jump function menu for jumping from the first system to the second system is pre-set in the first system, and cross-system login can be easily achieved by clicking the jump function menu.

[0057] When this step is implemented, when a cross-system login is required under the same domain name, the first user name userA and password pwdA registered in the first system are obtained through the login interface of the first system, and the first system is logged in through the first user name and the first password. Then, the first system is operated to prepare for cross-system login to the second system, as described in step S200.

[0058] Step S200: When an operation request to jump to the second system is detected through the jump function menu, the first login interface of the first system background is controlled to be called, and the second login interface of the second system is called through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface;

[0059] In the embodiment of this step, when an operation request to jump to the second system is detected through the jump function menu: the user operates in the first system and selects the function to jump to the second system. After the first system background receives the jump request, it calls the login interface of the first system and passes the user login credentials (such as user name and password). After successfully verifying the user's identity, the login interface of the first system calls the login interface of the second system and passes the user name and password of the second system to the second system.

[0060] Then the first login interface transmits the second user name and the second password of the second system to the second login interface, that is, the first system transmits the user credentials to the second system through the first login interface to complete the login authentication of the second system.

[0061] For example, when a user logs in to the first system A and wants to access the second system B, after logging in to the first system A, the first system can call the first login interface to pass the user name and password of user A to the second login interface of the second system B to wait for the second system B to verify, so that after the verification is passed in the subsequent steps, cross-system login can be realized, and the user can access the second system B without re-entering the user name and password.

[0062] In this step embodiment, verification is completed through a background interface call, thereby ensuring security and accuracy.

[0063] Furthermore, the step S200 specifically includes:

[0064] S201, detecting whether the jump function menu receives an operation instruction to jump to the second system;

[0065] S202. When an operation request to jump to the second system is detected through the jump function menu, control is performed to call the first login interface of the first system background, and the second login interface of the second system is called through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface.

[0066] That is, in the above detailed steps, firstly, S201 is used to detect whether the jump function menu receives an operation instruction to jump to the second system. If such an operation request is detected, S202 will be executed, that is, the first login interface of the first system background is controlled to be called, and the second login interface of the second system is called through the first login interface. In this way, a single sign-on between the two systems is realized.

[0067] S201: Detect whether the jump function menu receives an operation instruction to jump to the second system. This step monitors the user's operation in the first system to see whether there is an instruction to jump to the second system.

[0068] Step S202: When an operation request to jump to the second system is detected, the system controls the call of the first login interface of the first system backend. Through the first login interface, the system calls the second login interface of the second system and transmits the user name and password of the second system to the second login interface.

[0069] For example, when a user selects the function of jumping to the second system in the first system, the present invention will detect this operation request, and automatically call the background interface of the first system, and pass the login information of the user of the second system to the login interface of the second system. Then, the second system will verify the user information and log in the user directly without entering the user name and password.

[0070] It can be seen that the present invention completes login verification through background interface call, which can ensure the security of data transmission and avoid the risk of user information leakage. In addition, the seamless transition of user login helps users quickly switch to the second system, improving work efficiency and convenience.

[0071] Step S300: the second system verifies the second user name and the second password, and returns a small information storage file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the small information storage file cookie to the first system front end and configures it;

[0072] In this step embodiment, as described above, the second system verifies the second user name and the second password, generates a small information storage file (cookie) containing login information, and then returns the cookie to the login interface of the first system. Then, the first login interface sends the cookie to the front end of the first system and configures it so that the user can automatically log in to the second system when accessing the front end of the first system.

[0073] Specifically, when the second system receives the second user name and second password transmitted from the first system, it verifies this information to ensure the authenticity and validity of the user's identity. When the second system passes the verification, it will generate a cookie to store the login information and return it to the login interface of the first system. After receiving the cookie, the first login interface will send it to the front end of the first system, and perform relevant configurations to set the cookie returned by the second login interface of the second system B on the front end of the first system to ensure that the user can automatically log in to the second system when accessing the front end of the first system. Specifically, the front end of the first system obtains the information storage small file cookie with the second user name and second password login information returned by the first login interface A1, and sets the cookie returned by the second login interface of the second system on the front end of the first system.

[0074] For example, after a user logs in through the first system A, he needs to access the second system B. After the backend of the first system A calls the second login interface of the second system B to verify the user, the second system B generates a cookie containing login information and sends it to the backend of the first system A. The backend of the first system A passes this cookie to the frontend of the first system A and configures it to set the cookie returned by the second login interface of the second system B on the frontend of the first system. When the user accesses the second system on the frontend of the first system A, the first system A will automatically carry this cookie to automatically log in to the second system.

[0075] It can be seen that the present invention transmits login information by storing cookies, thereby avoiding the plain text transmission of user names and passwords and improving security. In addition, the present invention transmits login information across systems through cookies, thereby achieving seamless connection between different systems and improving the overall performance and connectivity of the system.

[0076] Furthermore, the step S300 specifically includes:

[0077] S301, after the second system successfully verifies the second user name and the second password, it returns a small information storage file cookie with the second user name and the second password login information to the first login interface;

[0078] S302: The first login interface sends a small information storage file cookie with the second user name and second password login information to the first system front end and configures it to verify whether the user is logged in when jumping to the second system.

[0079] In the detailed step of S300, after successfully verifying the second user name and the second password, the second system returns a small information storage file cookie containing login information to the login interface of the first system. Then, the first login interface sends the cookie with the second user name and the second password login information to the front end of the first system and configures it so as to verify whether the user has logged in when jumping to the second system.

[0080] Specifically, in step S301, after the second system successfully verifies the second user name and the second password, it will create a cookie containing login information and send it to the login interface of the first system. This cookie contains the user's identity authentication information and can help implement the single sign-on function.

[0081] After the login interface of the first system receives the cookie with the second user name and the second password login information in step S302, it will pass it to the front end and perform corresponding configuration to set the cookie returned by the second login interface of the second system B on the front end of the first system. In this way, when the user jumps to the second system, the front end can use this cookie to verify the user's login status, thereby realizing the function of automatically logging into the second system. This avoids writing the user name and password directly in the front end code, thereby improving system security. Moreover, logging in in the background makes user authority control more flexible (authority mapping can be done for users of the two systems according to needs).

[0082] For example, when a user successfully logs in through the first system, the first system A passes the user information of the second system to the second system B for login verification. After the second system B passes the verification, a cookie containing the login information of the second system is generated and returned to the first system A. The first system A sends this cookie to the front end and configures it, and sets the cookie returned by the second login interface of the second system B to the front end of the first system. When the user jumps from the first system A to the second system B, the second system B can verify the user's identity through the cookie and realize the automatic login function.

[0083] In the embodiment of the present invention, by storing information in cookies, the user information is avoided from being transmitted in plain text, thereby improving the security of the system. The user's login status is shared between different systems, reducing the number of repeated logins and improving work efficiency.

[0084] Step S400: The first system accesses the second system by configuring a small information storage file cookie with the second user name and second password login information and successfully verifying the authority of the second system.

[0085] In this step embodiment, the first system stores a small file (cookie) containing the configured second user name and second password login information, and implements the process of accessing the second system after the permission verification of the second system is successful.

[0086] Specifically, when the user successfully logs in to the first system, the first system A will configure a cookie containing the second username and second password login information, that is, the first system will set the cookie returned by the second login interface of the second system B on the front end of the first system. When the user jumps to the second system through the first system, the front end of the first system will carry this cookie and initiate a request to the second system. After receiving the request, the second system will perform a successful permission check and allow the user to access the second system.

[0087] For example, after a user successfully logs in through the first system A, the first system A configures a cookie containing the user login information of the second system. When the user clicks on cross-system login to the second system B in the first system A, the first system A will automatically carry this cookie in the request header and send it to the second system B. After receiving the request, the second system B successfully verifies the user information and allows the user to access the resources of the second system B.

[0088] In the embodiment of the present invention, the user login information is transmitted through cookies, so that seamless login between the two systems is realized, and the user experience is improved. The first system A has already performed user identity authentication when transmitting cookies, and the second system B verifies the user authority again after receiving the request, thereby enhancing system security.

[0089] Furthermore, the step S400 specifically includes:

[0090] S401: The first system front end obtains the information storage small file cookie with the second user name and second password login information returned by the first login interface A1 and is successfully set. The first system initiates an access permission verification request to the second system through the configured information storage small file cookie with the second user name and second password login information;

[0091] S402: The first system is allowed to access the second system through authority verification.

[0092] The above detailed steps involve the first system front end obtaining a small information storage file (cookie) containing the second user name and second password login information, setting it successfully, initiating a permission verification request to the second system through the configured cookie, and the process of the first system accessing the second system after successfully passing the permission verification.

[0093] In step S401, the first system front end successfully obtains the cookie containing the second user name and second password login information, and successfully sets it on the first system front end. Subsequently, the first system initiates a permission verification request to the second system through the configured cookie to verify whether the user has the permission to access the second system.

[0094] Step SS402: After the permission check is passed, the first system obtains the permission to access the second system and successfully accesses the second system. This means that after logging in to the first system, the user can directly access the second system without re-entering the login information, thus achieving convenient cross-system access.

[0095] For example, when a user successfully logs in to the first system A, the first system A sets a cookie containing the login information and sends it to the front end. When the user jumps to the second system B, the front end carries this cookie and initiates a permission verification request to the second system B. After the second system B successfully verifies the user information, it allows the user to access the resources of the second system B.

[0096] In the embodiment of the present invention, users can achieve seamless access between the two systems, providing a more convenient login experience. By storing user information through cookies, the user credentials are avoided from being transmitted in plain text, the security of data is improved, the time of switching logins is saved, and the work efficiency is improved.

[0097] Based on the above embodiment, the present invention further describes in detail a method for processing cross-system login under the same domain name through a specific application embodiment:

[0098] This specific application embodiment provides a method for processing cross-system login under the same domain name. When jumping from system A, a backend interface is first requested. This interface requests the login interface of system B. After successful login, system B returns cookie information. The backend interface then returns this cookie information to the front end. After the front end is successfully set, system B can be directly accessed.

[0099] like Figure 2 As shown, a method for processing cross-system login under the same domain name in this specific application embodiment includes the following steps:

[0100] Step S11: On the first system login interface, enter the first user name userA and the password pwdA to log in to the first system A.

[0101] Step S12, click a function menu to jump to the second system B. In this embodiment, this process first calls the first login interface A1 in the background of the first system A, and the first login interface A1 calls the second login interface B1 of the second system B. The first login interface A1 transmits the second user name useB and password pwdB of the second system B to the second login interface B1. After the second system B verifies the second user name useB and password pwdB, it returns a cookie to the first login interface A1. The first login interface A1 then sends this cookie to the front end. The second system B verifies whether the user has logged in through this cookie.

[0102] Step S13: The front end of the first system A obtains the cookie returned by the first login interface A1 and sets it. Code: Cookies.set(jsession,'******',{expires:365,path:' / b'}).

[0103] Step S14: After the setting is successful, the first system A can access the functions of the second system through authority verification.

[0104] The advantage of the present invention is that it avoids writing the user name and password directly in the front-end code, thereby improving the system security. Moreover, logging in the background makes the user authority control more flexible (authority mapping can be performed for users of the two systems according to the requirements).

[0105] Exemplary Devices

[0106] like Figure 3 As shown, an embodiment of the present invention provides a cross-system login processing device under the same domain name, the device comprising:

[0107] The presetting module 310 is used to pre-register a first user name and password in the first system for allowing login to the first system; and pre-register a second user name and password in the second system for allowing login to the second system; and pre-set a jump function menu for jumping from the first system to the second system;

[0108] The first system login processing module 320 is used to obtain the first user name and password entered into the first system when a cross-system login under the same domain name is required, and log in to the first system using the first user name and the first password;

[0109] The jump login processing module 330 is used to control the calling of the first login interface of the first system background when an operation request to jump to the second system is detected through the jump function menu, and the second login interface of the second system is called through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface;

[0110] The configuration processing module 340 is used to control the second system to verify the second user name and the second password, and return an information storage small file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the information storage small file cookie to the first system front end and performs configuration;

[0111] The jump login verification module 350 is used to control the first system to access the second system through the configured information storage small file cookie with the second user name and second password login information and the successful permission verification in the second system, as described above.

[0112] Based on the above embodiments, the present invention further provides an intelligent terminal, whose principle block diagram can be shown as follows: Figure 4As shown. The intelligent terminal can be a stress test server for stress testing of the Internet production environment, including a processor, a memory, a network interface, a display screen, and a database connected through a system bus. Among them, the processor of the intelligent terminal is used to provide computing and control capabilities. The memory of the intelligent terminal includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface of the intelligent terminal is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a cross-system login processing method under the same domain name is implemented. The database of the intelligent terminal is used to store a cross-system login processing program under the same domain name.

[0113] Those skilled in the art will understand that Figure 4 The principle block diagram shown in the figure is only a block diagram of a partial structure related to the scheme of the present invention, and does not constitute a limitation on the smart terminal to which the scheme of the present invention is applied. The specific smart terminal may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0114] In one embodiment, a smart terminal is provided, comprising a memory and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by one or more processors, and the one or more programs include instructions for performing the following operations:

[0115] When a cross-system login is required under the same domain name, a first user name and a password registered in a first system are obtained, and the first system is logged in using the first user name and the first password;

[0116] When an operation request to jump to the second system is detected through the jump function menu, the first login interface of the first system background is controlled to be called, and the second login interface of the second system is called through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface;

[0117] The second system verifies the second user name and the second password, and returns a small information storage file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the small information storage file cookie to the first system front end and configures it;

[0118] The first system accesses the second system by configuring a small information storage file cookie with the second user name and second password login information and successfully verifying the authority of the second system, as described above.

[0119] Wherein, when a cross-system login is required under the same domain name, the step of obtaining a first user name and a password entered for registration in a first system, and logging into the first system using the first user name and the first password includes:

[0120] A first user name and password pre-registered in the first system for allowing login to the first system;

[0121] And a second user name and password are pre-registered in the second system for allowing login to the second system.

[0122] Wherein, when a cross-system login is required under the same domain name, the step of obtaining a first user name and a password entered for registration in a first system, and logging into the first system using the first user name and the first password includes:

[0123] A jump function menu for jumping from the first system to the second system is preset.

[0124] Wherein, when a cross-system login is required under the same domain name, the step of obtaining a first user name and a password entered for registration in a first system, and logging into the first system using the first user name and the first password includes:

[0125] When a cross-system login is required under the same domain name, the first user name userA and password pwdA registered in the first system are obtained through the login interface of the first system, and the first system is logged in using the first user name and the first password.

[0126] Wherein, when an operation request to jump to the second system is detected through the jump function menu, the first login interface of the first system background is controlled to be called, and the second login interface of the second system is called through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface. The step includes:

[0127] Detecting whether the jump function menu receives an operation instruction to jump to the second system;

[0128] When an operation request to jump to the second system is detected through the jump function menu, the control calls the first login interface of the first system background, and calls the second login interface of the second system through the first login interface; the first login interface transmits the second user name and second password of the second system to the second login interface.

[0129] The second system verifies the second user name and the second password, and returns a small information storage file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the small information storage file cookie to the first system front end and performs configuration, including:

[0130] After the second system successfully verifies the second user name and the second password, it returns a small information storage file cookie with the second user name and the second password login information to the first login interface;

[0131] The first login interface sends a small information storage file cookie with the second user name and second password login information to the first system front end and configures it to verify whether the user is logged in when jumping to the second system.

[0132] The step of sending the cookie containing the information storage small file to the first system front end and configuring the cookie includes:

[0133] The first system front end obtains the information storage small file cookie containing the second user name and second password login information returned by the first login interface A1, and sets the cookie returned by the second login interface of the second system on the first system front end.

[0134] The first system accesses the second system by using a configured information storage small file cookie with the second user name and the second password login information and successfully checking the authority of the second system, including:

[0135] The first system front end obtains the information storage small file cookie with the second user name and second password login information returned by the first login interface A1 and is successfully set. The first system initiates an access permission verification request to the second system through the configured information storage small file cookie with the second user name and second password login information;

[0136] The first system is allowed to access the second system through authority verification, as described above.

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

[0138] In summary, the present invention provides a method, device, intelligent terminal and storage medium for processing cross-system login under the same domain name. When implementing cross-system login under the same domain name, the present invention can first request a background interface when jumping from system A, and this interface requests the login interface of system B. After successful login, system B will return cookie information. The background interface then returns this cookie information to the front end. After the front end is successfully set up, system B can be directly accessed. The present invention implements cross-system login under the same domain name, and the username and password used for login do not need to be written in the front-end page for submission. It has good security and flexible operation, which provides convenience for users. The present invention avoids writing the username and password directly in the front-end code, thereby improving system security. Moreover, logging in in the background makes user authority control more flexible.

Claims

1. A method for processing cross-system login under the same domain name, It is characterized in that include: When a cross-system login is required under the same domain name, a first user name and a password registered in a first system are obtained, and the first system is logged in using the first user name and the first password; When an operation request to jump to the second system is detected through the jump function menu, control to call the first login interface of the first system background, and call the second login interface of the second system through the first login interface; The first login interface transmits the second user name and the second password of the second system to the second login interface; The second system verifies the second user name and the second password, and returns a small information storage file cookie with the second user name and the second password login information to the first login interface; The first login interface sends the small file cookie with the information storage to the first system front end and configures it; The first system accesses the second system by configuring a small information storage file cookie with the second user name and second password login information and successfully verifying the authority of the second system.

2. The method for processing cross-system login under the same domain name according to claim 1, It is characterized in that The step of obtaining a first user name and a password entered into a first system and logging into the first system using the first user name and the first password when a cross-system login under the same domain name is required includes: A first user name and password pre-registered in the first system for allowing login to the first system; And a second user name and password are pre-registered in the second system for allowing login to the second system.

3. The method for processing cross-system login under the same domain name according to claim 1, It is characterized in that The step of obtaining a first user name and a password entered into a first system and logging into the first system using the first user name and the first password when a cross-system login under the same domain name is required includes: A jump function menu for jumping from the first system to the second system is preset.

4. The method for processing cross-system login under the same domain name according to claim 1, It is characterized in that When a cross-system login is required under the same domain name, the step of obtaining a first user name and a password entered for registration in a first system, and logging into the first system using the first user name and the first password comprises: When a cross-system login is required under the same domain name, the first user name userA and password pwdA registered in the first system are obtained through the login interface of the first system, and the first system is logged in using the first user name and the first password.

5. The method for processing cross-system login under the same domain name according to claim 1, It is characterized in that When an operation request to jump to the second system is detected through the jump function menu, the first login interface of the first system background is controlled to be called, and the second login interface of the second system is called through the first login interface; The step of transmitting the second user name and the second password of the second system to the second login interface by the first login interface comprises: Detecting whether the jump function menu receives an operation instruction to jump to the second system; When an operation request to jump to the second system is detected through the jump function menu, the control calls the first login interface of the first system background, and calls the second login interface of the second system through the first login interface; the first login interface transmits the second user name and second password of the second system to the second login interface.

6. The method for processing cross-system login under the same domain name according to claim 1, It is characterized in that The second system verifies the second user name and the second password, and returns a small information storage file cookie with the second user name and the second password login information to the first login interface; The step of sending the cookie with the information storage small file to the first system front end and configuring the first login interface includes: After the second system successfully verifies the second user name and the second password, it returns a small information storage file cookie with the second user name and the second password login information to the first login interface; The first login interface sends a small information storage file cookie with the second user name and second password login information to the first system front end and configures it to verify whether the user is logged in when jumping to the second system.

7. The method for processing cross-system login under the same domain name according to claim 1, It is characterized in that The first system accesses the second system by using a configured information storage small file cookie with the second user name and the second password login information and upon successful permission verification of the second system, the steps include: The first system front end obtains the information storage small file cookie with the second user name and second password login information returned by the first login interface and is successfully set, and the first system initiates an access permission verification request to the second system through the configured information storage small file cookie with the second user name and second password login information; The first system is allowed to access the second system through authority verification.

8. A device for processing logins across systems under the same domain name, It is characterized in that The device comprises: A presetting module is used to pre-register a first user name and password in the first system for allowing login to the first system; and to pre-register a second user name and password in the second system for allowing login to the second system; and to pre-set a jump function menu for jumping from the first system to the second system; A first system login processing module, used for obtaining a first user name and password registered in the first system when a cross-system login under the same domain name is required, and logging into the first system using the first user name and the first password; A jump login processing module, for controlling the calling of a first login interface of the first system background when an operation request for jumping to the second system is detected through the jump function menu, and calling a second login interface of the second system through the first login interface; the first login interface transmits the second user name and the second password of the second system to the second login interface; A configuration processing module is used to control the second system to verify the second user name and the second password, and return an information storage small file cookie with the second user name and the second password login information to the first login interface; the first login interface sends the information storage small file cookie to the first system front end and performs configuration; The jump login verification module is used to control the first system to access the second system through a configured information storage small file cookie with the second user name and second password login information and successful permission verification in the second system.

9. A smart terminal, It is characterized in that The device comprises a memory and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by one or more processors, and the one or more programs include being used to execute the method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium, It is characterized in that When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method as described in any one of claims 1 to 7.