A software login test method and related device

Abstract

The embodiment of the present application provides a software login test method and related devices. The method includes: the operation end sends a configuration instruction to the end to be tested, the end to be tested contains the software to be tested, and the configuration instruction is used to instruct the end to be tested to configure the authentication protocol information required for the software to be tested to log in; the operation end sends a test instruction to the client, and the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server; the client responds to the test instruction and logs in to the software to be tested on the browser, wherein, during the process of the client logging in to the software to be tested on the browser, the client and the end to be tested and the server perform login authentication according to the authentication protocol information. It can be seen that in the embodiment of the present application, the authentication protocol information required for configuring the login of the software to be tested and the automatic login of the software to be tested can be realized, so that when testing the software login, the test cycle can be shortened and the test efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a software login testing method and related devices. Background Art

[0002] With the rapid iteration of software versions, the design of software security is facing greater and greater challenges. Therefore, the verification and testing of software security is becoming more and more important. At present, software (such as baseboard management controller, server full life cycle intelligent management software (Fusion Director), application identity management service software (One Access)) all support client login through network authentication protocol. Among them, the network authentication protocol is a computer network authorization protocol used to authenticate personal communications in a secure way in an insecure network. Its design goal is to log in to the software through a key system to verify the security of the software.

[0003] However, when testing the software, the tester needs to follow the login configuration guide of the network authentication protocol and manually configure the login parameters of the network authentication protocol related to the software. After completing the parameter configuration, the tester needs to manually log in to the software with the account password to complete the security login test of the software. It can be seen that this method completes the security test of the software through manual operation by the user, resulting in a long test cycle for software security authentication and low test efficiency. Summary of the invention

[0004] The embodiment of the present application provides a software login testing method and related devices, which can shorten the test cycle and improve the test efficiency when testing the software login.

[0005] In a first aspect, an embodiment of the present application provides a software login test method, the method comprising:

[0006] The operation end sends a configuration instruction to the end to be tested, which includes the software to be tested. The configuration instruction is used to instruct the end to be tested to configure the authentication protocol information required for the software to be tested to log in.

[0007] The operation end sends a test instruction to the client, which is used to instruct the client to log in to the software to be tested by accessing the browser of the server;

[0008] The client responds to the test instruction and logs in to the software to be tested on the browser. During the process of the client logging in to the software to be tested on the browser, the client, the tested end and the server perform login authentication according to the authentication protocol information.

[0009] In the embodiment of the present application, the operation end can automatically configure the authentication protocol information required for the software to be tested to log in according to the configuration instructions by sending a configuration instruction to the end to be tested; the operation end can automatically log in to the software to be tested according to the test instructions by sending a test instruction to the client. It can be seen that by adopting the embodiment of the present application, when testing the software login, the authentication protocol information required for the software to be tested to log in and the automatic login to the software to be tested can be automatically realized, thereby shortening the test cycle for the software to be tested to log in and improving the test efficiency.

[0010] In an optional implementation, the test instruction includes a server identifier, and the client logs in to the software to be tested by accessing a browser of the server, including:

[0011] The client determines the target server based on the server identifier;

[0012] The client logs in to the software under test by accessing the browser of the target server.

[0013] In this implementation, the client can access different servers based on the server's identification, thereby logging into different browsers to perform software login testing.

[0014] In an optional implementation, the test instruction includes a login method for instructing the client to log in to the software to be tested, and the login method includes a first login method and a second login method;

[0015] The client responds to the test instructions and logs in to the software under test on the browser, including:

[0016] The client determines the login method.

[0017] If it is the first login method, the client, on the browser, simulates clicking the single sign-on button on the login homepage in the web page element through the automation interface to log in to the software under test. The first login method is used to instruct the client to log in to the software under test through the single sign-on login method;

[0018] If it is the second login method, the client selects the domain name through the automation interface on the browser, and enters the account password, simulating clicking the login button on the web page element to log in to the software under test. The second login method is used to instruct the client to log in to the software under test through the local or cross-domain login method.

[0019] In this implementation, the client can perform different network page element operations based on different login methods, thereby logging into the software to be tested based on different operations.

[0020] In an optional implementation, the software to be tested is BMC software, server lifecycle management software or application identity management software, and the authentication protocol information includes function point parameters required for login authentication when the client uses the authentication protocol to log in to the software to be tested.

[0021] In an optional embodiment, the method further includes:

[0022] If the tested end completes configuring the authentication protocol information required for the tested software to log in, a first message is sent to the operating end, where the first message is used to indicate that the authentication protocol information required for the tested software to log in has been configured.

[0023] In this implementation, the operation terminal can clearly know when the authentication protocol information required for logging into the software to be tested is configured, which is beneficial for the operation terminal to perform subsequent operations.

[0024] In an optional embodiment, the method further includes:

[0025] The client sends a login test result for the software to be tested to the operation end according to the login result of the software to be tested, and the login test result includes successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested.

[0026] In this implementation, the client sends the login test result of the software to be tested to the operation end, so that the operation end can clearly know whether the client has successfully logged into the software to be tested. Therefore, when the client fails to successfully log in to the software to be tested, the tester can promptly perform corresponding repair measures through the operation end until the client successfully logs in to the software to be tested.

[0027] In an optional implementation, during the process of the client logging into the software to be tested on the browser, the client, the tested end, and the server perform login authentication according to the authentication protocol information, including:

[0028] The authentication server in the server side responds to the first request message from the client and sends a ticket granting ticket to the client;

[0029] The client sends a second request message to the ticket authorization server in the server, the second request message is used to request to send a service ticket for accessing the terminal to be tested, and the second request message includes a ticket authorization ticket;

[0030] The ticket authorization server in the server responds to the second request message and sends a service ticket to the client;

[0031] The client sends an access request message to the end to be tested, and the access request message includes a service ticket;

[0032] The end to be tested responds to the access request message, checks the content of the service ticket and the identity of the client, and obtains the inspection result;

[0033] The tested end determines whether to approve the client's access based on the inspection result.

[0034] In an optional implementation manner, the ticket authorization server in the server responds to the second request message and sends the service ticket to the client, including:

[0035] The ticket granting server in the server determines whether the user identity in the ticket granting ticket included in the second request message is the same as the requesting user;

[0036] If the user identity is the same as the requesting user, a service ticket is sent to the client.

[0037] In an optional implementation manner, the end to be tested determines whether to approve the access of the client according to the inspection result, including:

[0038] If the check result is that the check passes, the tested end agrees to the client's access and sends a first notification message to the client, where the first notification message is used to notify the client that the login to the tested software is successful;

