JP2013109620A - Information system and authentication state management method thereof - Google Patents

Abstract

PROBLEM TO BE SOLVED: To appropriately perform an authentication process for access from an external system, and permit access to a plurality of servers with a single authentication process.SOLUTION: In an authentication server SVA1, a pseudo authentication process to an external system ES is performed using system identification information whose authenticity is secured between an information system SS and the external system ES as collateral, and an authentication state identifier (Cookie) showing an authentication result is issued. In a relay server SVR, a thread is prepared when a data operation request transmitted from the external system ES is received, and the authentication state identifier (Cookie) for the external system ES stored in an authentication state storage unit 22 is allocated to the thread and the thread is activated after it is confirmed that the authentication state identifier (Cookie) has been authenticated and is within an effective period. Then a data operation is executed after the data operation request is transferred to a service server SVS along with the authentication state identifier (Cookie).

Description

  The present invention relates to an information system in which a plurality of servers operate in cooperation, and an authentication state management method used in the information system.

  In order to perform data operations such as user registration / update and data registration for each server of an information system in which multiple servers operate in cooperation, authentication is performed for each server, and the system user who performs the operation is authorized. You need to make sure you have the correct access rights. In this case, it is very inconvenient for the system user to individually perform the authentication procedure with all the servers in the system.

  Therefore, a technique called single sign-on has been introduced that can notify the authentication status of the system user centrally to all servers in the information system by a single authentication procedure. Single sign-on is defined by, for example, SAML (Security Assertion Markup Language) or OpenID, and an attribute and processing of necessary authentication / authorization information is agreed in advance between servers in the system. For example, when the system user receives authentication from the server A, the authenticated certificate is inserted into the SOAP / HTTP message part and transferred to the server B. Using this single sign-on, once a system user is authenticated from any server in the system, it is possible to access other servers in the system without repeating the troublesome authentication procedure. This is very convenient (see, for example, Non-Patent Document 1 or 2).

Standard Corner: OASIS standard explanation “SAML”, Nihon Unitech Co., Ltd., [October 31, 2011 search], Internet <URL: http://www.utj.co.jp/xml/sta/saml.html> gihyo. jp DEVELOPER STAGE Special feature: "OpenID that can be used now 1st OpenID service to understand the mechanism of OpenID", [October 31, 2011 search], Internet <URL: http://gihyo.jp/ dev / feature / 01 / openid / 0001>

However, when an information system is linked with an external system having a different management policy and data manipulation in the information system is performed from the external system on behalf of the system user, there are problems to be solved as follows.
(1) When the data operation source is a system user, the authentication operation can be actively performed by an authentication procedure using an ID / password or an IC card. However, when the data operating source is an external system, a personal authentication procedure using an ID / password or an IC card cannot be used. For this reason, it is necessary to recognize that access for data operation from an external system is properly authenticated by some method.

  (2) Unlike access from an individual system user, access from an external system can be performed in multiple processes, and multiple threads are started simultaneously to improve performance. Is called. In this case, if the same certificate is shared by a plurality of threads, sessions for the plurality of threads being processed may be invalidated at the same time when the certificate expires.

  (3) If a certificate is issued for each thread in order to solve the problem described in (2), the authentication procedure must be executed each time, and the processing time required for data operation becomes longer. In addition, when access from a plurality of external systems occurs, access from a specific external system may occupy a thread and a certificate, and fairness among external systems cannot be maintained.

  The present invention has been made paying attention to the above circumstances, and the object of the present invention is to make it possible to properly perform authentication processing even for an access from an external system that cannot use a personal authentication procedure. It is an object of the present invention to provide an information system that is accessible to a plurality of servers by a single authentication process and an authentication state management method thereof.

  In order to achieve the above object, one aspect of the present invention is an information system in which a plurality of servers each storing data operate in cooperation and can communicate with an external system via a network. When system identification information whose authenticity is guaranteed between the system and the external system is held in advance, and the first data operation request including the system identification information of the external system is sent from the external system, the data A pseudo authentication process is executed by comparing the system identification information included in the operation request with the held system identification information, and the validity of the requesting external system is confirmed by the pseudo authentication process. In the case of authentication, an authentication status identifier representing the authentication result is issued. The issued authentication status identifier is stored, and when the second or subsequent data operation request is sent from the external system within the validity period of the authentication status identifier, the authentication status identifier is activated in response to the data operation request. By assigning the stored authentication status identifier to a thread and giving the assigned authentication status identifier to a data operation destination server together with a data operation request sent from the external system, The operation is performed on the existing data.

  Therefore, access from an external system that cannot use a personal authentication procedure using an ID / password, IC card, etc., by predefining system identification information that guarantees authenticity between the information system and the external system. However, it is possible to perform a pseudo authentication process with the system identification information as collateral. Also, the authentication status identifier issued by this pseudo authentication process is stored, and when a data operation request is sent from the same external system thereafter, the stored authentication status identifier is assigned to a thread to perform data operation. By executing this, the authentication status can be managed by the same mechanism as single sign-on.

