CN117812091A - Account information synchronization method and device, storage medium and electronic device - Google Patents

Abstract

The embodiment of the application provides an account information synchronization method, an account information synchronization device, a storage medium and an electronic device, wherein the method comprises the following steps: under the condition that the first baseboard management controller BMC determines that the account information of the second BMC needs to be set, randomly generating target account information; according to a uniform resource locator URL preset by the second BMC, sending a request for requesting to configure account information of the second BMC as the target account information to the second BMC; and under the condition that a message sent by the second BMC and used for indicating that the account information of the second BMC is configured as the target account information is received, communicating with the second BMC by using the target account information.

Description

Account information synchronization method and device, storage medium and electronic device

Technical Field

The embodiment of the application relates to the field of computers, in particular to an account information synchronization method, an account information synchronization device, a storage medium and an electronic device.

Background

When a plurality of BMCs related to the related art communicate with each other, a specific user name and a specific password are adopted for communication, for example, a machine head BMC (Baseboard Management Controller, a baseboard management controller) and a GPU BOX (Graphics Processing Unit Box, a graphics processor BOX) end BMC adopt fixed user names and passwords when communicating through a network, namely, one user name and one password are set at the BOX end BMC without modification, the user names and the passwords are written into the machine head BMC, and the machine head BMC communicates with the BOX end BMC each time by using the user names and the passwords to acquire related information of the BMC at the BOX end. Under the condition that the user name and the password are revealed, other devices can directly log in the BOX end BMC through the user name and the password to acquire related information, so that the problem of lower safety is caused.

In view of the above problems in the related art, no effective solution has been proposed at present.

Disclosure of Invention

The embodiment of the application provides an account information synchronization method, an account information synchronization device, a storage medium and an electronic device, which are used for at least solving the problem that in the related art, the security of the terminal BMC is lower due to the fact that the account information of the terminal BMC is not changed and the data security of the terminal BMC is affected under the condition that the account information is revealed.

According to one embodiment of the present application, there is provided an account information synchronization method, including: under the condition that the first baseboard management controller BMC determines that the account information of the second BMC needs to be set, randomly generating target account information; according to a uniform resource locator URL preset by the second BMC, sending a request for requesting to configure account information of the second BMC as the target account information to the second BMC; the second BMC is received to send the indication that the first BMC is already used; and under the condition that the account information of the BMC is configured as the message of the target account information, the target account information is used for communicating with the second BMC.

In one exemplary embodiment, before randomly generating the target account information, the method further comprises: determining whether the first BMC needs to set the account information of the second BMC or not by the following method; acquiring a value of a target zone bit preset in the first BMC; under the condition that the value of the target zone bit is a first value, determining that the first BMC needs to set account information of a second BMC; and under the condition that the value of the target zone bit is a second value, determining that the first BMC does not need to set account information of the second BMC.

In an exemplary embodiment, before communicating with the second BMC using the target account information, the method further comprises: receiving a message sent by the second BMC, wherein the message is used for indicating that the account information of the second BMC is configured as the target account information; and updating the value of the target zone bit in the first BMC to a second value.

In an exemplary embodiment, the method further comprises: and updating the value of the target zone bit to the first value under the condition that the time length for setting the value of the target zone bit to the second value reaches the target time length or the communication between the first BMC and the second BMC is interrupted.

In an exemplary embodiment, after communicating with the second BMC using the target account information, the method further comprises: acquiring target information of the second BMC; and displaying the target information of the second BMC on the first BMC side.

In an exemplary embodiment, the method further comprises: the second BMC receives a request message from a target device based on the preset URL, wherein the URL is integrated in a target redfish process of the second BMC, and the target redfish process is used for monitoring received network data in real time, analyzing the network data and distributing the network data based on an analysis result; the second BMC acquires a header of the request message and an IP address of the target device, and determines whether the target device is the first BMC according to the header and the IP address; the second BMC analyzes the request message to obtain request content contained in the request message under the condition that the target device is determined to be the first BMC; the second BMC stores the target account information and configures the account information of the second BMC as the target account information under the condition that the request content comprises the content for requesting the account information of the second BMC to be configured as the target account information; and the second BMC sends a response message for indicating that the account information of the second BMC is configured as the target account information to the target equipment.

