JP2009104220A - System having account release/block means, and account release/block program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system enabling accurate and prompt releasing and blocking of a work account. <P>SOLUTION: In a system administration computer, there is provided an account correspondence table that stores the correlation of a work application for releasing the account with the corresponding account released by the work application. When the account is released for maintenance, data correlating the work application with the released account is set in the account correspondence table. When the account is to be blocked after the work is completed, the account correspondence table is examined to check whether the account to be blocked is in use for another work. If the account is in use, only the account correspondence table is changed, while its blocking is not performed actually. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

The present invention relates to a system having a means for centrally managing the opening and closing of accounts to which an operator logs in for maintenance of each server in a network system to which a plurality of servers are connected, and a program for opening and closing accounts It is about.

Conventionally, as a system for centrally managing accounts of each server, there is a configuration described in, for example, Japanese Patent Application Laid-Open No. 10-307793 (see Patent Document 1). This is because the creation and deletion of an account and the confirmation of which terminal the user is registered in are made via a network between the workstation 10 which is a virtual terminal server and the workstations 11 and 12 which are virtual terminal clients. And running while transferring data.

Further, in the local account centralized management system and management method and program described in Japanese Patent Application Laid-Open No. 2007-52477 (see Patent Document 2), local account information is managed by a managing terminal in a terminal connected via a network. The terminal that is controlled and controlled in a manner corresponding to the change or control (lockout) can change or control the local account information of the computer owned by each terminal.
Japanese Patent Laid-Open No. 10-307793 JP 2007-52477 A

The configuration of setting an account on the server and logging in is a function necessary for maintenance of the server function, and has an account function that allows the operator to log in regardless of the type of OS used for the server. . Accounts are also password protected to prevent unauthorized persons from logging into the server and harming the system. As the scale of the system increases, the number and complexity of hardware such as servers and software executed in the system increase. As a result, the number of operators engaged in maintenance and the like increases, and the number of accounts set in each server also increases. As the number of accounts working in the system increases, the risk of misuse of accounts and their passwords increases.

As shown in the above references, many techniques for managing accounts and their passwords are known. However, to reduce the risk of account and password leaks, the number of accounts working on the system should be as small as possible. Therefore, when it is necessary to log in to the server due to maintenance, etc., the account for that work is released (UNLOCK), and when the maintenance is completed and the account becomes unnecessary, the account becomes unnecessary A method of locking (LOCK) is adopted. According to this method, only a limited number of administrator accounts can be used at any time in the system, and work accounts are only temporarily opened when needed, The risk of misuse of your account is reduced.

Many systems are configured by connecting a plurality of servers via a network. FIG. 11 shows a conventional procedure for executing server maintenance in a system 2000 including a plurality of servers (2002, 2004,...).
(1) The maintenance worker 2200 decides the work schedule, and applies to the administrator 2100 for the worker name, the maintenance target server (for example, server 2002), the account name used for the work, the maintenance start time and end time, etc. To do.
(2) The administrator 2100 accesses the target server 2002 from the administrator terminal 2001 provided in the system 2000 by means such as Telnet, and logs in to the target server 2002 using the administrator account and password. . After logging in with the administrator's authority, open the work account that was applied for work, and set the login password for the work account.
(3) The administrator 2100 notifies the applicant 2200 that the work account has been opened and can be used and the login password by e-mail or the like.
(4) The applicant 2200 operates the console terminal 2003 of the server 2002, logs in to the application account for the application using the notified password, and performs operations such as maintenance.
(5) The worker 2200 who has finished the work notifies the manager 2100 of the completion of the work.
(6) The administrator 2100 closes the work account of the server 2002.

The above example is an example in which work is performed on one server. However, when the work spans multiple servers, work accounts are released to all target servers, and all of these accounts are blocked by the end of the work. The
Since an operating system (OS) for managing servers is selected according to the purpose, there are many network systems having servers managed by different OSs. The procedure for opening and closing an account, and the command to be used differ depending on the OS. Therefore, the administrator confirms the OS of the server that the applicant has requested to open the account, and opens the account and sets the password by using a procedure and command suitable for the OS.
As the scale of the system increases and the number and types of servers constituting the system increase, the amount of work such as maintenance increases, and the complexity of work such as work across multiple servers also increases. As a result, it is necessary to open accounts of a plurality of servers at the start of work and close all related accounts at the end of the work. In some cases, one account is shared by a plurality of operations. In such a situation, even if the end of one work is notified, if another work using the account is being performed, the other work becomes impossible if the account is closed. Therefore, when closing an account, it is necessary to confirm whether blocking the account does not affect others, and the administrator requires a great deal of labor.