One aspect of the present invention is also characterized by comprising the following aspects.
In the first aspect, it is determined whether the assigned authentication state identifier is valid or invalid, and if it is determined to be invalid, the pseudo authentication process is executed again to issue a new authentication state identifier. It is a thing.
In this way, it is possible to set an additional authentication condition such as an expiration date for the authentication state identifier, thereby further improving the reliability of the authentication state identifier.

In the second aspect, when assigning an authentication state identifier, an upper limit is set for the number of authentication state identifiers issued to one external system, and a plurality of threads are set in response to a data operation request from the same external system. Is prepared, the authentication status identifier is assigned to these threads within a range not exceeding the set upper limit value.
In this way, the number of threads that can be used simultaneously by one external system is limited. For this reason, it is possible to prevent a problem that the information system is occupied by one external system, and to maintain fairness among the external systems with respect to data operation requests from a plurality of external systems.

  That is, according to the present invention, it is possible to appropriately perform authentication processing even from an external system that cannot use a personal authentication procedure, and to access a plurality of servers by one authentication processing. An information system and an authentication state management method thereof can be provided.

The block diagram which shows the function structure of the information system which concerns on 1st Embodiment of this invention, and an external system. The flowchart which shows the processing procedure of the authentication state management in the information system shown in FIG. 1, and its processing content. The figure for demonstrating the content of the authentication status management process by the relay server of the information system shown in FIG. The block diagram which shows the function structure of the information system which concerns on 2nd Embodiment of this invention, and the external system which accesses this information system. The figure for demonstrating the content of the authentication status management process by the relay server of the information system shown in FIG.

Embodiments according to the present invention will be described below with reference to the drawings.
[First Embodiment]
(Constitution)
FIG. 1 is a block diagram showing functional configurations of an information system and an external system according to the first embodiment of the present invention. The information system SS and the external system ES can communicate with each other via the network NW. An IP (Internet Protocol) network is used as the network NW.

The information system SS includes a plurality of service servers SVS, a relay server SVR, and an authentication server SVA1, all of which are Web servers. In FIG. 1, only one service server SVS is shown for simplicity of illustration.
Each of the plurality of service servers SVS is an operation destination of data, and an operation destination data storage unit 42 that stores data such as personal information, and registration, change, and deletion of data in the operation destination data storage unit 42 are performed. A data operation unit 41 is provided.