[0039] If the check result is that the check fails, the tested end denies the client's access and sends a second notification message to the client, where the second notification message is used to notify the client that the login to the tested software fails.

[0040] In this implementation, the end to be tested may send information indicating whether the client has successfully or failed to log into the software to be tested to the client according to the inspection result, so that the client may know whether the software to be tested has been successfully logged into.

[0041] In a second aspect, an embodiment of the present application provides a software login test device, which is used to perform the operation of the operating end in the software login test method described in the first aspect, and the device may include:

[0042] The communication unit is used to send a configuration instruction to the terminal to be tested, where the terminal to be tested includes the software to be tested, and the configuration instruction is used to instruct the terminal to be tested to configure the authentication protocol information required for the software to be tested to log in;

[0043] The communication unit is also used to send a test instruction to the client, where the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server.

[0044] In an optional implementation, the software to be tested is BMC software, server lifecycle management software or application identity management software, and the authentication protocol information includes function point parameters required for login authentication when the client uses the authentication protocol to log in to the software to be tested.

[0045] In an optional implementation, the communication unit is further configured to:

[0046] A login test result for the software to be tested is received from the client, the login test result including successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested. The login test result is determined by the client according to the login result of logging into the software to be tested.

[0047] In a third aspect, an embodiment of the present application provides a software login test device, which is used to perform the operation of the client in the software login test method described in the first aspect, and the device may include:

[0048] The communication unit is used to receive a test instruction from the operation end, and the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server end;

[0049] The processing unit is used to respond to the test instruction and log in the software to be tested on the browser. In the process of the client logging in the software to be tested on the browser, the client and the tested end and the server end perform login authentication according to the authentication protocol information.

[0050] In an optional implementation, the test instruction includes a server identifier, and the processing unit is further configured to log in to the software to be tested by accessing a browser of the server;

[0051] When the processing unit is used to log in to the software under test by accessing the browser of the server, it is specifically used to:

[0052] Determine the target server based on the server identifier;

[0053] Log in to the software under test by accessing the browser of the target server.

[0054] In an optional implementation, the test instruction includes a login method for instructing the client to log in to the software to be tested, and the login method includes a first login method and a second login method;

[0055] When the processing unit is used to respond to the test instruction and log in to the software to be tested on the browser, it is specifically used to:

[0056] Determine the login method.

[0057] If it is the first login method, then on the browser, the single sign-on button in the login homepage element of the network page is simulated to be clicked through the automation interface to log in to the software under test. The first login method is used to instruct the client to log in to the software under test through the single sign-on login method;

[0058] If it is the second login method, on the browser, select the domain name through the automation interface, enter the account password, and simulate clicking the login homepage login button in the network page element to log in to the software under test. The second login method is used to instruct the client to log in to the software under test through the local or cross-domain login method.

[0059] In an optional implementation, the communication unit is further configured to:

[0060] According to the login result of the software to be tested, the login test result for the software to be tested is sent to the operation terminal, and the login test result includes successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested.

[0061] In an optional implementation, during the process of the client logging into the software to be tested on the browser, the client, the tested end, and the server perform login authentication according to the authentication protocol information, including:

[0062] The authentication server in the server side responds to the first request message from the client and sends a ticket granting ticket to the client;

[0063] The client sends a second request message to the ticket authorization server in the server, the second request message is used to request to send a service ticket for accessing the terminal to be tested, and the second request message includes a ticket authorization ticket;

[0064] The ticket authorization server in the server responds to the second request message and sends a service ticket to the client;

[0065] The client sends an access request message to the end to be tested, and the access request message includes a service ticket;

[0066] The end to be tested responds to the access request message, checks the content of the service ticket and the identity of the client, and obtains the inspection result;

[0067] The tested end determines whether to approve the client's access based on the inspection result.

[0068] Optionally, the ticket authorization server in the server responds to the second request message and sends the service ticket to the client, including: the ticket authorization server in the server determines whether the user identity in the ticket authorization ticket included in the second request message is the same as the requesting user; if the user identity is the same as the requesting user, sending the service ticket to the client.

[0069] Optionally, the end to be tested determines whether to approve the client's access based on the inspection result, including:

[0070] If the check result is that the check passes, the tested end agrees to the client's access and sends a first notification message to the client, where the first notification message is used to notify the client that the login to the tested software is successful;

[0071] If the check result is that the check fails, the tested end denies the client's access and sends a second notification message to the client, where the second notification message is used to notify the client that the login to the tested software fails.

[0072] In a fourth aspect, an embodiment of the present application provides a software login test device, which is used to perform the operation of the end to be tested in the software login test method described in the first aspect, and the device may include:

[0073] The communication unit is used to receive a configuration instruction from the operation end, where the configuration instruction is used to instruct the end to be tested to configure the authentication protocol information required for logging into the software to be tested;

[0074] The processing unit is used to respond to the configuration instruction and configure the authentication protocol information required for the software to be tested to log in.

[0075] In an optional implementation, the software to be tested is BMC software, server lifecycle management software or application identity management software, and the authentication protocol information includes function point parameters required for login authentication when the client uses the authentication protocol to log in to the software to be tested.

[0076] In an optional implementation, the communication unit is further configured to:

[0077] If the configuration of the authentication protocol information required for the software to be tested to log in is completed, a first message is sent to the operation terminal, where the first message is used to indicate that the configuration of the authentication protocol information required for the software to be tested to log in is completed.

[0078] In a fifth aspect, an embodiment of the present application provides a software login test system, including an operation terminal, a terminal to be tested and a client, wherein the operation terminal is connected to the terminal to be tested and the client, and the terminal to be tested includes the software to be tested, wherein:

[0079] The operation terminal is used to send configuration instructions to the terminal under test, which includes the software under test. The configuration instructions are used to instruct the terminal under test to configure the authentication protocol information required for the software under test to log in.

[0080] The operation end is used to send a test instruction to the client, and the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server;

[0081] The client is used to respond to the test instruction and log in the software to be tested on the browser. During the process of the client logging in the software to be tested on the browser, the client, the tested end and the server perform login authentication according to the authentication protocol information.

[0082] In the sixth aspect, an embodiment of the present application provides a device, comprising one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program codes, and the computer program codes include computer instructions. When the one or more processors execute the computer instructions, the device executes the steps performed by the operating end in the first aspect above.

[0083] In the seventh aspect, an embodiment of the present application provides a device, comprising one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, and the computer program code includes computer instructions. When the one or more processors execute the computer instructions, the device performs the steps performed by the client in the first aspect above.