The present invention provides a system capable of opening and closing a work account accurately and quickly in a system having a plurality of servers managed by different OSs, and a program for opening and closing a work account. Is aimed at. The present invention automatically determines a procedure and command suitable for the OS of the target server based on the request for opening the work account requested by the worker and the request for closing the account, and determines the requested account. Open and close. Alternatively, the present invention manages the release of a work account based on the relationship between a plurality of work and work accounts.

FIG. 1 is a diagram showing an outline of an entire account opening / closing system according to the present invention. The system includes an account application database 110 that stores work application data applied by a worker who performs work such as maintenance, a management computer 100 having an administrator terminal 111 operated by an administrator, and a plurality of servers 112 and 114. It is composed of
Servers included in the system are managed by different OSs such as Open-VMS (registered trademark), Tru64 (registered trademark), HPUX (registered trademark), and Solaris (registered trademark). FIG. 1 shows an HPUX server 112 and an Open-VMS server 114. Each server has external storage devices 113 and 115 for storing management information such as accounts and passwords set in the server.

The account application database 110 is a database that stores account information necessary for work on servers in the system. Workers who are scheduled to perform maintenance work on servers in the system are account application databases that contain information such as the worker's name, the account used for the work, and the scheduled start and end dates of work. Register with 110. If the work spans multiple servers, register the accounts of all the target servers.
The system administrator retrieves work application data to be processed from the database 110 using the manager terminal 111 of the management computer 100 and displays it on the terminal 111. Search and display forms include a list of all work application data, a method of listing work accounts by specifying work application numbers, a fuzzy search by specifying a host name or user name, and the results. List display methods are possible. A specific one is selected from a plurality of work applications displayed in a list, or a plurality of work applications are selected at once, and the management computer 100 is instructed to perform processing such as opening, closing, and changing a password.

FIG. 2 is an example of instructions and responses exchanged between the administrator terminal 111 and the account release block processing unit 102 by a GUI (graphical user interface).
(a) is a method of designating an account release block by specifying a work application number. Work application data from a specific date or time or a specific work applicant is extracted from the account application database 110 and displayed in a list, and a work application number is specified in the [IN] field to instruct the management computer 100 to open or close an account. The management computer 100 displays a report on whether there is an error in the work application content, the result of opening or closing, etc. in the [OUT] column.
(b) is a method of directly specifying a server (node) name and an account name. The administrator specifies the server (node) name and account name of the account to be opened or closed in the [IN] field. The management computer 100 displays a report such as the result of opening or closing in the [OUT] field.
(c) is an instruction for changing the account password, and is a GUI used when changing the account password because the operator requests to change the password for logging in to the specific account. Specify the server (node) name and account name of the account whose password is to be changed in the [IN] field. The management computer 100 displays a report such as the processing result in the [OUT] field.

The management computer 100 shown in FIG. 1 includes an account input check unit 101, an account release block processing unit 102, a password registration unit 103, and an account database 104.
The account input check unit 101 reads work application data instructed by the administrator from the account application database 110. The read work application is inspected for whether there are no errors in the contents of the work application, such as whether all necessary items are specified or whether the specified items are correct. When an error is found, the presence of the error is notified to the manager terminal 111 as [OUT] “input rule error” in FIG.
The account release block processing unit 102 inputs an administrator instruction from the administrator terminal 111. In addition, work application data corresponding to the administrator's instruction is read from the account application database 110 via the account input check unit 101.
The management computer 100 is connected to a target server in the system by a technique such as Telnet. The account release block processing unit 102 interprets the work application data read by referring to the stored contents of the account database 104, selects a command suitable for the OS of the target server, sends it to the target server, and executes the instruction Report the results.
In response to the administrator's instruction to change the password (FIG. 2C), the password registration unit 103 changes the password stored in the account database 104 and sends the result to the administrator terminal 111. Return to the administrator via
The account database 104 stores information on the servers in the system and the accounts set in the servers.

FIG. 3 is a diagram showing the information registered in the account database 104 and the relationship between the information.
The account table is a table for managing a work account for a worker to log in to a target server when performing a work such as maintenance on a host (server) in the system. In the account table 201 of FIG. 3, “account 1”, “account 2”,..., “Account n” are registered. Each account includes a host (server) name to which the account belongs, a user ID (worker ID) for logging in to the account, an account type, a current state, and the like.
There are two types of accounts that can be lent to workers: a type that opens an account upon application and sets a password to lend to the worker (type 1), a type that opens an account upon application and lends without setting a password (type 2) ), Change or set the password of the account by application, and can provide multiple forms such as a type (type 3) that notifies the worker of the password. In the “account type”, type data indicating the above form is set.
“Current status” is data indicating whether the account is currently open or closed. “Account 2” in the account table 201 belongs to “Host 2”, the worker ID is “UserX”, and is an account to be opened / closed, indicating that it is currently closed and is not being used. ing.