In an exemplary embodiment, the second BMC storing the target account information includes: and under the condition that the target account information comprises a user name and a password, the second BMC stores the target account information in a user name password list pre-established in the second BMC in a local session mode.

According to another embodiment of the present application, there is provided an account information synchronizing device, including: the generation module is used for randomly generating target account information under the condition that the first baseboard management controller BMC determines that the account information of the second BMC needs to be set; the first sending module is used for sending a request for requesting to configure the account information of the second BMC to the target account information to the second BMC according to a uniform resource locator URL preset by the second BMC; and the communication module is used for communicating with the second BMC by using the target account information under the condition that the message sent by the second BMC and used for indicating that the account information of the second BMC is configured as the target account information is received.

According to a further embodiment of the present application, there is also provided a computer readable storage medium having stored therein a computer program, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

According to a further embodiment of the present application, there is also provided an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

According to the method and the device, the target account information can be randomly generated by one end BMC included in the associated plurality of BMCs and sent to the other end BMC for configuration, so that the account information can be flexibly and synchronously updated among the plurality of BMCs, and therefore the problem that the data security of the end BMC is affected under the condition that the account information is revealed due to the fact that the account information of the end BMC is unchanged in the related technology can be solved, the problem that the security of the end BMC is lower is caused, and the effect of improving the security of the BOX end BMC is achieved.

Drawings

Fig. 1 is a hardware configuration block diagram of a server device of an account information synchronization method according to an embodiment of the present application;

fig. 2 is a flowchart one of an account information synchronization method according to an embodiment of the present application;

fig. 3 is a second flowchart of an account information synchronization method according to an embodiment of the present application;

fig. 4 is a flowchart III of an account information synchronization method according to an embodiment of the present application;

fig. 5 is a block diagram of a configuration of an account information synchronizing device according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in detail below with reference to the accompanying drawings in conjunction with the embodiments.

It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

The method embodiments provided in the embodiments of the present application may be performed in a server device or similar computing device. Taking the operation on the server device as an example, fig. 1 is a hardware structural block diagram of the server device of the account information synchronization method in the embodiment of the present application. As shown in fig. 1, the server device may include one or more (only one is shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a microprocessor MCU, a programmable logic device FPGA, or the like processing means) and a memory 104 for storing data, wherein the server device may further include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those of ordinary skill in the art that the architecture shown in fig. 1 is merely illustrative and is not intended to limit the architecture of the server apparatus described above. For example, the server device may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

The memory 104 may be used to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to the account information synchronization method in the embodiment of the present application, and the processor 102 executes the computer program stored in the memory 104, thereby performing various functional applications and data processing, that is, implementing the method described above. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located with respect to the processor 102, which may be connected to the server device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module for communicating with the internet wirelessly.

In this embodiment, a method for synchronizing account information is provided, fig. 2 is a flowchart of a method for synchronizing account information according to an embodiment of the present application, as shown in fig. 2, where the flowchart includes the following steps:

step S202, under the condition that the first baseboard management controller BMC determines that the account information of the second BMC needs to be set, randomly generating target account information;

step S204, according to a URL preset by the second BMC, a request for requesting to configure account information of the second BMC as the target account information is sent to the second BMC;

step S206, when a message sent by the second BMC and used for indicating that the account information of the second BMC has been configured as the target account information is received, the second BMC is used to communicate with the second BMC.