[0084] In an eighth aspect, an embodiment of the present application provides a device, comprising one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program codes, and the computer program codes include computer instructions, and when the one or more processors execute the computer instructions, the device performs the steps performed by the end to be tested in the first aspect above. In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising computer instructions, and when the computer instructions are executed on the device, the device performs the operations performed by the operating end or the client or the end to be tested in the first aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] Figure 1 This is an architecture diagram of a software login test system provided in an embodiment of the present application;

[0086] Figure 2 It is a decomposition schematic diagram of a parameter configuration module provided in an embodiment of the present application;

[0087] Figure 3 It is a flowchart of a software login test method provided in an embodiment of the present application;

[0088] Figure 4 It is a schematic diagram of communication between a node service and a hub service provided in an embodiment of the present application;

[0089] Figure 5 It is a flowchart of another software login test method provided in an embodiment of the present application;

[0090] Figure 6It is a schematic diagram of the interaction between a client, a tested environment, and a key distribution center adopted in an embodiment of the present application;

[0091] Figure 7 This is a schematic diagram of a scenario of automated test maintenance provided by an embodiment of the present application;

[0092] Figure 8 It is a structural diagram of a software login test device provided by the present application;

[0093] Fig. 9 It is a structural schematic diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0094] In order to better understand the technical solutions provided by the embodiments of the present application, the relevant embodiments of the present application are described below.

[0095] During the process of logging in the authentication protocol of the software to be tested, it is necessary to first configure the function point parameters required for the authentication protocol login of the software to be tested, and then log in. The embodiment of the present application provides a method for logging in the software to be tested and a related device, which can improve the configuration efficiency of the function point parameters required for the login of the software to be tested, thereby shortening the test cycle for the software to be tested and improving the test efficiency.

[0096] See also Figure 1 , Figure 1 This is an architecture diagram of a software authentication protocol login system provided in an embodiment of the present application. Figure 1 As shown, the authentication protocol login system of the software may include a terminal to be tested 101, a client 102 and an operating terminal 103. Among them, the terminal to be tested 101 refers to the device where the software to be tested is located, that is, the terminal to be tested contains the software to be tested. Optionally, the terminal to be tested includes but is not limited to a server, a virtual machine, a host or a hardware device. The operating terminal 103 can be a local personal computer (personal computer, PC) or a scheduling machine in an automated testing factory. The operating terminal 103 can send a configuration instruction to the terminal to be tested 101, and the configuration instruction is used to instruct the terminal to be tested to configure the authentication protocol information required for the login of the software to be tested. Correspondingly, the terminal to be tested 101 receives the configuration instruction from the operating terminal 103 and configures the authentication protocol information required for the login of the software to be tested. Thereby, the authentication protocol information required for the login of the software to be tested can be automatically configured to improve the configuration efficiency. In addition, the operation end 103 can also send a test instruction to the client 102, and the test instruction is used to instruct the client 102 to log in to the software to be tested by accessing the browser of the server. Accordingly, the client 102 receives the test instruction, responds to the test instruction, and logs in to the software to be tested on the browser. In the process of the client logging in to the software to be tested on the browser, the client and the tested end and the server perform login authentication according to the authentication protocol information.

[0097] The client 102 is provided with hardware or configuration corresponding to the software to be tested, such as an out-of-band controller (Baseboard Management Controller, BMC) or a processor, for example, the software to be tested may be BMC software, server full life cycle management software (Fusion Director), application identity management software (One Access), etc.

[0098] Among them, the authentication protocol information may include the function point parameters required for login authentication when using the authentication protocol to log in to the software to be tested. Optionally, the authentication protocol may be a network authentication protocol Kerberos. Among them, Kerberos is a computer network authorization protocol used to authenticate personal communications in a secure manner in an insecure network. Its design goal is to perform login tests on the software through a key system to verify the security of the software. Optionally, the authentication protocol may also be a Lightweight Directory Access Protocol (LDAP). This application takes the Kerberos authentication protocol as an example to explain the software login test method provided in an embodiment of the present application.

[0099] Optionally, the function point parameters may include but are not limited to a user account and a password. In an optional implementation, the operation end may log in to the client based on the user account and password.

[0100] For example, taking the Kerberos authentication protocol as an example, the authentication protocol information required for the software under test to log in can be the relevant function point parameters required when using Kerberos to log in to the software under test. Figure 2As shown, after the operation terminal 103 logs in to the tested terminal 101 through Redfish or WEB UI, it sends a configuration instruction to the tested terminal 101; accordingly, the tested terminal 101 receives the configuration instruction, and in response to the configuration instruction, sets the function point parameters required when using Kerberos to log in to the tested software one by one. Optionally, the function point parameters required when using Kerberos to log in to the tested software may include Kerberos enable switch, Kerberos domain name, Kerberos server address Internet Protocol (Internet Protocol, IP), Kerberos server port, upload key table file (keytab) key table, Network Time Protocol (Network Time Protocol, NTP) enable switch, Kerberos user group name, software host name, Domain Name System (Domain Name System, DNS) domain name address and IP, NTP server address, Kerberos user group security identifier (Security Identifiers, SID), Kerberos user role, Kerberos user interface authority, Kerberos user login rules, etc. In this way, compared with the test personnel manually configuring the function point parameters required for Kerberos login of the software under test one by one with the help of help documents, the configuration efficiency of the function point parameters required for Kerberos login can be improved.

[0101] The function point parameters mentioned above may include user accounts and passwords. For example, when a client uses Kerberos to log in to the software under test, the user account and password refer to the account and password of the Kerberos domain user. The domain user account refers to an account in a domain controller (DC). Unlike a local account, the domain user account is a network account. Each time you log in with a domain user, you need to verify it on the domain controller. A domain controller refers to at least one server in the "domain" mode that is responsible for the verification of each computer and user connected to the network.

[0102] Optionally, the operation terminal 103 may include a parameter configuration module and a hub service startup module.

[0103] The parameter configuration module is used to send a configuration instruction to the terminal 101 under test, where the configuration instruction is used to instruct the terminal 101 under test to configure the authentication protocol information required for logging into the software under test.

[0104] Optionally, the parameter configuration module is further used to log in to the terminal to be tested 101 through a management standard based on Hypertext Transfer Protocol Security Service (Redfish) or a web user interface (WEB User Interface, WEB UI).

[0105] Optional, above Figure 2 It can be called a decomposition diagram of the parameter configuration module. Figure 2 The description of can be found in the previous article, which will not be repeated here.