The host table is a table for managing hosts (servers) existing in the system. In the host table 211 of FIG. 3, “host 1”, “host 2”,..., “Host m” are registered. Each host is set with a host name, an IP address in the system, an OS type controlling the host computer, an administrator account for logging in to the OS, and the like. In the host table 211, the host name of "Host 2" is "HOSTXX" and the IP address is "192.169
... ”, The OS is“ HPUX ”, and the administrator user ID for login is“ masterxxx ”.
From the host information set for each account in the account table 201, the corresponding host information in the host table 211 can be accessed.

The account database 104 is provided with a command table corresponding to the OS. FIG. 3 shows a command table 221 for HPUX and a command table 231 for Open-VMS. In each command table, “Login command” executed when logging in to the server OS, “Unlock command” executed when releasing the account, “Lock command” executed when closing the account, account password setting, Alternatively, link information to the “password command” used to change the set password is set. In FIG. 3, link information to the Login command 225 for HPUX is stored in the Login command column of the HPUX command table 221, and Open-VMS is stored in the Login command column of the Open-VMS command table 231. The link information to the Login command 235 is stored.
A function code string for executing a command is stored in the link destination of each command table. In the example of FIG. 3, the HPUX Login command 225 includes three function codes of “function code 1”, “function code 2”, and “function code 3”. The Login command 235 for Open-VMS is composed of two function codes, “function code 1” and “function code 2”. The account release block processing unit 102 sequentially reads and executes the function codes constituting the command one by one.
Each command stores a message such as a success message and a failure message, and outputs the execution result of the command to the administrator terminal 111.

The account release block processing unit 102 performs an operation corresponding to the type specified by the “account type” in the account table. In this embodiment, the account is divided into three types and managed, and FIG. 4A shows the operation of the count release block processing 102 that reads “account type”.
Step 250: The account release block processing unit 102 refers to the account table 201 and the host table 211 stored in the account database 104 and logs in to the target server. Check the "account type" of the requested account. When the account type is “Type1”, the process proceeds to step 252; when the account type is “Type2”, the process proceeds to step 255;
Step 252: The “Type 1” account is closed when not in use, released when a use request is issued, and a new password is set and lent to the operator. Accordingly, in the case of an account of “Type 1”, the account release block processing unit 102 performs processing for releasing the requested account (step 252) and processing for setting a new password for the account (step 253). Next, the processing result is output to the administrator terminal 111 and logged out from the target server (step 254). The administrator who confirms the account release notifies the application worker that the work can be started and the set password.
Step 255: The account of “Type2” is set to be closed when not in use, and released when the use request is issued and lent to the operator. This type of account does not require password processing such as setting a password. Therefore, in the case of an account of “Type 2”, the account release block processing unit 102 performs only the processing for releasing the requested account (step 255), outputs the processing result to the administrator terminal 111, and logs out from the target server. (Step 254). The administrator who confirms the account release notifies the requesting worker that work can be started.
Step 256: The account of “Type 3” is not blocked even when it is not being used, and when a request for use is issued, a new password is set and lent to the operator. In the case of a “Type 3” account, the account release block processing unit 102 performs only the process of setting a new password for the requested account (step 256), outputs the processing result to the administrator terminal 111, and logs out from the target server. (Step 254). The administrator who confirms the setting of the bath word notifies the newly set bath wort to the worker who applied.

