JPS6272049A - Resource using control method in information processing system - Google Patents

Abstract

PURPOSE:To decrease the burden of individual users by providing a step to receive and read the card where using right information is recorded, the step to preserve the using right information, the step to select and the step to decide the propriety of the resource using request. CONSTITUTION:A system controller 11 selects the right information corresponding to each 'DB' of the data base sub-system designated by the command from a using right information group 32 received and held from a terminal equipment 21 and sends to a data base sub-system DB. (72) When the data base sub-system DB investigates of the user identifying code of the received right information and is judged to have the using right, the sub-system reports the using permission to the system controller 11. (73) The system controller 11 sends the message saying to permit the use to the terminal equipment 21. (74) Thereafter, when the data setting name is designated and the access is requested, the data base sub-system DB investigates and judges the information using code of the right information received earlier.

Description

[Detailed Description of the Invention] [Field of Application of the Invention] The present invention relates to the management of resource usage by users in an information processing system shared by a plurality of users.
In particular, the present invention relates to the management of resource usage in a shared information processing system including a plurality of resources whose usage is determined based on different usage authority information.

[Background of the Invention] A database system is a typical information processing system that is shared by a plurality of users and where management of resource usage by individual users is important. For database systems, in order to prevent unauthorized use of information or intentional destruction of information by users without usage authority,
It is essential to have a security mechanism that excludes users who do not have usage rights, and this security system checks the user identification code given to each user with usage rights, and the information set in advance for each information group. Information usage code (
For example, a data set password) is used.

Recently, as the use of databases has become more active, there is an increasing demand for integrated use of multiple databases of the same type or different types. One effective way to meet this request is to
It is the construction of a single complex system by integrating multiple existing database systems. Such complex systems typically include multiple database subsystems (i.e., database management systems) and multiple messaging subsystems that manage message exchange between these database subsystems and numerous users. Moreover, these subsystems were designed and developed independently. Therefore, each subsystem has its own security mechanism using its own user identification code and information access code, so that users of the complex have separate user identification codes and information access codes for each subsystem. For each subsystem that has a code and is to be used, an appropriate user identification code or information use code must be selected and input, which is extremely troublesome.

Regarding security protection in a complex system in which there are multiple institutions collaborating, such as a group of banks that have an online business partnership, Japanese Patent Application Laid-open No. 124653/1983 describes how to protect the security of each credit card issued by each institution. A transaction terminal is described that is capable of receiving and securely processing user identification numbers held therein for user authentication.

However, users of this device must maintain separate credit cards for each institution they use.
Furthermore.

It is necessary to remember the user identification number registered with each institution.

The above circumstances are not limited to security protection in complex database systems, but are generally applicable to various resources (subsystems,
The same applies to shared systems in which permission or disapproval of use of data, etc.) by individual users is determined based on different usage authority information (user identification codes, passwords, etc.).

[Purpose of the invention]

An object of the present invention is to maintain the usage permission determination function for each resource in an information processing system that includes a plurality of resources, each of which is determined to be permitted to be used by an individual user based on separate usage authority information. At the same time, the aim is to reduce the burden on individual users in responding to such demands.

[Summary of the invention]

According to the present invention, usage authority information (user identification code, password, etc.) for various resources (subsystems, data, etc.) that can be used by each user is stored in one card (magnetic card, IC card, etc.). recorded. When a user wants to use any resource, this card is inserted into a terminal device and usage authority information is read out.

All of the read usage authority information is stored within the system (for example, within the system controller or within the terminal device). After that, when the user operates the terminal device to specify a resource and requests its use, usage authority information for the requested resource is selected from the stored usage authority information, and permission or disapproval of usage is determined based on it. Ru. If each resource is equipped with a usage permission determination mechanism, the selected usage authority information is sent to the corresponding resource,
There, a determination is made as to whether or not the use is permitted.

[Embodiments of the invention]