[0106] The Hub service startup module is used to send a Hub service operation instruction to the client 102 , and the operation instruction is used to instruct the client 102 to access the browser of the server through the Hub service. The Hub service is deployed in the client 102 .

[0107] Optionally, the client 102 may include a login module.

[0108] The login module is used to log in the software to be tested on the browser in response to the test instruction from the operation terminal 103. The browser is a browser that accesses the server in response to the operation instruction of the Hub service after the client 102 receives the operation instruction of the Hub service from the operation terminal 103. Optionally, the login module can select different browsers to execute different network page element operation instructions according to different test instructions received.

[0109] See also Figure 3 , Figure 3 1 is a flowchart of a software login test method provided in an embodiment of the present application, which can be applied to scenarios where automated testing and maintenance of software is performed. Figure 4 As shown, the method may include but is not limited to the following steps:

[0110] S301. The operating terminal sends a configuration instruction to the terminal to be tested. Correspondingly, the terminal to be tested receives the configuration instruction from the operating terminal. The configuration instruction is used to instruct the terminal to configure the authentication protocol information required for logging into the software to be tested.

[0111] Optionally, the authentication protocol information may include function point parameters required by the client when logging into the software under test using the authentication protocol. Figure 1 The relevant contents in the description will not be repeated here.

[0112] Optionally, the configuration instruction may be a Redfish instruction based on the Hypertext Transfer Protocol Security Service, or a Web interface instruction. The configuration instruction is a programming program stored in the operating terminal that is automatically sent to the terminal to be tested.

[0113] In an optional implementation, before the operating end sends the configuration instruction to the end to be tested, the operating end also logs in to the end to be tested through a management standard based on Hypertext Transfer Protocol Security Service (Redfish) or a web user interface (WEB User Interface, WEBUI).

[0114] Optionally, step S301 may be executed by the parameter configuration module in the aforementioned operation terminal 103 .

[0115] In an optional implementation, after receiving the configuration instruction from the operation terminal, the tested terminal can immediately configure the authentication protocol information required for the tested software to log in. In other words, the tested terminal can configure the authentication protocol information required for the tested software to log in at the moment of receiving the configuration instruction.

[0116] In another optional implementation, after receiving the configuration instruction from the operation end, the end to be tested can configure the authentication protocol information required for the login of the software to be tested within a certain time period (or referred to as the target duration). For example, assuming that the target duration is 5 seconds, the end to be tested can configure the authentication protocol information required for the login of the software to be tested in the 2nd second after receiving the configuration instruction.

[0117] In an optional implementation, if the end to be tested has completed configuring the authentication protocol information required for the software to be tested to log in, a first message may be sent to the operating end, the first message being used to indicate that the function point parameters required for the software to be tested to log in have been configured. Accordingly, the operating end receives the first message. In this way, the operating end can clearly know when the authentication protocol information required for the software to be tested to log in has been configured, so that the operating end can perform subsequent operations, such as the following step S302.

[0118] S302: The operation end sends a test instruction to the client, where the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server.

[0119] In an optional implementation, the test instruction may include information instructing the client to run the Hub service.

[0120] In another optional implementation, the operation end may send a running instruction of the Hub service to the client separately, and the running instruction is used to instruct the client to access the browser of the server. Optionally, the operation end may be executed through the Hub service startup module in the aforementioned operation end 103. In this implementation, the client may access the browser of the server through the Hub service in response to the running instruction of the Hub service. In this way, the client can access the browser based on the running instruction, thereby avoiding the problem of difficulty in starting the browser after switching the client. Optionally, the client accessing the browser of the server through the Hub service may include: starting the Hub service; accessing the browser of the server. Optionally, starting the Hub service may include: starting the Hub service; starting the node Node service, which is a sub-service in the Hub service; registering the Node to the Hub, and establishing communication between the Node and the Hub.

[0121] The communication between Node and Hub can be seen in Figure 4 ,like Figure 4 As shown, the Hub can receive a request message from the client through a fixed port, and the request message is used to request access to the browser of the server; the Hub sends the request message to the Node, and correspondingly, the Node receives the request message from the Hub; the Node responds to the request message, starts the browser and the network page element; the Node returns the execution result to the Hub; the Hub returns the execution result of the Node to the client. Optionally, the network page elements include but are not limited to forms, input boxes, password boxes, text boxes, pictures, radio buttons, check boxes, list boxes, etc.

[0122] In an optional implementation, the test instruction includes a server identifier, and the client logs in to the software to be tested by accessing a browser of the server, which may include: the client determines the target server based on the server identifier; the client logs in to the software to be tested by accessing a browser of the target server. In this way, the client can access different servers based on the server identifier, thereby logging in to different browsers to perform software login testing.

[0123] S303: The client responds to the test instruction and logs into the software to be tested on the browser.

[0124] When the client logs in to the software under test on the browser, the client, the tested end and the server perform login authentication according to the authentication protocol information.

[0125] Optionally, step S303 may be executed by the login module in the aforementioned client 102 .

[0126] In an optional implementation, the client may also send a login test result for the software to be tested to the operation terminal based on the login result of the software to be tested, where the login test result includes successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log into the software to be tested.

[0127] It can be seen that in the embodiment of the present application, the operation end can send a configuration instruction to the end to be tested, so that the end to be tested can automatically configure the function point parameters required for the login of the software to be tested according to the configuration instruction; the operation end can automatically send a test instruction to the client, so that the client can automatically log in to the software to be tested according to the test instruction. It can be seen that by adopting the embodiment of the present application, when testing the software login, the authentication protocol information required for the login of the software to be tested is configured in an automated way by programming, and the login of the software to be tested is automatically realized, which can shorten the test cycle for the login of the software to be tested and improve the test efficiency.

[0128] See also Figure 5 , Figure 51 is a flow chart of another method for logging into the software to be tested provided by an embodiment of the present application. Figure 3 Compared with the method shown, Figure 5 The method shown also specifically describes how the client responds to the test instruction and logs into the software to be tested on the browser. Figure 5 As shown, the method may include but is not limited to the following steps:

[0129] S501, the operation end logs in to the end to be tested through the management standard Redfish based on the Hypertext Transfer Protocol Security Service or the network user interface.

[0130] S502: The operating terminal sends a configuration instruction to the terminal to be tested. Correspondingly, the terminal to be tested receives the configuration instruction from the operating terminal. The configuration instruction is used to instruct the terminal to configure the authentication protocol information required for logging into the software to be tested.

[0131] S503: The terminal to be tested responds to the configuration instruction and configures the authentication protocol information required for logging into the software to be tested.