FIG. 4B is an example of control performed between the administrator terminal 111, the management computer 100, the account application database 110, and the target servers 112 and 114 in executing the “Type1” command.
(a): The account application database 110 stores work application data such as opening accounts applied by workers who perform maintenance work on the servers 112 and 114. The administrator operates the administrator terminal 111 to instruct the management computer 100 to search for work application data that meets a specific condition. Upon receiving the instruction, the account release block processing unit 102 of the management computer 100 searches the account application database 110 via the account input check unit 101, extracts work application data that matches the specified conditions, and sends it to the administrator terminal 111. indicate.
(b): The administrator selects one or more work application data to be processed from the work application data displayed on the administrator terminal 111 and instructs the management computer 100 to perform the process.
The account release block processing unit 102 reads work application data corresponding to the account input check unit 101 from the account application database 110 and instructs verification of whether the data contents are valid. If an error is found in the work application content, a message to that effect is displayed on the administrator terminal 111.
When there is no error in the work application content, the requested account is extracted from the work application data (assuming that “account 2” in FIG. 3 is extracted).
The account release block processing unit 102 reads information set in the account “account 2” extracted from the account table 201 of the account database 104. From this information, it is confirmed that “Account 2” is blocked, and a pointer to the table of “Host 2” to which the user ID “UserX” for the worker and “Account 2” belong is read.
Next, the account release block processing unit 102 reads information set in “host 2” of the host table 211 based on the pointer to the table of “host 2”. From this information, it is determined that the OS of “host 2” is “HPUX” and the user ID for the administrator who logs in to the host 2 is “masterxxx”.
(c): Processing corresponding to step 250 in FIG. The management computer 100 connects to the target host (server) using Telnet.
The account release block processing unit 102 controls the communication means of the management computer 100 and connects to the “host 2” using Telnet. After confirming the connection, the login command 225 for “HPUX” is read out from the account database 104 and executed, and the user ID “masterxxx” for the administrator and a password for the administrator specified separately are used to connect to the host 2. In.
The account release block processing unit 102 performs processing corresponding to step 251. The account release block processing unit 102 reads the account type from the account database 104. In the example of FIG. 4B, the command is “Type 1”, and the account release block processing unit 102 executes the processing of “Type 1”, that is, Step 252 and Step 253 of FIG.
(d): Processing corresponding to step 252 in FIG. Read account unlock command “Unlock command” for “HPUX” which is OS of host 2 from account database 104, apply necessary items such as user ID “UserX” for worker to command and send to host 2 And execute. When an error response is returned from the host 2 that is the target server, a message to that effect is displayed on the administrator terminal 111 and the process ends. When a normal response is returned from the target server, the process proceeds to the next.
(e): Processing corresponding to step 253. The password change command “password command” for “HPUX” is read from the account database 104, and the necessary items such as the old password and new power registered by the password registration unit 103 in FIG. Run towards.
(f): Processing corresponding to step 254 in FIG. When an error response is returned from the target server, error information is displayed on the administrator terminal 111, and when the normal response is returned, a message indicating that the processing has been completed normally is displayed.
(g): A long-off command is transmitted to the target server, and the login performed in (c) is terminated.

FIG. 5 is a flowchart of the process executed in FIG.
Step 311: An administrator operates the administrator terminal 111 to specify work application data for requesting account opening or closing.
Step 312: The account release block processing unit 102 instructs the account input check unit 101 to read work application data corresponding to the account input database 110.
Step 313: The account input check unit 101 searches the work application database 110, reads the instructed work application data, and checks whether there are any errors such as a lack of essential items in the work application content. If an error is found, the process proceeds to step 321 where an error is displayed on the administrator terminal 111 and the process ends.
Step 314: The account release block processing unit 102 extracts the account to be released from the work application data retrieved from the work application database 110 (“Account 2” in FIG. 3). It is possible to instruct processing of a plurality of accounts by one work application data. In this case, the subsequent processing is sequentially executed for each account.
With reference to the account table 201 of the account database 104, the server (host 2) to which the extracted account belongs is identified.
Step 315: The account release block processing unit 102 checks the OS of the identified server (host 2) from the account table 211 (HPUX).
Step 316: The account database 104 stores commands for controlling the server such as a command for logging in to the server, a command for opening the account, and a command for closing the account. The system has servers with different OSs, and the above commands exist for each OS, and the commands are stored according to each OS.
The account release block processing unit 102 retrieves, from the account database 104, a login command (HPUX Login command 225) suitable for the OS (HPUX) of the target server identified in Step 315.
Step 317: Data such as an administrator user ID and password is set in the variable portion of each function code constituting the login command.
Step 318: Connect to the host 2 which is the target server via Telnet.
Step 319: It is determined whether or not the connection is successful. If unsuccessful, the process proceeds to step 321 where an error is displayed on the administrator terminal 111 and the process ends.
Step 320: The login command generated in Step 317 is executed to log in to the target server.

FIG. 6A is an example of a command for executing login to the target server executed in step 320 in FIG. 5, where (a) is a command for HPUX and (b) is a command for Open-VMS. When other OSs such as Tru64 and Solaris exist in the system, commands suitable for these OSs are prepared. These commands are stored in the account database 104, and commands corresponding to the OS of the target server are read and executed.
The “prompt” is output by the OS, which allows input from the outside, to indicate the type of input and prompt the input. Upon receiving the prompt, the account release block processing unit 102 transmits the data defined in the “transmission data” field to the OS.