FIG. 2 schematically represents a database system from a functional perspective as an example of an information processing system consisting of a plurality of subsystems. Under the management of the system controller 11 that controls and manages the entire system, a message controller 11 that manages the sending and receiving of messages between the system and the user
Subsystem 12 (subsystem name MA, MB,...
) and a database subsystem that manages the database (so-called database management system)13
A group of (subsystem names DA, DB, DC, . . . ) exists. Each of these subsystems includes a usage permission determination mechanism 14.15 for security protection.

FIG. 3 shows an external appearance of an example of a secure terminal device used to access the system of FIG. 2 in accordance with the present invention. This terminal device! 21 is the display
Screen 22. Card insertion slot 23. Power switch 24
and a keyboard 25. Terminal device connected to the system! 21 is a group of message subsystems 1
managed by a selected one of 2. The user uses this terminal device! 21 to access the system shown in FIG.
3 must be inserted.

This memory card is a card such as a magnetic card or an IC card that can record information in a machine-readable format. Each user has his or her own card, which contains the names of several subsystems available to him, his user identification code for each of these subsystems, and the control of these subsystems. It consists of an information usage code that indicates usage authority for certain information.

A group of usage authority information unique to each user is recorded (
5), the user identification code may be, for example, a user identification name for identifying an individual user and/or a secret number given to the user by the respective subsystem to verify the user. (password) can be used. In addition, the above-mentioned information usage code may include, for example, the names (for example, file names) of some information groups that are allowed to be used, and the information given to the user by the subsystem that manages the use of these information groups. A secret number (password) can be used. The permission to use information may be set for each file (data set), each storage medium, or any other suitable information unit that is convenient for management.

FIG. 4 shows the configuration of a system on which an example of the usage management process to be explained later is based.

Message subsystem 12a (subsystem name MA
), database subsystems 13b (subsystem name DB) and 13c (subsystem name DC), and a system controller 11 that manages these subsystems. The database subsystem 13b is
Dataset 41a (dataset name DSIA) and 4
1b (dataset name DSIB), and the database subsystem 13c manages datasets 42a (dataset name DS2A) and 42b (dataset name D
S2B) and 42c (data set name D82C). Permission to use information groups is set for each dataset. The subsystems 12a, 13b, and 13c have usage permission/denial determination mechanisms 14a, 15b, respectively, for security protection.
, 15c.

FIG. 5 shows a group of usage authority information recorded on a memory card of a certain user who uses the system of FIG.

Usage authority information group 32 recorded on memory card 31
For each subsystem that this user has authority to use, each authority information set 50(a) includes an authority information set 5°(al b, Q).

b, c) contain the corresponding subsystem name 51 and the user identification code 52 of that user regarding the use of this subsystem, and furthermore a set of authorization information for the database subsystem 50 (b, c) I: , the user identification code 5λ, which includes an information usage code 53 regarding the data set that can be used by this user under the management of the subsystem, consists of a user identification name 521 and a password 522. The information usage code 53 consists of an available data set name 531 and a password 532. Each set of authorization information for a database subsystem may include multiple information usage codes 53. The usage authority information group 32 on the memory card shown in FIG. /MP
A, UIDB/DPB, and UIDC/DPC are used to indicate that it can be used. It also means that this user can create datasets belonging to the database subsystem DB, and
This shows that data sets DS2A and D32B belonging to C can be used using passwords DSPCI and DSPC2, respectively.

1A and 1B show an example of the usage management process according to the present invention. Referring to FIG. 1A, when the user wants to use the system, the user transfers the memory card 31 to the terminal device (Figure), and then use the keyboard 25 to log on (L) to start using the system.
OGON) command and specify the name of the message subsystem you wish to use (rMAJ in this example) (60), terminal device! 21 reads the usage authority information group 32 from the inserted memory card 31 in response to the logon command, and sends it to the system controller 11.
(61), the system controller 11 stores the received usage authority information group 32 in an internal format, and
From this information group 32, the authority information set 50 (a) corresponding to the message subsystem name rMAJ specified in the logon command is selected and sent to the corresponding message subsystem MA (12a). 62).