[0132] S504: If the tested end has completed configuring the authentication protocol information required for the tested software to log in, a first message is sent to the operating end, where the first message is used to indicate that the authentication protocol information required for the tested software to log in has been configured.

[0133] S505: The operation end sends a test instruction to the client, and correspondingly, the client receives the test instruction, which includes a login method for instructing the client to log in to the software to be tested.

[0134] The test command is used to instruct the client to log in to the software to be tested by accessing the browser of the server.

[0135] In an optional implementation, before the client receives the running instruction of the hub service from the operation end, it may also receive the user account and password from the operation end.

[0136] S506. The client determines the login method for logging into the software to be tested. If it is the first login method, execute step S507a; if it is the second login method, execute step S507b.

[0137] Among them, the first login method is used to instruct the client to log in to the software to be tested through the single sign-on (SSO) login method. Single sign-on means that in multiple application systems, users only need to log in once to access all mutually trusted application systems. For example, when a user accesses application 1 for the first time, because he has not logged in yet, he will be guided to the authentication system to log in. After that, the authentication system will verify his identity based on the login information provided by the user. If the verification is passed, a certified ticket will be returned to the user. In this way, when the user accesses application 2 again, he will carry the ticket as the credential for his own authentication. When the application system receives the user's request to access the application, it will send the ticket to the authentication system so that the authentication system can verify the ticket and check the legitimacy of the ticket. If the verification is passed, the user can directly access application 2 without logging in again.

[0138] The second login method is used to instruct the client to log in to the software under test through the login method of local domain / cross-domain user domain name login. Among them, the local domain refers to a domain with the same domain name, the same port, and the same protocol. For example, "http: / / 1234.com:xx" and "http: / / 1234.com:xx / course / list". Cross-domain means that at least one of the domain name, port, and protocol is different. For example, "http: / / 1234.com:xx / course / list" and "http: / / www.1234.com:xxxy / course / list".

[0139] S507a: The client, on the browser, simulates clicking a single sign-on button on the login homepage in a web page element through an automation interface to log in to the software to be tested.

[0140] S507b, the client selects the domain name through the automation interface on the browser, enters the account password, and simulates clicking the login homepage login button in the network page element to log in to the software to be tested.

[0141] Optionally, steps S507a and S507b may be performed by Figure 1 The login module in the client 102 executes.

[0142] It can be seen from step S507a and step S507b that no matter it is the first login method or the second login method, the client can automatically log in to the software to be tested in the browser through the network page operation elements, that is, the client can automatically perform the authentication protocol login function of the software to be tested without the need for manual operation by the tester.

[0143] In an optional implementation, during the process of the client logging into the software under test on the browser, the client, the end under test, and the server perform login authentication according to the authentication protocol information. That is, when the client logs into the software under test through the authentication protocol, no matter which login method in the above steps S507a and S507b is used by the client, in the process of logging into the software under test, there will be interaction between the client, the end under test, and the server for login authentication.

[0144] In this implementation, the client and the end to be tested and the server perform login authentication according to the authentication protocol information, which may include: the identity authentication server in the server responds to the first request message from the client and sends a ticket authorization ticket to the client; the client sends a second request message to the ticket authorization server in the server, the second request message is used to request to send a service ticket for accessing the end to be tested, and the second request message includes the ticket authorization ticket; the ticket authorization server in the server responds to the second request message and sends the service ticket to the client; the client sends an access request message to the end to be tested, and the access request message includes the service ticket; the end to be tested responds to the access request message, checks the content of the service ticket and the identity of the client, and obtains the inspection result; the end to be tested determines whether to agree to the client's access based on the inspection result.

[0145] In this implementation, the ticket authorization server in the server responds to the second request message and sends a service ticket to the client, which may include: the ticket authorization server in the server determines whether the user identity in the ticket authorization ticket included in the second request message is the same as the requesting user; if the user identity is the same as the requesting user, the service ticket is sent to the client.

[0146] In this implementation, the end to be tested determines whether to approve the client's access based on the inspection result, which may include: if the inspection result is that the inspection is passed, the end to be tested approves the client's access and sends a first notification message to the client, the first notification message is used to notify the client that the login to the software to be tested is successful; if the inspection result is that the inspection is not passed, the end to be tested denies the client's access and sends a second notification message to the client, the second notification message is used to notify the client that the login to the software to be tested fails. In this way, the client can know whether the login to the software to be tested is successful based on the indication information from the end to be tested.

[0147] See also Figure 6 , Figure 6It is a schematic diagram of the interaction between a client, a tested environment, and a key distribution center adopted by an embodiment of the present application. Among them, the tested environment is the aforementioned end to be tested, and the domain controller (Domain Controller, DC) includes a key distribution center (Key Distribution Center, KDC) (corresponding to the aforementioned server) and an account database (Account Database, AD). KDC includes an authentication server (Authentication Service, AS) and a ticket granting server (Ticket Granting Service, TGS), wherein AS is used to perform initial user identity authentication and issue a ticket granting ticket (Ticket Granting Ticket, TGT) to the user; TGS is used to issue a service ticket based on the initial TGT. A whitelist of all clients is stored in AD, and only clients that exist in the whitelist can successfully apply for TGT.

[0148] Below Figure 6 The interaction process in the example is briefly described, and the interaction process may include the following steps:

[0149] (1) The client sends a first request message to the AS in the KDC. In response, the AS receives the first request message, which is used to request a TGT.

[0150] The TGT is the client's permission to access the tested environment.

[0151] (2) The AS responds to the first request message and sends a TGT to the client. Correspondingly, the client receives the TGT.

[0152] After receiving the first request message, AS will first determine whether the client is trustworthy based on the data stored in AD, that is, determine whether the client's identity information exists in AD; if it is determined that the client's identity information exists in AD, it will send TGT to the client.

[0153] (3) The client sends a second request message to the TGS. Accordingly, the TGS receives the second request message. The second request is used to request to send a service ticket (Server Ticket) for accessing the software service under test. The second request message includes a TGT.

[0154] (4) If the TGS determines that the user identity in the TGT is the same as the requesting user, it sends a ServerTicket to the client, and the client receives the ServerTicket accordingly.

[0155] (5) The client sends an access request message to the end-to-be-tested. The access request message includes a Server Ticket.

[0156] (6) The end-to-be-tested responds to the access request message and checks the contents of the Server Ticket and the identity of the client.

[0157] In an optional implementation, before checking the content of the Server Ticket and the identity of the client, the tested end also checks whether there is the service IP requested by the client.