In step S202, the target account information includes, but is not limited to: user name, password, etc., the first BMC including, but not limited to: a handpiece BMC including, but not limited to: GPU BOX end BMC. The first BMC determines that the second BMC is needed; the method for setting the account information of the BMC includes, but is not limited to: and acquiring and checking the value of a target zone bit preset in the first BMC, and determining whether the account information of the second BMC needs to be set according to the value of the target zone bit. The method for randomly generating the target account information by the first BMC includes but is not limited to: randomly generating target account information using a pseudo-random number generator: the user name and the password are randomly generated by using a pseudo-random number generator, wherein the pseudo-random number generator is an algorithm-based random number generator, and can generate a random-like number sequence according to a certain rule, and the number sequence can be used as the user name and the password; the target account information is randomly generated using a UUID (Universally Unique Identifier, universally unique identification code) generator: a UUID generator is used to generate a random username and password, which is a 128-bit numerical identifier that can be used to uniquely identify objects, including usernames and passwords; randomly generating target account information using a cryptographic hash function: generating a random user name and password using a cryptographic hash function, which is a function of compressing messages of arbitrary length into message digests of fixed length that can be used to generate a random user name and password; randomly generating target account information using a true random number generator: a true random number generator is used to generate a random user name and password. A true random number generator is a physical process based random number generator that can generate true random numbers that can be used to generate random usernames and passwords.

In step S204, the URL (Uniform Resource Locator ) includes, but is not limited to: a redfish URL, and the like.

In step S206, the method of the first BMC and the second BMC for communication includes, but is not limited to: communication with the intelligent platform management interface via IPMI (Intelligent Platform Management Interface), communication via restful (Representational State Transfer ), communication via redfish, etc., wherein the interfaces are predetermined by the head-end BMC and BOX-end BMC when communicating using redfish or restful.

Through the steps, the machine head BMC randomly generates the target account information and sends the target account information to the BOX end BMC for configuration, so that the problem that the data security of the end BMC is affected under the condition that the account information is leaked due to the fact that the account information of the end BMC is unchanged in the related art can be solved, the problem that the security of the end BMC is low is solved, and the effect of improving the security of the BOX end BMC is achieved.

In an alternative embodiment, the method further comprises, prior to randomly generating the target account information: determining whether the first BMC needs to set the account information of the second BMC or not by the following method; acquiring a value of a target zone bit preset in the first BMC; under the condition that the value of the target zone bit is a first value, determining that the first BMC needs to set account information of a second BMC; and under the condition that the value of the target zone bit is a second value, determining that the first BMC does not need to set account information of the second BMC.

In the above steps, the method for determining whether the first BMC needs to set the account information of the second BMC includes, but is not limited to: acquiring a flag value, wherein if the flag value is 0, the first BMC needs to set the account information of the second BMC, and if the flag value is 1, the first BMC does not need to set the account information of the second BMC; or if the value of the flag is 0, the first BMC needs to set the account information of the second BMC, and if the value of the flag is 1, the first BMC does not need to set the account information of the second BMC, and the flag bit includes but is not limited to: userSetFlag (user set flag), and so forth.

In an alternative embodiment, before communicating with the second BMC using the target account information, the method further comprises: receiving a message sent by the second BMC, wherein the message is used for indicating that the account information of the second BMC is configured as the target account information; and updating the value of the target zone bit in the first BMC to a second value.

In the above step, updating the value of the target flag bit in the first BMC to the second value includes, but is not limited to: and updating the value of the user set flag bit from 0 to 1, or updating the value of the user set flag bit from 1 to 0.

In an alternative embodiment, the method further comprises: the value of the target zone bit is the first value; and updating the value of the target zone bit to the first value under the condition that the time length for setting the value of the target zone bit to the second value reaches the target time length or communication between the first BMC and the second BMC is interrupted.

In the above step, the target duration includes, but is not limited to: the target duration may be set by the operation and maintenance personnel, or may be randomly generated within a duration range set by the operation and maintenance personnel, for example, the duration range set by the operation and maintenance personnel is 6 to 48 hours, and the first BMC randomly generates a duration within the duration range as the duration of the use of the user name and the password. The communication interruption conditions include, but are not limited to: the network connection between the first BMC and the second BMC is interrupted, the I2C (Inter-Integrated Circuit, serial bus) integrated in a re-timer card and a cable between the first BMC and the second BMC is failed, the account number and the password are invalid, and the like.