The message subsystem MA uses its usage permission/denial determination mechanism (not shown) to determine the received authority information set 50.
The user identification code 52 in (a) is compared with the registered user identification code to authenticate the user, and if it is determined that the user has the authority to use the message subsystem MA, the user is permitted to use the message subsystem MA. is reported to the system controller 11 (63), and a message is sent to the terminal device 21 indicating that it accepts a message from the user (64), and the terminal device 21 displays this.

From then on, this user will be unable to send and receive messages via the terminal device 21 and the message subsystem MA (12a) until the user inputs a logoff (LOGOFF) command from the terminal device 21 to declare the end of using the system. can.

On the other hand, when it is determined in the user authentication in the message subsystem MA that the user does not have the authority to use the message subsystem MA, the message subsystem MA must report this to the system controller 11. 63), upon receiving this, the system controller 11 sends a message to the terminal device 21 to the effect that the message subsystem MA is unavailable (65).

Next, referring to FIG. 1B, the user who is permitted to communicate via the message subsystem MA then issues a CONNECT command to declare the start of use of the database subsystem to the database he or she wishes to use. - Subsystem name - Subsystem MA transfers this command to the system controller 11 (71).

The system controller 11 selects the authority information set 50 (b) corresponding to the database subsystem name rDBJ specified by the command from the usage authority information group 32 received and held by the terminal device 21, Send this to the relevant database subsystem DB (72)
, the database subsystem DB uses its usage permission/denial determination mechanism (not shown) to determine the set of authority information 5 it has received.
0 (b), the user is authenticated, and it is determined that the user has the authority to use the database subsystem DB.

Report usage permission to system controller 11 (7
3) Upon receiving this, the system controller 11 sends a message to the message subsystem M to permit the user to use the database subsystem DB.
It is sent to the terminal device 21 via A (74). However, if it is determined that the user does not have usage authority, a message indicating that the database subsystem DB cannot be used is sent to the terminal device 21 via the same route as described above.

Thereafter, when the user specifies the data set name and requests access to it, the database subsystem DB uses its usage permission determination mechanism to obtain the set of authority information 50 previously received from the system controller 11.
The information use code 53 in (b) is checked to determine whether the user has the right to use the data set. Then, the requested access is executed only if it is determined that the user has usage authority.

6A and 6B show another example of the usage management process according to the present invention. In this type of usage management process, the usage authority information group 32 read from the memory card 31 is not stored in the system controller 11 The basic difference from the process shown in FIG. 1 is that the process is held inside the terminal device 21. The procedure until the user inputs the logon command is the same as the process shown in FIG. Referring to FIG. 6A, when the user specifies the message subsystem name rMAJ that he/she wishes to use and inputs a logon command (60), the terminal device 21 uses the memory card 31 inserted. The authority information group 32 is read out and stored in a predetermined area of the built-in memory, and the logon and
Each message subsystem rM specified in the command
Selects the authority information set 50 (a) corresponding to AJ and sends it to the designated message subsystem MA (12a) via the system controller 11 (6
1), message subsystem MA.

Using the usage permission/denial determination mechanism (not shown), the user identification code 52 in the received authority information set 50 (a) is
If it is determined that the user has the authority to use the message subsystem MA, the usage permission is reported to the system controller 11 (62), and the user is sent to the terminal bag [21]. , sends a message indicating that it accepts messages from that user (63)
, the terminal device 21 displays this. Thereafter, this user can send and receive messages via the terminal device 21 and the message subsystem MA (12a) until he inputs a logoff command from the terminal bag v121 to declare the end of using the system.

On the other hand, when it is determined in the user authentication in the message subsystem MA that the user does not have the authority to use the message subsystem MA, the message subsystem MA must report this to the system controller 11. 62), upon receiving this, the system controller 11 sends a message to the terminal device 21 to the effect that the message subsystem MA is unavailable (64).