The relay server SVR includes an authentication state holding unit 22 and a data operation relay unit 21.
The data operation relay unit 21 has the following processing functions.
(1) When a data operation request transmitted from an external system ES is received, a thread is prepared after confirming the requesting external system ES based on the system identification information included in the data operation request, and the authentication status Processing for requesting the holding unit 22 to assign an authentication status identifier representing an authentication result.

  (2) When an authentication state identifier is assigned from the authentication state holding unit 22 in response to the assignment request, it is determined based on the authentication state identifier whether the authentication state has been authenticated and is within the expiration date. processing.

  (3) If it is determined that the authentication status is authenticated and within the expiration date, the authentication status identifier is assigned to the prepared thread, the thread is started, and the data operation received earlier A process of transferring a request together with the authentication status identifier to the service server SVS to execute a data operation.

  (4) If it is determined that the authentication status is unauthenticated or expired, the authentication server SVA1 is requested to perform pseudo authentication and a new authentication status identifier is received, and the received new authentication status identifier Is stored in the authentication state holding unit 22. Then, a process of allocating the new authentication state identifier to the prepared thread and starting the thread, transferring it to the service server SVS together with the previously received data operation request, and executing the data operation.

  The authentication state holding unit 22 stores the authentication state identifier transferred from the data operation relay unit 21 in a memory. When an authentication status identifier allocation request is sent from the data operation relay unit 21, the stored authentication status identifiers are allocated up to a predetermined number.

The authentication server SVA1 includes an authentication data storage unit 32 and a pseudo authentication unit 31.
The authentication data storage unit 32 stores in advance information necessary for authenticating the system user and the external system ES. As information necessary for authenticating the system user, for example, the ID and password of the system user are used. As information necessary for authenticating the external system ES, system identification information of the external system ES is used. This system identification information is information guaranteed to uniquely indicate an external system by technical or operational measures, and for example, an IP address or a server certificate is used.

  When the authentication request for the external system ES is sent from the relay server SVR, the pseudo authentication unit 31 compares the system identification information included in the authentication request with the system identification information stored in the authentication data storage unit 32. By doing so, a pseudo authentication process is performed. When the validity of the external system ES is confirmed, a process of issuing an authentication status identifier for the external system ES and returning it to the requesting relay server SVR is performed. For example, a cookie is used as the authentication state identifier.

The external system ES includes, for example, a web server owned by a local government, and includes a data operation request unit 11 and an operation source data storage unit 12.
The operation source data storage unit 12 stores data such as personal information to be registered in the information system SS. The data operation request unit 11 performs a process of transmitting an operation request for the data to the information system SS based on the data stored in the operation source data storage unit 12 on a regular basis or according to an operator's operation, for example. . At this time, the system identification information of the external system ES is added to the data operation request.

(Operation)
Next, an authentication state management operation by the information system configured as described above will be described. FIG. 2 is a flowchart showing the processing procedure and processing contents.
In this case, an organization that handles personal information independently, such as a local government, requests data operation from the information system SS using the external system ES that it operates, and this causes a service server in the information system to A case where user data is registered, updated, or deleted will be described as an example.

  In the authentication data storage unit 32 of the authentication server SVA1 in the information system SS, system identification information whose authenticity is ensured between the information system SS and the external system ES, for example, the IP address and server certificate of the external system ES are stored. Saved. In FIG. 1, only one external system ES is shown for simplicity of illustration, but there are actually a plurality of external systems. In this case, the authentication data storage unit 32 stores system identification information for each of the plurality of external systems.

  When the external system ES transmits a data operation request, the data operation request is received by the relay server SVR of the information system SS. Under the control of the data operation relay unit 21, the relay server SVR first confirms the requesting external system ES based on the system identification information included in the received data operation request, such as an IP address or a server certificate. (Step S1). Based on the confirmation result, a thread corresponding to the requesting external system ES is prepared in step S2, and the authentication status holding unit 22 is requested to assign an authentication status identifier.

  Upon receiving the allocation request, the authentication status holding unit 22 first selects an authentication status identifier (for example, cookie) corresponding to the corresponding external system ES based on the system identification information included in the allocation request. It is determined in step S3 whether or not the number of assigned identifiers has already reached the preset upper limit value. As a result of this determination, if the number of assigned authentication status identifiers has not reached the upper limit, one stored authentication status identifier is read and returned to the requesting data operation relay unit 21 (step S4). If the number of assigned (in use) authentication status identifiers has reached the upper limit, the process waits until the authentication status identifier in use is released.

  Based on the authentication state described in the authentication state identifier returned from the authentication state holding unit 22, the data operation relay unit 21 determines whether the authentication state identifier has been authenticated and is valid. To do. If the authentication status is authenticated and valid, the prepared thread is activated, and the authentication status identifier is added to the data operation request received from the external system ES previously. The data operation request and the authentication status identifier are transferred to each service server SVS that is the operation destination.