Through the steps, when the communication faults and the target account information use time reach the preset time, the zone bit is updated, so that the operation of generating and using a new user name and password for communication is triggered, and the safety of the first BMC and the second BMC is effectively improved.

In an alternative embodiment, after communicating with the second BMC using the target account information, the method further comprises: acquiring target information of the second BMC; and displaying the target information of the second BMC on the first BMC side.

Through the steps, the operation and maintenance personnel can know the information of the second BMC and related equipment through the target information of the second BMC displayed by the first BMC, so that multi-equipment management and monitoring are realized, and meanwhile, the rapid diagnosis and positioning of faults are facilitated under the condition that the second BMC breaks down.

In an alternative embodiment, the method further comprises: the second BMC receives a request message from a target device based on the preset URL, wherein the URL is integrated in a target redfish process of the second BMC, and the target redfish process is used for monitoring received network data in real time, analyzing the network data and distributing the network data based on an analysis result; the second BMC acquires a header of the request message and an IP address of the target device, and determines whether the target device is the first BMC according to the header and the IP address; the second BMC analyzes the request message to obtain request content contained in the request under the condition that the target device is determined to be the first BMC; the second BMC stores the target account information and configures the account information of the second BMC as the target account information under the condition that the request content comprises the content for requesting the account information of the second BMC to be configured as the target account information; and the second BMC sends a response message for indicating that the account information of the second BMC is configured as the target account information to the target equipment.

In the above steps, the method for the second BMC to send the response message to the first BMC includes, but is not limited to: sending a response message using IPMI; sending a response message using SNMP (Simple Network Management Protocol ); sending a response message using the Redfish API (Redfish Application Programming Interface ); transmitting a response message using a custom protocol: the BMCs may also use custom protocols for message communication, such as custom communication protocols based on TCP (Transmission Control Protocol ) or UDP (User Datagram Protocol, user Datagram protocol), and the like. The method for determining whether the target device is the first BMC according to the header and the IP address includes, but is not limited to: in the case where the IP address is a fixed IP address of the head BMC and the "host" field is present in the header, it is determined that the data to access the URL is from the head. The machine head BMC integrates threads for setting the user name and the password of the BOX end BMC in a hardware monitoring process of the machine head BMC, wherein the hardware monitoring process monitors whether the machine head BMC and the BOX end BMC can communicate correctly or not in real time, for example, whether network connection is normal or not, whether I2C is normal or not, whether transmitted data can be sent and returned normally or not, if the machine head BMC and the BOX end BMC communicate abnormally, the hardware monitoring process can analyze fault reasons, for example, whether the I2C is abnormal or not, whether the network is abnormal or not, whether the user name and the password are abnormal or not, and sets the userSetFlag to 0 under the condition that the user name and the password are abnormal (for example, incorrect or invalid). The URL of the user name and the password set by the BMC at the BOX end is integrated in a redfish process, the process monitors network data sent by the BMC at the machine head in real time, analyzes the content of the data and distributes the data, and if the sent data is found to be the URL of the user name and the password, the URL is given to the URL of the user name and the password to be processed. The redfish process performs data analysis and distribution according to the received URL field, for example, setting the URL of the user name and password as/redfish/v 1/OEM/Adduser, setting the URL of the BMC time zone as/redfish/vI/OEM/Timezone, setting the URL of the power-on strategy as/redfish/v 1/OEM/PowerPolicy and the like.

In an alternative embodiment, the second BMC storing the target account information includes: and under the condition that the target account information comprises a user name and a password, the second BMC stores the target account information in a user name password list pre-established in the second BMC in a local session mode.