[0158] In an optional implementation, the end to be tested may determine whether to agree to the client's access based on the inspection result. Optionally, if the inspection result is that the inspection is passed, the end to be tested agrees to the client's access and establishes a connection with the client. At this time, the end to be tested may also send a first notification message to the client, and the first notification message is used to notify the client that the software to be tested has successfully logged in. If the inspection result is that the inspection fails, the end to be tested may reject the client's access and does not establish a connection with the client. At this time, the end to be tested may send a second notification message to the client, and the second notification message is used to notify the client that the software to be tested has failed to log in. Optionally, the second notification message may include the reason for the failure to log in to the software to be tested, etc. In other words, only when the end to be tested agrees to the client's access, can the client successfully log in to the software to be tested, and then test the software to be tested.

[0159] It can be seen that by adopting the embodiment of the present application, the client can automatically perform different operations based on the network page elements in the browser according to different test instructions from the operation end, thereby improving the login efficiency, and further when testing the software, the test cycle can be shortened and the test efficiency can be improved.

[0160] In addition, by adopting the embodiments of the present application, it is also possible to avoid damage to the test environment due to the lack of experience of the testers, thereby avoiding the need to repair the test environment, thereby saving time costs.

[0161] The embodiment of the present application only needs to deploy the Redfish and WEB framework tools required by the above solution, as well as programming implementation, to automatically realize the login of the software to be tested. On the one hand, it can shorten the test cycle and greatly improve the test efficiency; on the other hand, it can save manpower and reduce test expenses.

[0162] Optionally, the method provided in the embodiment of the present application can be applied to the scenario of automated test maintenance. Figure 7 , Figure 7 Schematic diagram of an automated test maintenance scenario provided by an embodiment of the present application. Figure 7 As shown, an environment for generating a host key table corresponding to a Kerberos service can be selected from an environment resource pool through an automated environment scheduling system, and then the above Figure 5The steps shown. Among them, the execution scheduling machine can correspond to the aforementioned operating terminal; the connected environment refers to the environment of the software to be tested, that is, the aforementioned terminal to be tested. It can be seen that the embodiment of the present application can cover all Kerberos authentication login scenarios. When in a large-scale connection environment, it cooperates with the upper-level scheduling system to simultaneously test and verify the environments of multiple software to be tested, and improves the test efficiency through parallel testing.

[0163] Optionally, the tester can also integrate the tools and codes required to implement the above method into the automated task system to form an intelligent solution with the function of detecting the health status of the Kerberos server.

[0164] See also Figure 8 , Figure 8 This is a schematic diagram of the structure of a software login test device provided by this application. Figure 8 As shown, the device may include but is not limited to a communication unit 801 and a processing unit 802 .

[0165] In an optional implementation, the device may be used to execute the operations of the operating end in the above-mentioned software login test method.

[0166] For example:

[0167] The communication unit 801 is used to send a configuration instruction to the terminal to be tested, where the terminal to be tested includes the software to be tested, and the configuration instruction is used to instruct the terminal to be tested to configure the authentication protocol information required for the software to be tested to log in;

[0168] The communication unit 801 is further used to send a test instruction to the client, where the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server.

[0169] In this implementation, the software to be tested is BMC software, server lifecycle management software or application identity management software, and the authentication protocol information includes function point parameters required for login authentication when the client uses the authentication protocol to log in to the software to be tested.

[0170] In this implementation, the communication unit 801 is further used for:

[0171] A login test result for the software to be tested is received from the client, the login test result including successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested. The login test result is determined by the client according to the login result of logging into the software to be tested.

[0172] In another optional implementation, the device can be used to perform the client operation in the above software login test method. For example:

[0173] The communication unit 801 is used to receive a test instruction from the operation end, and the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server end;

[0174] The processing unit 802 is used to respond to the test instruction and log in the software to be tested on the browser. In the process of the client logging in the software to be tested on the browser, the client, the tested end and the server perform login authentication according to the authentication protocol information.

[0175] In this implementation, the test instruction includes a server identifier, and the processing unit 802 is further configured to log in to the software to be tested by accessing a browser on the server;

[0176] When the processing unit 802 is used to log in to the software to be tested by accessing the browser of the server, it is specifically used to:

[0177] Determine the target server based on the server identifier;

[0178] Log in to the software under test by accessing the browser of the target server.

[0179] In this implementation, the test instruction includes a login method for instructing the client to log in to the software to be tested, and the login method includes a first login method and a second login method;

[0180] When the processing unit 802 is used to respond to the test instruction and log in to the software to be tested on the browser, it is specifically used to:

[0181] Determine the login method.

[0182] If it is the first login method, then on the browser, the single sign-on button in the login homepage element of the network page is simulated to be clicked through the automation interface to log in to the software under test. The first login method is used to instruct the client to log in to the software under test through the single sign-on login method;

[0183] If it is the second login method, on the browser, select the domain name through the automation interface, enter the account password, and simulate clicking the login homepage login button in the network page element to log in to the software under test. The second login method is used to instruct the client to log in to the software under test through the local or cross-domain login method.

[0184] In this implementation, the communication unit 801 is further used for:

[0185] According to the login result of the software to be tested, the login test result for the software to be tested is sent to the operation terminal, and the login test result includes successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested.

[0186] In this implementation, during the process of the client logging into the software to be tested on the browser, the client, the tested end and the server perform login authentication according to the authentication protocol information, including:

[0187] The authentication server in the server side responds to the first request message from the client and sends a ticket granting ticket to the client;

[0188] The client sends a second request message to the ticket authorization server in the server, the second request message is used to request to send a service ticket for accessing the terminal to be tested, and the second request message includes a ticket authorization ticket;

[0189] The ticket authorization server in the server responds to the second request message and sends a service ticket to the client;

[0190] The client sends an access request message to the end to be tested, and the access request message includes a service ticket;

[0191] The end to be tested responds to the access request message, checks the content of the service ticket and the identity of the client, and obtains the inspection result;

[0192] The tested end determines whether to approve the client's access based on the inspection result.

[0193] Optionally, the ticket authorization server in the server responds to the second request message and sends the service ticket to the client, including: the ticket authorization server in the server determines whether the user identity in the ticket authorization ticket included in the second request message is the same as the requesting user; if the user identity is the same as the requesting user, sending the service ticket to the client.

[0194] Optionally, the end to be tested determines whether to approve the client's access based on the inspection result, including:

[0195] If the check result is that the check passes, the tested end agrees to the client's access and sends a first notification message to the client, where the first notification message is used to notify the client that the login to the tested software is successful;

[0196] If the check result is that the check fails, the tested end denies the client's access and sends a second notification message to the client, where the second notification message is used to notify the client that the login to the tested software fails.