FIG. 6B is a flow for logging in to the target server. The flow when the command of FIG. 6A is executed is as follows.
Step 421: Corresponds to the command line 401 in FIG. The account release block processing unit 102 reads and executes “function code 1” which is the first function code of the function codes constituting the login command. “Function code 1” instructs the account release block processing unit 102 to wait for the prompt “Login:” from the host to transmit the data set in the transmission data column to the host.
The account release block processing unit 102 that has read “function code 1” receives the prompt “Login:” from the host OS, and then transmits “user ID” defined in “transmission data” of the command line 401. . The user ID transmitted here is the ID of an administrator set as an account for the administrator, and is “masterxxx” in the example of FIG.
Step 422: Upon completion of execution of “function code 1”, the account release block processing unit 102 executes “function code 2” which is the next function code. The operation indicated by “Function Code 2” waits for the prompt “Password:” from the host, sends the data set in the transmission data column to the host, waits for a response from the host, and when the response is successful The next function code is selected, and if unsuccessful, an error message is displayed and an operation to end the process is instructed.
The OS that has received the user ID outputs a prompt “Password:” requesting a password. The account release block processing unit 102 having read “function code 2” waits for the prompt “Password:” to be transmitted, and transmits “password” corresponding to the administrator user ID.
Step 423: The account release block processing unit 102 checks the response of the OS and determines whether or not the login is successful. If the login is not successful, the process proceeds to step 428, an error message is displayed on the administrator terminal 111, and the process is terminated.
Step 424: It is determined whether or not the next function code exists. When it does not exist, the process proceeds to step 429 and the process is terminated. Since “function code 3” exists in the HPUX command shown in FIG. 6A, the command execution is continued.
Step 425: The account release block processing unit 102 reads “function code 3” in the command line 403. With “function code 3”, the account release block processing unit 102 transmits “su root” to the host and waits for the prompt “Password:”. When “Password:” is received, the data set in the transmission data column is transmitted to the host and a response from the host is awaited. When the host response is successful, the next function code is selected. When the host response is not successful, an error message is displayed and the process is terminated.
The account release block processing unit 102 that has read “function code 3” in step 425 transmits “su root” to the host.
Step 426: The OS that has received the “su root” command issues a prompt “Password:” requesting a password. Upon receiving this prompt, the account release block processing unit 102 transmits the root password set in the transmission data column of the command line 404. The HPUX that has received each data transmitted by the management computer 100 by executing “function code 3” gives root authority to the administrator “masterxxx” transmitted by “function code 1”.
Step 427: The account release block processing unit 102 checks the response of the OS and determines whether or not the login is successful. If the login is not successful, the process proceeds to step 428, an error message is displayed on the administrator terminal 111, and the process ends. If the login is successful, the process proceeds to step 429. Since “function code 3” is the last function code, the account release block processing unit 102 ends the process.

The execution of the command for Open-VMS shown in FIG. 6B is as follows.
The command line 411 and the command line 412 in (b) are the same as the command line 401 and the command line 402 in (a), and the account release block processing unit 102 performs steps 421 to 423 in the flow shown in FIG. Execute. In step 424 of FIG. 6B, the account release block processing unit 102 determines whether or not the next function code exists. Since Open-VMS does not require a command corresponding to “su root” of HPUX, there is no code following “function code 2” in command (b) for Open-VMS. Therefore, the processing of the account release block processing unit 102 proceeds from step 424 to step 429 and ends the processing.

If the login to the target server is successful in step 320 of FIG. 5, the account is unlocked (Unlock). The account release command corresponding to the OS of the server identified in step 315 of FIG.
FIG. 7-1 shows an example of an account release command. (a) is an example of the HPUX Unlock command. It consists of one function code “function code 4”, and “/ usr / lbin / modprpw -l -m alock = NO user ID” is set as transmission data. ing.
(b) is an unlock command for Open-VMS. Like (a), it consists of one function code “function code 4”, and “MCR AUTHORIZE MODIFY / FLAGS = NoDisUser user ID” is set as transmission data. ing.
The ID (“UserX” in FIG. 3) of the applicant (worker of the host 2) described in the work application data is assigned to both “user IDs”. The transmission data of (a) and (b) is the account release command of the corresponding OS, and the OS that has received these data performs the release process of the account specified by the “user ID”, and the success / unsuccess response Reply.