In the above step, the second BMC stores the target account information in a preset user name password list in the second BMC in a local session manner, including but not limited to: the user name and password are added to the user name password list of the GPU BOX by way of non-authenticated local session, and UserID is fixed to 15 (for illustration only, not limitation).

The following describes the overall scheme of the present invention with reference to specific examples:

embodiment one:

fig. 3 is a second flowchart of an account information synchronization method according to an embodiment of the present application, as shown in fig. 3, the flowchart includes the following steps:

step S302, a machine head BMC sets a random user name and a password for a GPU BOX end BMC;

step S304, judging whether the setting result returned by the BOX end BMC is successful, executing step S306 under the condition of success, and jumping to step S312 under the condition of unsuccessful;

step S306, the user name and the password are used for communication with the BMC at the BOX end periodically;

step S308, judging whether the communication between the machine head BMC and the BOX end BMC is normal, executing step S310 under the normal condition, and jumping to step S302 under the abnormal condition;

step S310, judging whether the user name and the password are out of date, jumping to step S306 if the user name and the password are not out of date, and jumping to step S302 if the user name and the password are out of date;

in step S312, SEL (System Event Log) is written to record.

In the above steps, the machine head BMC adds a synchronization thread for setting the user name and the password of the GPU BOX end BMC and marks whether the user name and the password of the GPU BOX end are set as the flag bit usersetsetflag of the random user name and the password, the default value of the usersetsetflag is set to 0 at the initial moment, when the machine head BMC is started, when the usersetsetflag is detected to be 0, it is determined that the user name and the password of the GPU BOX end BMC are not set, at this moment, the synchronization thread generates a random user name and password according to the current timestamp, for example, the user name is 12 bytes, the password is 12 bytes, then the user name and the password are set to the BMC of the GPU BOX end by accessing the URL of the GPU BOX end, the user name and the password are stored in the machine head, and when the user name and the password of the GPUBOX end are successfully set to the user name and the password, the machine head BMC sets the value of the usersetsetflag to 1. And then, the machine head BMC uses the user name and the password to communicate with the BMC at the GPU BOX end, and gathers key information at the BOX end to the machine head for display, thereby facilitating alarming and operation and maintenance. And under the condition that communication between the machine head BMC and the GPU BOX end BMC is abnormal, setting the value of the UserSetFlag to 0, and when the synchronous thread detects that the flag bit is 0, regenerating a user name password and executing the subsequent steps. When the machine head BMC sets the UserSetFlag to 1, the time T1 is recorded as the time of successful random user name password synchronization, the synchronous thread continuously compares the current time in the first BMC with the time T1 of successful user name and password synchronization to obtain a time difference, and when the time difference is greater than 24 hours (for illustration and not limitation), the synchronous thread sets the UserSetFlag to 0, and the user name and the password are randomly generated again and the subsequent steps are executed. The connection manner between the handpiece BMC and the BOX terminal BMC includes, but is not limited to: I2C, network connection, etc., the communication method between the set-top BMC and the BOX-top BMC includes, but is not limited to: ipmi cmd, restful, redfish, etc.

Embodiment two:

fig. 4 is a flowchart III of an account information synchronization method according to an embodiment of the present application, as shown in fig. 4, the flowchart includes the following steps:

step S402, the BMC at the BOX end newly adds a URL;

step S404, checking a Header and an IP address of a data stream accessing a URL of the BOX terminal BMC by the BOX terminal BMC;

step S406, the BOX end BMC determines whether the source of the data stream is the machine head BMC, if yes, step S408 is executed, and if not, step S410 is executed;

step S408, the BOX terminal BMC sets information such as a user name and a password contained in a data stream sent by the machine head BMC to the GPU BOX terminal BMC, and uses the user name and the password to communicate with the machine head BMC;

in step S410, the BOX end BMC returns a data exception to the handpiece BMC, and the setting fails.