The operations of the authentication state holding unit 22 and the data operation relay unit 21 will be described more specifically. FIG. 3 is a diagram showing this operation. Now, it is assumed that five threads TH1 to TH5 are prepared for the external system ES and that up to four cookies C1 to C4 can be assigned as authentication status identifiers. In this case, the stored cookies are selected and assigned to the threads TH1 to TH4 one by one in the order of activation, and as a result, the threads TH1 to TH4 are activated. However, since all the cookies C1 to C4 for the external system ES have already been assigned to the thread TH5, the assignment is not performed. For this reason, the thread TH5 is not activated.
The data operation relay unit 21 uses the activated threads TH1 to TH4 to transfer a data operation request and an authentication state identifier to different service servers SVS.

  On the other hand, the authentication state identifier (Cookie) for the external system ES is not yet stored in the authentication state holding unit 22, or the authentication state described in the authentication state identifier (Cookie) is unauthenticated or stored even if stored. Suppose that it has expired. In this case, the data operation relay unit 21 sends an authentication request to the authentication server SVA1 as shown in FIG. This authentication request includes the system identification information of the external system ES.

  Upon receiving the authentication request, the authentication server SVA1 controls the system identification information stored in advance in the authentication data storage unit 32 in step S6 under the control of the pseudo-authentication unit 31. Authentication is performed by checking with. In other words, a pseudo authentication process for the external system ES is performed using the system identification information whose authenticity is guaranteed between the information system SS and the external system ES as collateral. When the validity of the external system ES is confirmed by this pseudo authentication process, the authentication status identifier (cookie) for the external system ES is reissued and returned to the requesting relay server SVR.

  The data operation relay unit 21 of the relay server SVR stores the returned authentication state identifier (Cookie) in the authentication state holding unit 22 and receives the reissued authentication state identifier (Cookie) from the external system ES. It is added to the data operation request and transferred to the service server SVS as the operation destination.

  When a data operation request is sent from the relay server SVR, the service server SVS determines whether or not the data operation request is approved based on the authentication status identifier (cookie) sent together with the data operation request. If it is determined in step S7 and approved, in step S8, user data is registered, changed, or deleted in the operation destination data storage unit 42 in accordance with the content of the data operation request. When the data operation ends, information representing the operation result is returned to the relay server SVR.

  When the relay server SVR receives the information representing the operation result, the relay server SVR terminates the thread corresponding to the data operation in step S8 under the control of the data operation relay unit 21, and the authentication state assigned to the thread. The identifier (cookie) is returned to the authentication status holding unit 22. The authentication status holding unit 22 stores the returned authentication status identifier (Cookie) as an empty authentication status identifier. Information representing the operation result is returned from the data operation relay unit 21 to the requesting external system ES via the network NW.