[0197] In another optional implementation, the device can be used to perform the operation of the terminal to be tested in the above software login test method. For example:

[0198] The communication unit 801 is used to receive a configuration instruction from the operation terminal, where the configuration instruction is used to instruct the tested terminal to configure the authentication protocol information required for logging into the tested software;

[0199] The processing unit 802 is used to respond to the configuration instruction and configure the authentication protocol information required for the software to be tested to log in.

[0200] In this implementation, the software to be tested is BMC software, server lifecycle management software or application identity management software, and the authentication protocol information includes function point parameters required for login authentication when the client uses the authentication protocol to log in to the software to be tested.

[0201] In this implementation, the communication unit 801 is further used for:

[0202] If the configuration of the authentication protocol information required for the software to be tested to log in is completed, a first message is sent to the operation terminal, where the first message is used to indicate that the configuration of the authentication protocol information required for the software to be tested to log in is completed.

[0203] It can be understood that the specific implementation of each unit in the software login test device provided in the embodiment of the present application and the beneficial effects that can be achieved can be referred to the description of the aforementioned software login test method embodiment, and will not be repeated here.

[0204] See also Fig. 9 , Fig. 9 9 is a schematic diagram of a structure of a device provided in an embodiment of the present application, which includes a processor 901, a memory 902 and a transceiver 903.

[0205] The processor 901, the memory 902 and the transceiver 903 may be connected via a bus, which may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0206] The transceiver 903 is used to receive and send data.

[0207] The memory 902 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or portable read-only memory (CD-ROM), and is used to store executed computer programs or instructions and transmitted data.

[0208] The processor 901 may be one or more central processing units (CPUs). When the processor 901 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0209] In an optional implementation, the processor 901 may be used to call a computer program or instruction stored in the memory 902 to perform the operation of the operating end in the above software login test method, for example:

[0210] Sending a configuration instruction to the end to be tested, the end to be tested includes the software to be tested, and the configuration instruction is used to instruct the end to be tested to configure the authentication protocol information required for the software to be tested to log in;

[0211] Send a test instruction to the client, which is used to instruct the client to log in to the software under test by accessing the browser of the server.

[0212] In this implementation, the software to be tested is BMC software, server lifecycle management software or application identity management software, and the authentication protocol information includes function point parameters required for login authentication when the client uses the authentication protocol to log in to the software to be tested.

[0213] In this implementation, the processor 901 is further configured to:

[0214] A login test result for the software to be tested is received from the client, the login test result including successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested. The login test result is determined by the client according to the login result of logging into the software to be tested.

[0215] In another optional implementation, the processor 901 may be used to call a computer program or instruction stored in the memory 902 to execute the client operation in the above software login test method, for example:

[0216] Receive a test instruction from the operation end, the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server end;

[0217] In response to the test instruction, the software to be tested is logged in on the browser. During the process of the client logging in to the software to be tested on the browser, the client, the tested end and the server perform login authentication according to the authentication protocol information.

[0218] In this implementation, the test instruction includes a server identifier, and the processor 901 is further configured to log in to the software to be tested by accessing a browser on the server;

[0219] When executing the operation of logging into the software to be tested by accessing the browser of the server, the processor 901 specifically performs:

[0220] Determine the target server based on the server identifier;

[0221] Log in to the software under test by accessing the browser of the target server.

[0222] In this implementation, the test instruction includes a login method for instructing the client to log in to the software to be tested, and the login method includes a first login method and a second login method;

[0223] When the processor 901 executes the operation of responding to the test instruction and logging into the software to be tested on the browser, it specifically performs the following steps:

[0224] Determine the login method.

[0225] If it is the first login method, then on the browser, the single sign-on button in the login homepage element of the network page is simulated to be clicked through the automation interface to log in to the software under test. The first login method is used to instruct the client to log in to the software under test through the single sign-on login method;

[0226] If it is the second login method, on the browser, select the domain name through the automation interface, enter the account password, and simulate clicking the login homepage login button in the network page element to log in to the software under test. The second login method is used to instruct the client to log in to the software under test through the local or cross-domain login method.

[0227] In this implementation, the processor 901 further executes:

[0228] According to the login result of the software to be tested, the login test result for the software to be tested is sent to the operation terminal, and the login test result includes successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested.

[0229] In this implementation, during the process of the client logging into the software to be tested on the browser, the client, the tested end and the server perform login authentication according to the authentication protocol information, including:

[0230] The authentication server in the server side responds to the first request message from the client and sends a ticket granting ticket to the client;

[0231] The client sends a second request message to the ticket authorization server in the server, the second request message is used to request to send a service ticket for accessing the terminal to be tested, and the second request message includes a ticket authorization ticket;

[0232] The ticket authorization server in the server responds to the second request message and sends a service ticket to the client;

[0233] The client sends an access request message to the end to be tested, and the access request message includes a service ticket;

[0234] The end to be tested responds to the access request message, checks the content of the service ticket and the identity of the client, and obtains the inspection result;

[0235] The tested end determines whether to approve the client's access based on the inspection result.

[0236] Optionally, the ticket authorization server in the server responds to the second request message and sends the service ticket to the client, including: the ticket authorization server in the server determines whether the user identity in the ticket authorization ticket included in the second request message is the same as the requesting user; if the user identity is the same as the requesting user, sending the service ticket to the client.

[0237] Optionally, the end to be tested determines whether to approve the client's access based on the inspection result, including:

[0238] If the check result is that the check passes, the tested end agrees to the client's access and sends a first notification message to the client, where the first notification message is used to notify the client that the login to the tested software is successful;

[0239] If the check result is that the check fails, the tested end denies the client's access and sends a second notification message to the client, where the second notification message is used to notify the client that the login to the tested software fails.

[0240] In another optional implementation, the processor 901 may be used to call a computer program or instruction stored in the memory 902 to execute the operation of the terminal under test in the above software login test method, for example:

[0241] Receive a configuration instruction from the operation end, the configuration instruction is used to instruct the tested end to configure the authentication protocol information required for logging into the tested software;

[0242] Respond to the configuration instructions and configure the authentication protocol information required for the software under test to log in.

[0243] In this implementation, the software to be tested is BMC software, server lifecycle management software or application identity management software, and the authentication protocol information includes function point parameters required for login authentication when the client uses the authentication protocol to log in to the software to be tested.

[0244] In this implementation, the processor 901 is further configured to execute:

[0245] If the configuration of the authentication protocol information required for the software to be tested to log in is completed, a first message is sent to the operation terminal, where the first message is used to indicate that the configuration of the authentication protocol information required for the software to be tested to log in is completed.