In the above steps, the GPU BOX end BMC adds a refush URL, and checks not the user name password but the header and the IP address of the source of the data stream for the data stream accessing the refush URL, determines that the data stream currently accessing the refush URL is from the head only when the IP address is the fixed IP address of the head BMC and the header has a "host" field, receives and parses the data stream from the head, extracts the user name and the password contained in the data stream, and then adds the user name and the password to the user name password list of the GPU BOX by means of a non-authentication local session, and fixes the UserID to 15 (for illustration only, not limitation).

Through the steps, the URL which is not authenticated but is used for verifying the data source is newly added at the GPU BOX end BMC, a random user name and a random password are generated at the machine head BMC at regular intervals, the user name and the password are set into the GPU BOX end BMC, and meanwhile the machine head BMC uses the user name and the password to communicate with the GPU BOX end BMC, so that the user name and the password of the machine head BMC and the GPU BOX end BMC are not disclosed to the outside and cannot be cracked, and therefore the GPU BOX end BMC cannot be attacked by the external network. The redfish URL is used for checking simply, only the user name, the password and the header field data and the IP are required to be checked, and the checking efficiency is high.

From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiment also provides an account information synchronization device, which is used for implementing the above embodiment and the preferred implementation, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

Fig. 5 is a block diagram of a configuration of an account information synchronization device according to an embodiment of the present application, as shown in fig. 5, the device includes: the generating module 52 is configured to randomly generate target account information when the first baseboard management controller BMC determines that the account information of the second BMC needs to be set; the first sending module 54 is configured to send, to the second BMC, a request for requesting that the account information of the second BMC be configured as the target account information according to a uniform resource locator URL preset by the second BMC; and a communication module 56, configured to, when receiving a message sent by the second BMC and used for indicating that the account information of the second BMC has been configured as the target account information, communicate with the second BMC using the target account information.

In an alternative embodiment, the apparatus further comprises: a first determining module, configured to determine, before randomly generating target account information, whether the first BMC needs to set the account information of the second BMC, where the first determining module includes: the acquisition unit is used for acquiring the value of a target zone bit preset in the first BMC; the first determining unit is used for determining that the first BMC needs to set account information of the second BMC under the condition that the value of the target zone bit is a first value; the second determining unit is configured to determine that the first BMC does not need to set account information of the second BMC when the value of the target flag bit is the second value.

In an alternative embodiment, the apparatus further comprises: the first receiving module is used for receiving a message sent by the second BMC and used for indicating that the account information of the second BMC is configured as the target account information before the target account information is used for communicating with the second BMC; and the first updating module is used for updating the value of the target zone bit in the first BMC to a second value.

In an alternative embodiment, the apparatus further comprises: and the second updating module is used for updating the value of the target zone bit to the first value under the condition that the time length for setting the value of the target zone bit to the second value reaches the target time length or the communication between the first BMC and the second BMC is interrupted.

In an alternative embodiment, the apparatus further comprises: the acquisition module is used for acquiring target information of the second BMC after the target account information is used for communicating with the second BMC; and the display module is used for displaying the target information of the second BMC on the first BMC side.

In an alternative embodiment, the second BMC device further includes: the second receiving module is used for receiving a request message from a target device based on the preset URL, wherein the URL is integrated in a target redfish process of the second BMC, and the target redfish process is used for monitoring received network data in real time, analyzing the network data and distributing the network data based on an analysis result; the second determining module is used for acquiring a header of the request message and an IP address of the target device, and determining whether the target device is the first BMC according to the header and the IP address; the analyzing module is used for analyzing the request message to acquire the request content contained in the request message under the condition that the target device is determined to be the first BMC; the storage module is used for storing the target account information and configuring the account information of the second BMC as the target account information when the request content comprises the content for requesting the account information of the second BMC to be configured as the target account information; and the second sending module is used for sending a response message for indicating that the account information of the second BMC is configured as the target account information to the target equipment.

In an alternative embodiment, the storage module includes: and the storage unit is used for storing the target account information in a user name and password list pre-established in the second BMC in a local session mode when the target account information comprises the user name and the password.