(Effects of the first embodiment)
As described above in detail, in the first embodiment, in the authentication server SVA1, pseudo-authentication for the external system ES is ensured by using the system identification information whose authenticity is guaranteed between the information system SS and the external system ES. Processing is performed and an authentication status identifier (cookie) representing the authentication result is issued. When the relay server SVR receives a data operation request transmitted from the external system ES, a thread is prepared, and the authentication status identifier (Cookie) for the external system ES held in the authentication status holding unit 22 is used. After confirming whether it is authenticated and within the validity period, the thread is activated by assigning it to the thread, and the data operation request is transferred to the service server SVS together with the authentication status identifier (Cookie) to perform the data operation. To be executed.

  Therefore, it is possible to perform a pseudo authentication process using the system identification information as collateral even for an access from an external system ES that cannot use a personal authentication procedure using an ID / password or an IC card. Become. Further, the authentication state identifier (Cookie) issued by the pseudo authentication process is stored, and when the data operation request is sent from the same external system ES, the stored authentication state identifier (Cookie) is stored. By assigning to the thread and executing the data operation, the authentication state can be managed by the same mechanism as single sign-on.

  Further, when the authentication state identifier (Cookie) for the external system ES is not yet stored in the authentication state holding unit 22, or the authentication state described in the authentication state identifier (Cookie) is unauthenticated or stored If the expiration date has expired, the authentication server SVA1 performs the pseudo-authentication and reissues the authentication status identifier. Therefore, it is possible to set an additional authentication condition such as an expiration date for the authentication status identifier, thereby further improving the reliability of the authentication status identifier.

  Furthermore, when assigning an authentication status identifier (cookie), an upper limit is set for the number of authentication status identifiers assigned to one external system ES, and a plurality of threads are set in response to data operation requests from the same external system ES. When activated, an authentication state identifier (cookie) is assigned to these threads in a range not exceeding the set upper limit value.

  In this way, the number of threads that can be used simultaneously by one external system ES is limited, and as a result, a problem that access to the information system SS is occupied by one external system ES is prevented.

[Second Embodiment]
FIG. 4 is a block diagram showing a functional configuration of an information system according to the second embodiment of the present invention and an external system accessing the information system. In the figure, the same parts as those in FIG.

  A plurality of external systems ES1 and ES2 (two examples are shown in the figure) can be connected to the information system SS via the network NW. In addition, an operation staff terminal MT used by an operator of the system can be connected to the information system SS via the network NW or directly.

  The external systems ES1 and ES2 include, for example, Web servers operated by different local governments or different departments of one local government, and include data operation request units 111 and 112 and operation source data storage units 121 and 122, respectively. The functions of the data operation request units 111 and 112 and the operation source data storage units 121 and 122 are the same as those of the data operation request unit 11 and the operation source data storage unit 12 described in FIG.

On the other hand, the authentication server SVA2 of the information system SS includes a regular authentication unit 33 in addition to the pseudo authentication unit 31 and the authentication data storage unit 32.
The regular authentication unit 33 is included in the authentication request when the authentication request including the ID and password of the operation staff transmitted from the operation staff terminal MT is transferred from the data operation relay section 21 of the relay server SVR. The person in charge of the operation is authenticated by comparing the ID and password to be stored with the ID and password stored in the authentication data storage unit 32. When the validity of the operation staff is confirmed, an authentication status identifier for the operation staff is issued. Also in this case, Cookie is used as the authentication status identifier. The issued authentication status identifier (Cookie) is stored in a browser on the operator terminal MT.

  The authentication state holding unit 22 of the relay server SVR sets an upper limit number of authentication state identifiers assigned to each of the plurality of external systems ES1 and ES2. Then, authentication status identifiers are assigned to the external systems ES1 and ES2 so as not to exceed the set upper limit number.