Next, referring to FIG. 6B, the user who is permitted to communicate via the message subsystem MA then sends the connect command for declaring the start of use of the database subsystem to the database subsystem that he/she wishes to use. When inputting the system name rDBJ together with the keyboard 25 of the terminal device 21 (70), the terminal device 21 selects the database subsystem specified by the command from the usage authority information group 32 read from the card and stored in the memory. The authority information set 50(b) corresponding to the system name rDF3J is selected and sent to the corresponding database via the message subsystem MA and the system controller 11.
The database subsystem DB uses its usage permission determination mechanism (not shown) to check the user identification code 52 in the received authority information set 50 (b) (71). If the user is authenticated and it is determined that the user has the authority to use the database subsystem DB, the system controller 11 reports the usage permission to the system controller 11 (72). That user has a database
A message indicating permission to use the subsystem DB,
The terminal device 21 via the message subsystem MA
(73) If it is determined that the user does not have usage authority, a message indicating that the database subsystem DB cannot be used is sent to the terminal device 21 via the same route as described above.

Thereafter, when the user specifies the data set name and requests access to it, the database subsystem DB uses its usage permission determination mechanism to use the authority information set 50 ( The information usage code 53 in b) is checked to determine whether the user is authorized to use the data set. Then, the requested access is executed only if it is determined that the user has usage authority.

The embodiments shown in FIGS. 1A and 1B require that memory space sufficient to accommodate all of the usage authority information of various users simultaneously using the system be prepared in advance in the system controller. I need. Such a requirement is not present in the embodiment shown in FIGS. 6A and 6B.

〔Effect of the invention〕

According to the present invention, the user is freed from the trouble of having to create and use different user identification codes and passwords for each resource, and furthermore, the use permission/denial function for each resource is completely maintained, and the security of the system is maintained. It will be done. Furthermore, it becomes easy to incorporate an existing system with its own usage permission/denial mechanism into the system 11 as a subsystem.

fFA of the drawings Fig. 1A and l"l are schematic diagrams of an embodiment of the present invention, Fig. 2 is a block diagram of an example of an information processing system to which the present invention can be applied, and Fig. 3 is a diagram of an embodiment of the present invention. FIG. 4 is a block diagram of an information processing system to which an embodiment of the present invention is applied, and FIG. 5 is an external view of an example of a terminal device used in an embodiment of the present invention. Figures 6A and 6B showing information are schematic diagrams of other embodiments of the present invention.

11 ・System controller, 12.12a...
Message subsystem as a resource.

13, 13b, 13c-database subsystem as resource, 21...terminal device, 2
3...Card insertion slot, 31...Card, 32...
Usage authority information group.

Claims (1)

[Scope of Claims] 1. A plurality of resources, whose use is determined to be permitted or disallowed by each user based on individual usage authority information, are managed by a system controller and shared by a plurality of users via a terminal device. In the information processing system, the terminal device accepts and reads a card in which usage authority information for all of the resources available to a certain user is recorded; a step of storing the card in a system; a step of selecting usage authority information for a corresponding resource from the stored usage authority information in response to a resource usage request via a terminal device that accepts the card; and a step of selecting the usage authority information for the corresponding resource from the stored usage authority information; and determining whether the resource usage request is appropriate based on the information.
Resource usage management method. 2. In claim 1, each of the resources is provided with a usage request propriety determination mechanism, the selection step includes a step of transferring the selected usage authority information to the corresponding resource, and the determination step includes the step of transferring the selected usage authority information to the corresponding resource. A resource usage management method that is performed within the resource to which usage authority information has been transferred. 3. The resource usage management method according to claim 2, wherein the storing step stores the usage authority information in the system controller. 4. The resource usage management method according to claim 2, wherein the storage step stores the usage authority information in the terminal device, and the transfer step is performed via the system controller. 5. In claim 3 or 4, the plurality of resources include at least one database subsystem, and the database subsystem manages at least one information group and provides information for use by the database subsystem. The authority information includes a first usage authority part for the database subsystem itself and a second usage authority part for a group of information under the management of the database subsystem, and the determination step includes a first usage authority part for the database subsystem itself and a second usage authority part for the information group under the management of the database subsystem. a step of determining whether or not a usage request for the database subsystem itself is appropriate based on the first usage authority portion; and determining whether or not a subsequent usage request for the information group is appropriate or not based on the second usage authority portion of the usage authority information that has been transferred; a method for managing resource usage for security protection, comprising: determining based on the method;