[0246] It is understandable that the specific implementation of the processor 901 and the beneficial effects that can be achieved can be referred to the description of the aforementioned software login test method embodiment, which will not be repeated here.

[0247] Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

[0248] The present application also provides a computer-readable storage medium on which a computer program is stored. The computer program includes program instructions, and when the program instructions are executed by a computer, the functions of any of the above method embodiments are implemented.

[0249] The computer-readable storage medium includes but is not limited to a flash memory, a hard disk, and a solid-state drive.

[0250] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0251] The scheme described in the present application can be implemented in various ways. For example, these technologies can be implemented in hardware, software or a combination of hardware. For hardware implementation, the processing unit used to execute these technologies at the relevant device can be implemented in one or more general-purpose processors, digital signal processors (digital signal processor, DSP), digital signal processing devices, application specific integrated circuits (application specific integrated circuit, ASIC), programmable logic devices, field programmable gate arrays (field programmable gate array, FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any traditional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0252] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The device or computing device involved in the embodiment of the present application can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.

[0253] In this application, elements expressed in the singular are intended to mean "one or more" rather than "one and only one", unless otherwise specified. In this application, "at least one" is intended to mean "one or more", and "more than one" is intended to mean "two or more", unless otherwise specified.

[0254] In addition, the term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. A can be singular or plural, and B can be singular or plural.

[0255] Those skilled in the art will appreciate that, for the sake of convenience and brevity of description, the specific working processes of the systems, devices and units described above may refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0256] The same or similar parts between the various embodiments in this application can refer to each other. In the various embodiments in this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of this application do not constitute a limitation on the scope of protection of this application.

Claims

1. A software login test method, characterized in that: The method comprises: The operation end logs in to the end to be tested through the management standard or network user interface based on the Hypertext Transfer Protocol Security Service; The operation end sends a configuration instruction to the end to be tested, the end to be tested includes the software to be tested, and the configuration instruction is used to instruct the end to be tested to configure the authentication protocol information required for the software to be tested to log in; the end to be tested responds to the configuration instruction and sets the function point parameters required when using the authentication protocol to log in to the software to be tested; the authentication protocol is the network authentication protocol Kerberos, and the authentication protocol information is the function point parameters required when using the authentication protocol to log in to the software to be tested; The operation end sends a test instruction to the client, wherein the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server; The client responds to the test instruction and logs in the software to be tested on the browser. During the process of the client logging in the software to be tested on the browser, the client performs login authentication with the tested end and the server according to the authentication protocol information.

2. The method according to claim 1, characterized in that The test instruction includes a server identification, and the client logs in to the software to be tested by accessing a browser of the server, including: The client determines a target server based on the server identifier; The client logs in to the software to be tested by accessing the browser of the target server.

3. The method according to claim 1, characterized in that The test instruction includes a login method for instructing the client to log in to the software to be tested, and the login method includes a first login method and a second login method; The client responds to the test instruction and logs in to the software to be tested on the browser, including: The client determines the login method, If it is the first login method, the client, on the browser, simulates clicking a single sign-on button in a web page element through an automation interface to log in to the software under test. The first login method is used to instruct the client to log in to the software under test through a single sign-on login method; If it is the second login method, the client selects the domain name on the browser through the automation interface and enters the account password, simulating clicking the login homepage login button in the network page element to log in to the software under test. The second login method is used to instruct the client to log in to the software under test through the local domain or cross-domain login method.

4. The method according to claim 1, characterized in that The software to be tested is BMC software, server full life cycle management software or application identity management software.

5. The method according to claim 1, characterized in that The method further comprises: If the tested end has completed configuring the authentication protocol information required for the tested software to log in, a first message is sent to the operating end, where the first message is used to indicate that the authentication protocol information required for the tested software to log in has been configured.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The client sends a login test result for the software to be tested to the operating end according to the login result of the software to be tested, and the login test result includes successful login to the software to be tested, failed login to the software to be tested, and the reason for the failure to log in to the software to be tested.

7. The method according to claim 1, characterized in that In the process of the client logging into the software to be tested on the browser, the client, the end to be tested and the server perform login authentication according to the authentication protocol information, including: The identity verification server in the server sends a ticket authorization ticket to the client in response to the first request message from the client; The client sends a second request message to the ticket authorization server in the server, where the second request message is used to request to send a service ticket for accessing the terminal to be tested, and the second request message includes the ticket authorization ticket; The ticket authorization server in the server sends the service ticket to the client in response to the second request message; The client sends an access request message to the end to be tested, wherein the access request message includes the service ticket; The end to be tested responds to the access request message, checks the content of the service ticket and the identity of the client, and obtains a check result; The tested end determines whether to approve the access of the client according to the checking result.

8. The method according to claim 7, characterized in that The ticket authorization server in the server responds to the second request message and sends the service ticket to the client, including: The ticket granting server in the server determines whether the user identity in the ticket granting ticket included in the second request message is the same as the requesting user; If the user identity is the same as the requesting user, the service ticket is sent to the client.

9. The method according to claim 7, characterized in that The end to be tested determines whether to approve the access of the client according to the inspection result, including: If the check result is that the check is passed, the tested end agrees to the access of the client and sends a first notification message to the client, where the first notification message is used to notify the client that the login to the tested software is successful; If the check result is that the check fails, the tested end denies the access of the client and sends a second notification message to the client, where the second notification message is used to notify the client that the login to the tested software fails.

10. A software login test system, characterized in that: It includes an operation terminal, a terminal to be tested and a client, wherein the operation terminal is connected to the terminal to be tested and the client, and the terminal to be tested includes software to be tested, wherein: The operation terminal is used to log in to the terminal to be tested through a management standard or a network user interface based on a hypertext transfer protocol security service; The operation terminal is also used to send a configuration instruction to the terminal to be tested, the terminal to be tested includes the software to be tested, and the configuration instruction is used to instruct the terminal to be tested to configure the authentication protocol information required for the software to be tested to log in; the terminal to be tested responds to the configuration instruction and sets the function point parameters required when using the authentication protocol to log in to the software to be tested; the authentication protocol is the network authentication protocol Kerberos, and the authentication protocol information is the function point parameters required when using the authentication protocol to log in to the software to be tested; The operation end is used to send a test instruction to the client, and the test instruction is used to instruct the client to log in to the software to be tested by accessing the browser of the server; The client is used to respond to the test instruction and log in the software to be tested on the browser. During the process of the client logging in the software to be tested on the browser, the client performs login authentication with the tested end and the server according to the authentication protocol information.

Images