Next, an authentication state management operation by the information system SS configured as described above will be described. FIG. 5 is a diagram for explaining the operation contents.
For example, it is assumed that the upper limit number of authentication status identifiers (Cookies) that can be used by the external systems ES1 and ES2 is set to “3”, and the number of threads that can be activated by the relay server SVR is set to “4”. In this state, it is assumed that a data operation request arrives from the external system ES1, and the data operation relay unit 21 of the relay server SVR tries to start four threads TH1 to TH4 in response to this request. However, at this time, since the upper limit number of cookies that can be used by the external system ES1 is set to “3”, the authentication state holding unit 22 of the relay server SVR has three of the four threads TH1 to TH4. The three cookies C1-1 to C1-3 for the external system ES1 are assigned only to the threads TH1 to TH3. As a result, only three threads TH1 to TH3 among the four threads TH1 to TH4 are activated.

  In this allocation, the data operation relay unit 21 recognizes that the cookie C1-1 to C1-3 has been authenticated by the information indicating the authentication state described in the cookie for each cookie C1-1 to C1-3 and is within the expiration date. It is determined whether or not there is. The Cookies C1-1 to C1-3 are assigned to the threads TH1 to TH3 only when it is determined that they have been authenticated and are within the expiration date.

  In this state, it is assumed that a data operation request comes from the external system ES2. Then, in the data operation relay unit 21 of the relay server SVR, the upper limit value of the number of threads that can be started by the relay server SVR is set to “4”, and three of these are already started for the external system ES1. Therefore, the remaining one thread TH4 is prepared for the external system ES2. Then, the authentication state holding unit 22 notifies the data operation relay unit 21 of one of the cookies C2-1 to C2-3 that can be used by the external system ES2, and the data operation relay unit 21 notifies the notified CookieC2 -1 is assigned to the activated thread TH4 after confirming that it is authenticated and within the validity period according to the authentication state described in the Cookie C2-1. As a result, the thread TH4 is activated for the external system ES2.

  On the other hand, when the person in charge of operation performs data operation of the information system SS using his / her terminal MT, the person in charge of the operation is transmitted including the person in charge ID and the password. Then, in the information system SS, the person-in-charge ID and password included in the data operation request are transferred from the relay server SVR to the authentication server SVA.

  In the authentication server SVA, the regular authentication unit 33 verifies the ID and password of the operation person transmitted from the operation person terminal MT with the ID and password stored in the authentication data storage unit 32, thereby Authentication is performed. When the validity of the operator is confirmed, an authentication status identifier (Cookie) for the operator is issued, and this authentication status identifier (Cookie) is stored in the browser on the operator terminal MT. .

  Therefore, when a data operation is subsequently performed on the service server SVS or another server in the information system SS at the operation staff terminal MT, the operation staff terminal MT requests the data operation and the authentication stored in the browser. A state identifier (Cookie) is transmitted to the information system SS. On the other hand, in the information system SS, the data operation request and the authentication status identifier (Cookie) are directly transferred to the service server SVS to be accessed without going through the relay server SVR. Upon receiving this data operation request, the service server SVS makes an inquiry about the authentication status identifier (Cookie) to the authentication server SVA, and the authentication status identifier (Cookie) received as a result and the authentication status identifier managed by the authentication server SVA. If (Cookie) corresponds, the data operation is executed. Then, information representing the operation result is returned to the requesting operation staff terminal MT.

  If there are a plurality of service servers in the information system SS and a data operation request is sent from the operator terminal MT to the plurality of service servers, each of these service servers is connected to the authentication server SVA. Authentication status identifier (Cookie) approval processing is performed between them, and if approved, data operation is executed according to the request contents, and information representing the result is returned to the requesting operation staff terminal MT. That is, the person in charge of operation can perform data operations in parallel without executing the authentication procedure for each of the plurality of service servers in the information system SS.

  As described above, according to the second embodiment, in response to a data operation request from the external systems ES1 and ES2, threads are activated within the range of the number of threads (4) that the relay server SVR can simultaneously activate, and Cookies are assigned to the activated thread so as not to exceed the upper limit (three) of the preset number of assigned cookies. For this reason, the number of threads that can be used simultaneously for each of the external systems ES1 and ES2 is limited by the upper limit number of cookies, and a problem that one external system occupies all threads is prevented. Therefore, it is possible to keep the fairness between the external systems ES1 and ES2 to a minimum when performing data operations on the information system SS.