It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; alternatively, the above modules may be located in different processors in any combination.

Embodiments of the present application also provide a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

In one exemplary embodiment, the computer readable storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random AccessMemory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.

Embodiments of the present application also provide an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

In an exemplary embodiment, the electronic device may further include a transmission device connected to the processor, and an input/output device connected to the processor.

Specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the exemplary implementation, and this embodiment is not described herein.

It will be appreciated by those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the same, but rather, various modifications and variations may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application should be included in the protection scope of the present application.

Claims (10)

1. A method for synchronizing account information is characterized in that,

comprising the following steps:

under the condition that the first baseboard management controller BMC determines that the account information of the second BMC needs to be set, randomly generating target account information;

according to a uniform resource locator URL preset by the second BMC, sending a request for requesting to configure account information of the second BMC as the target account information to the second BMC;

and under the condition that a message sent by the second BMC and used for indicating that the account information of the second BMC is configured as the target account information is received, communicating with the second BMC by using the target account information.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the method further includes, prior to randomly generating the target account information:

determining whether the first BMC needs to set the account information of the second BMC or not by the following method;

acquiring a value of a target zone bit preset in the first BMC;

under the condition that the value of the target zone bit is a first value, determining that the first BMC needs to set account information of a second BMC;

and under the condition that the value of the target zone bit is a second value, determining that the first BMC does not need to set account information of the second BMC.

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

before communicating with the second BMC using the target account information, the method further includes:

receiving a message sent by the second BMC, wherein the message is used for indicating that the account information of the second BMC is configured as the target account information;

and updating the value of the target zone bit in the first BMC to a second value.

4. The method of claim 2, wherein the step of determining the position of the substrate comprises,

the method further comprises the steps of:

and updating the value of the target zone bit to the first value under the condition that the time length for setting the value of the target zone bit to the second value reaches the target time length or the communication between the first BMC and the second BMC is interrupted.

5. The method according to any one of claim 1 to 4, wherein,

after communicating with the second BMC using the target account information, the method further comprises:

acquiring target information of the second BMC;

and displaying the target information of the second BMC on the first BMC side.

6. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the method further comprises the steps of:

the second BMC receives a request message from a target device based on the preset URL, wherein the URL is integrated in a target redfish process of the second BMC, and the target redfish process is used for monitoring received network data in real time, analyzing the network data and distributing the network data based on an analysis result;

the second BMC acquires a header of the request message and an IP address of the target device, and determines whether the target device is the first BMC according to the header and the IP address;

the second BMC analyzes the request message to obtain request content contained in the request message under the condition that the target device is determined to be the first BMC;

the second BMC stores the target account information and configures the account information of the second BMC as the target account information under the condition that the request content comprises the content for requesting the account information of the second BMC to be configured as the target account information;

and the second BM C sends a response message for indicating that the account information of the second BM C is configured as the target account information to the target equipment.

7. The method of claim 6, wherein the step of providing the first layer comprises,

the second BMC storing the target account information includes:

and under the condition that the target account information comprises a user name and a password, the second BMC stores the target account information in a user name password list pre-established in the second BMC in a local session mode.

8. An account information synchronizing device is characterized in that,

comprising the following steps:

the generation module is used for randomly generating target account information under the condition that the first baseboard management controller BM C determines that the account information of the second BM C needs to be set;

the first sending module is used for sending the first uniform resource locator U RL to the second B M C according to a preset uniform resource locator U RL; b M C sends a request for requesting to configure the account information of the second B M C as the target account information; and the communication module is used for communicating with the second BM C by using the target account information under the condition that the message sent by the second BM C and used for indicating that the account information of the second BM C is configured as the target account information is received.

9. A computer-readable storage medium comprising,

the computer readable storage medium has stored therein a computer program, wherein the computer program when executed by a processor realizes the steps of the method as claimed in any of claims 1 to 7.

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that,

the processor, when executing the computer program, implements the steps of the method as claimed in any one of claims 1 to 7.