FIG. 7-2 is a processing flow of an account release command. “Function code 4” sends the data set in the transmission data field to the account release block processing unit 102 and waits for a response from the host. If the response is successful, the processing ends normally and fails. In this case, an error message is displayed to instruct to end the process.
In step 521, the account release block processing unit 102 that has read “function code 4” transmits an Unlock command for each OS set in the transmission data column to the target server that is logged in as an administrator. Wait for a response. In step 522, the response from the target server is analyzed to determine whether or not the command has been executed normally. If not executed normally, the process proceeds to step 523, an error message is displayed on the administrator terminal 111, and the process is terminated.

When the account is normally released (Unlock), a password is set for the worker's account in Fig. 4-2 (e). A password change command (passwd command) corresponding to the OS type of the server identified in step 315 in FIG. 5 is read from the account database 104.
FIG. 8A shows a command for HPUX, which is composed of four function codes. (b) is a command for Open-VMS, which is composed of one function code and transmission data “MCR AUTHORIZE MODIFY / NOPWDEXP / PASSWD = password user ID”. Both “user IDs” are user IDs described in the work application data, that is, worker IDs assigned to the “user ID” field of the Unlock command in FIG. 7A (“UserX” in FIG. 3). )) Is substituted.
In the HPUX command (a), the “old password” and “new password” contain the previously set password and the newly set password. It is blank when "Old Password" is not set. The “new password” may be a character string designated by the administrator, or a character string randomly generated by the management computer. Each password is a management computer
It is managed by the password registration unit 103 in 100 and set in a predetermined location of the account database 104.
The “password” and “user ID” in the command (b) for Open-VMS correspond to the “new password” and “user ID” in (a), respectively.

FIG. 8-2 is a processing flow for changing the password of the account for the opened worker.
Step 621: The account release block processing unit 102 reads and executes “function code 5” on the command line 601 in FIG. By reading “function code 5”, the account release block processing unit 102 transmits the “passwd user ID” set in the transmission data column to the host and waits for a response from the host. When the response is “error”, an error message is displayed and the process is terminated. When the response is the prompt “Old password”, the next function code 6 is read and executed, and when the response is the prompt “New password” The next next function code 7 is read and executed.
The account release block processing unit 102 having read “function code 5” transmits the “passwd user ID” set in the transmission data column to the target server and waits for a response from the server.
Step 622: If the OS of the target server responds with an error to the passwd command, the process proceeds to step 629, an error message is displayed on the administrator terminal 111, and the process is terminated. If the target account is an operator account or root, the server may return an "Old password" prompt to enter the set password (old password) (depending on the OS version). Upon detecting this prompt, the account release block processing unit 102 proceeds to step 623. Upon detecting the prompt “New password” requesting input of a password to be set (new password), the account release block processing unit 102 proceeds to Step 625.
Step 623: In response to the prompt “Old password”, the account release block processing unit 102 reads and executes “function code 6” in FIG. “Function code 6” sends the “old password” stored in the transmission data column to the server, waits for a response, and displays an error message when the response is “error”. The process is terminated, and when the response is the prompt “New password”, the next function code 7 is read and executed.
Step 624: If the server responds with an error to the transmission of the old password, the process proceeds to step 629, an error message is displayed on the administrator terminal 111, and the process is terminated. If a prompt “New password” requesting input of a password (new password) to be set as a response signal is responded, the process proceeds to step 625.
Step 625: In response to the prompt “New password”, the account release block processing unit 102 reads “function code 7” in the command line 603 in FIG. “Function code 7” sends the “new password” stored in the transmission data column to the account release block processing unit 102 and waits for a response.
Step 626: If the server responds with an error to the transmission of the new password due to reasons such as including characters that cannot be used in the new password, the process proceeds to step 629, and an error message is displayed on the administrator terminal 111. To finish. If the server OS responds with a prompt “Re-enter new password” requesting confirmation of a new password, the process proceeds to step 627.
Step 627: In response to the prompt “Re-enter new password”, the account release block processing unit 102 reads “function code 8” in the command line 604 in FIG. By reading “function code 8”, the account release block processing unit 102 transmits the “new password” stored in the transmission data column to the server and ends the process (step 628).

When the server OS is identified as Open-VMS in step 315 of FIG. 5, the account release block processing unit 102 uses the password change command for Open-VMS shown in FIG. Read from the account database 104. The account release block processing unit 102 reads “function code 9” to transmit the data set in the transmission data column to the OS. This data is a password setting command for the OS of the server, and the OS of the server that has received this data performs a password setting process and returns a success / failure response.
The password setting command of Open-VMS has only one function code. Therefore, the count release block processing unit 102 determines the presence or absence of an error from the server response, displays a predetermined message on the administrator terminal 111, and ends the process.