[Other Embodiments]
In each of the embodiments described above, the case where one service server SVS is arranged in the information system SS has been described as an example. However, the present invention can be applied even when a plurality of service servers are arranged. Further, the number of threads that can be activated by the relay server SVR and the upper limit number of authentication status identifiers assigned to one external system ES1, ES2 are not limited to “4” and “3”, respectively. If the upper limit number of authentication status identifiers is small, other numbers may be set.

  In addition, the configuration of the information system and the external system, the authentication status management processing procedure and processing contents by the information system, the type of data to be operated, the type of network, and the like are variously modified without departing from the scope of the present invention Can be implemented.

  In short, the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the components without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in each embodiment. Furthermore, you may combine suitably the component covering different embodiment.

  SS ... Information system, ES ... External system, NW ... Network, SVR ... Relay server, SVA1, SVA2 ... Authentication server, SVS ... Service server (operation destination server), 11 ... Data operation request unit, 12 ... Operation source data storage unit , 21 ... Data operation relay unit, 22 ... Authentication state holding unit, 31 ... Pseudo authentication unit, 32 ... Authentication data storage unit, 33 ... Authentication unit, 41 ... Data operation unit, 42 ... Operation destination data storage unit.

Claims (6)

In an information system in which a plurality of servers each storing data operate in cooperation and can communicate with an external system via a network,
Means for retaining system identification information whose authenticity is ensured between the external system and the information system;
When the first data operation request including the system identification information of the external system is sent from the external system, the system identification information included in the data operation request is compared with the held system identification information. A pseudo-authentication unit that issues an authentication status identifier representing an authentication result when the validity of the requesting external system is confirmed by the pseudo-authentication process;
The issued authentication state identifier is stored, and when a second or subsequent data operation request is sent from the external system within the validity period of the authentication state identifier, the thread activated in response to the data operation request Authentication state holding means for assigning the stored authentication state identifier to the storage device;
Relay means for transferring the assigned authentication status identifier to a data operation destination server together with a data operation request sent from the external system, and executing data operation on the data stored in the server; An information system characterized by   A means for determining whether the assigned authentication status identifier is valid or invalid, and requesting a pseudo authentication process to the pseudo-authentication means and issuing a new authentication status identifier if it is determined to be invalid The information system according to claim 1, further comprising:   The authentication status holding means sets an upper limit value for the number of authentication status identifiers issued to one external system, and when trying to start a plurality of threads in response to a data operation request from the same external system 3. The information system according to claim 1, wherein the authentication status identifier is assigned to these threads within a range not exceeding the set upper limit value. An authentication status management method executed in an information system in which a plurality of servers each storing data operate in cooperation and can communicate with an external system via a network,
A process in which the information system holds system identification information whose authenticity is ensured between the information system and the external system;
When the first data operation request including the system identification information of the external system is sent from the external system, the information system includes the system identification information included in the data operation request as the held system identification information. Performing a pseudo authentication process by collating, and issuing an authentication status identifier representing an authentication result when the validity of the requesting external system is confirmed by the pseudo authentication process;
When the information system stores the issued authentication status identifier and a second or subsequent data operation request is sent from the external system within the validity period of the authentication status identifier, in response to the data operation request Assigning the stored authentication state identifier to an activated thread;
The information system gives the assigned authentication status identifier to a data operation destination server together with the data operation request sent from the external system, and executes the data operation on the data stored in the server. An authentication state management method comprising:   Determining whether the assigned authentication status identifier is valid or invalid, and further comprising a step of re-executing the pseudo-authentication process and issuing a new authentication status identifier if it is determined to be invalid. The authentication state management method according to claim 4.   In the process of assigning the authentication status identifier, an upper limit value is set for the number of authentication status identifiers issued to one external system, and a plurality of threads are started in response to a data operation request from the same external system. 6. The authentication state management method according to claim 4 or 5, wherein the authentication state identifier is assigned to these threads within a range not exceeding the set upper limit value.

Images