FIGS. 4-2 to 8-2 process a work application instructing release of an account. If the instructed work application is account closing, the account closing processing is performed in (d) of FIG. The account release block processing unit 102 reads out and executes a Lock command suitable for the OS of the target server from the account database 104.
FIG. 9A shows an example of the HPUX Lock command, which is composed of one function code and transmission data “/ usr / lbin / modprpw -l -m alock = YES user ID”.
(b) is an example of the Lock command for Open-VMS, and is composed of one function code and transmission data “MCR AUTHORIZE MODIFY / FLAGS = DisUser user ID”, as in HPUX. The user ID of the account to be blocked is assigned to both “user IDs”.
FIG. 9-2 is an account closing flow. The account release block processing unit 102 reads the “function code 10” and transmits the data set in the transmission data column to the OS. This data is a server OS account block command, and the received OS performs account block processing and returns a success / unsuccess response.
The Lock command has only one function code. Therefore, the count release block processing unit 102 determines the presence or absence of an error from the server response, displays a predetermined message on the administrator terminal 111, and ends the process.

System maintenance involves work across multiple servers in the system. Such maintenance requires an operator to log in to a plurality of related servers simultaneously. In such a work, all of the plurality of accounts required for one work application requesting the account release are requested. When an account is released, all accounts that have been applied for work are released, and when maintenance work is completed, all opened accounts are closed.
A plurality of operations such as maintenance can be performed in parallel in one system, and one account may be shared by a plurality of operations. The present invention provides a work application in which an account is released in the account database 104 and an account correspondence table for managing the account released in each work application, and the work being performed and the account being used in the system. Is stored.

FIG. 10A is an example of an account correspondence table. (a) is an account correspondence table in which “Account 1” and “Account 3” are opened in “Work application 1” and “Account 2” is opened in “Work application 2”. ) Is the account correspondence table when “Account 1” and “Account 4” are released for “Work Application 3” with the start of Work 3, and (c) It is an account correspondence table when the account of “application 1” is blocked. It is shown that “account 1” is shared by the work 1 and the work 3 by releasing the account for the work 3 in (b).
FIG. 10-2 is a flow for opening an account for a new work application, and FIG. 10-3 is a flow for closing an account opened for the work upon completion of the work.

The account opening flow shown in FIG. 10-2 is as follows.
Step 811: This is a step corresponding to (b) of FIG. 4B. The administrator instructs the administrator computer 100 to open an account by a method such as instructing a work application number from the administrator terminal 111. The account release block processing unit 102 of the administrator computer 100 reads the instructed work application data from the account application database 110, and checks and analyzes the work application content as described above.
Step 812: The work to be newly executed and an item for managing the account are added to the account correspondence table stored in the account database 104. In the account correspondence table shown in FIG. 10A, the management item “work application 3” corresponding to the work 3 requested to open the account is added to the account correspondence table in the state (a).
Step 813: One account requested to be released is extracted from the work application data read from the account application database 110 in step 811. “Account 1” is extracted from the work application data of work 3 in FIG. When the process of “Account 1” is completed, Step 813 is executed again through Step 817 described later, and “Account 4” is extracted.
Step 814: Check the account correspondence table and check whether the extracted account has already been opened by another work application. Since “Account 1” has already been opened by “Work application 1”, Step 815 is skipped and the process proceeds to Step 816. If “account 4” is extracted, “account 4” is not open, and the process proceeds to step 815.
Step 815: Log in to the corresponding server according to the procedure described in FIG. 4-2 to FIG. 8-2, and release the requested account (“Account 4” in work application 3 in FIG. 10-1).
Step 816: Data indicating that “account 1” and “account 4” are used in operation 3 is added to the account correspondence table.
Step 817: It is determined whether or not another account exists in the work application data read in Step 811. When the processing of “account 1” is completed, there is another “account 4”, and the process returns to step 813. When the processing of “account 4” is completed, there is no other account to be processed, and the process proceeds to step 818.
Step 818: Notify the work applicant that the account has been opened and the password for logging in to the account.

The account closing flow shown in FIG. 10-3 is as follows.
Step 821: When the worker reports the end of the work to the administrator, the administrator instructs the administrator computer 100 from the administrator terminal 111 to close the account released by the work application. FIG. 10C is an example of closing work 1, and the account release block processing unit 102 reads the instructed work application data, that is, work application data 1 from the account application database 110.
Step 822: An account is extracted from the read work application data. First, “account 1” is extracted from the work application data 1. When the processing of “Account 1” is completed, Step 822 is executed again through Step 827 described later, and “Account 3” is extracted.
Step 823: Check the account correspondence table stored in the account database 104, and check whether the account extracted in step 822 is used in other work.
Step 824: The account used in other work cannot be closed. Since “account 1” in FIG. 10A is used in operation 3, the process proceeds to step 826. If the account extracted in step 822 is “account 3”, there is no work using “account 3”, and the process proceeds to step 825.
Step 825: Log in to the corresponding server according to the procedure described in FIGS. 4-2 to 6-2 and FIGS. 8-1 to 9-2, and request the account (“Work Application 1” in FIG. 10-1). “Account 3”) is blocked.
Step 826: Delete data indicating that “account 1” and “account 3” in the account correspondence table are used in operation 3.
Step 827: Check whether there are other accounts to be blocked in the work application data. If it remains, the process proceeds to step 822, and the remaining account is closed. If there is no remaining account to be blocked, the process proceeds to step 828, and the blocking process in the work application data is terminated.

In the present invention, in a system composed of a plurality of servers managed by different OSs, application data for requesting release of a work account necessary for server maintenance is stored in the account application database 110. In addition, a command for instructing the OS to open / close an account and change a password is stored for each OS. When the system administrator specifies work application data that requires the release of an account by the work application number or the like, the administrator computer 100 identifies the server of the requested account and the OS of the server, and issues a command suitable for the OS. Read and execute. Also, when closing an account that is no longer required due to the end of maintenance, the administrator automatically closes the related account by specifying the work application number and instructing the account to be closed.
With the configuration of the present invention, the administrator creates a login command, an account release command, etc. corresponding to the OS when opening the account requested by the maintenance worker and setting the password, and closing the account executed when the maintenance is completed. For example, it is not necessary to perform an operation in consideration of the type of OS, and the account can be opened or closed quickly and accurately.
Further, in another embodiment of the present invention, a configuration is adopted in which work such as maintenance performed in the system and an account opened for each work are associated and managed in an integrated manner. With this configuration, in a situation where a plurality of maintenance operations are performed at the same time, it is possible to prevent an erroneous operation such as instructing to open an account that has already been opened, or closing an account that is being used for other operations. It becomes possible, and the burden on the administrator and the work time can be reduced.

Schematic diagram of an account opening and closing system according to the present invention The figure which shows the example of GUI of the system and program which concern on this invention The figure which shows the example of the account database which concerns on this invention The figure which shows the flow of control according to the type of command which concerns on this invention The figure which shows the flow of control of the system and program which concern on this invention Flow chart of initial processing of system and program according to the present invention Diagram showing HPUX and Open-VMS login commands Flow chart of login processing of system and program according to the present invention Figure showing HPUX and Open-VMS Unlock command Flow chart of account release processing of system and program according to the present invention Figure showing HPUX and Open-VMS password change commands Flow diagram of password change processing of system and program according to the present invention Figure showing Lock command of HPUX and Open-VMSOS Flow chart of account closing process of system and program according to the present invention Example of account correspondence table Diagram of account correspondence table management flow when opening an account Diagram of the account correspondence table management flow when an account is closed Figure showing the conventional account opening procedure

Claims (2)

A system having a plurality of servers,
The system
Work application data input means for entering work application data for applying for account opening or closing,
Account release block processing means for sending an account release command or block command to the server,
Account correspondence table means for storing the correspondence between the work application for releasing the account and the account released by the work application;
The account opening block processing means includes:
Means for storing, in the account correspondence table means, data for associating a work application instructing the release of an account and an account designated by the work application;
Means for accepting a work application instructing account closure and referring to the account correspondence table means to determine an account that can be closed;
A system comprising: means for transmitting a command for closing the determined account to a server. An account opening / closing program for controlling opening / closing of accounts of a plurality of servers by a computer,
A step of inputting work application data for instructing to open an account;
Storing data associating the work application with the open account in an account correspondence table according to an account release instruction;
Sending an account release command to the account server specified by the account release instruction;
A step of inputting work application data for instructing account closure;
Selecting an account to be blocked by referring to the account correspondence table according to the instruction;
Sending a block command to the selected account server to be blocked;
A program comprising the step of deleting, from the account correspondence table, data associating the work application instructed to be closed with an open account.

Images