Information processing system and log recording method in information processing system

Abstract

To generate a log which can be confirmed without checking up on users, while avoiding duplication of user names between systems.SOLUTION: When a cooperation source user name corresponding to identification information of a user included in a received request is included in a cooperation destination system user information, a cooperation destination system 102 that cooperates with a cooperation source system 101 converts the identification information of the user included in the request into a user ID corresponding to the cooperation source user name in the cooperation destination system user information. The cooperation destination system processes the request on the basis of the user ID and determines whether a cooperation source user name corresponding to the user ID is included in the cooperation destination system user information. In a case where the cooperation source user name corresponding to the user ID is included in the cooperation destination system user information, the cooperation destination system converts the user ID into a cooperation source user name corresponding to the user ID in the cooperation destination system user information, and outputs a log including the cooperation source user name converted from the user ID.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to an information processing system and a log recording method in an information processing system. [Background technology]

[0002] Audit logs are used as one of the pieces of information to prove or confirm that the operation of an information system complies with laws and regulations, security evaluation standards, and the like.

[0003] In addition to the direct management of systems such as servers and storage, services that manage these systems via cloud services have recently emerged. When servers or storage are operated from such cloud services, the operations are also recorded in the audit logs of the servers and storage.

[0004] As integration with such cloud services increases, the number of users also increases, and the user names used to operate from the cloud service and those used to directly operate servers and storage devices overlap, making it difficult to determine which user performed an operation even when looking at the audit log.

[0005] One method for managing names such as user names that may collide and avoid duplication is to use a universally unique IDentifier (UUID). For example, in Patent Document 1, a UUID is used to identify a server, making it possible to manage the server while avoiding duplication. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2009-151560 A Summary of the Invention [Problem to be solved by the invention]

[0007] When systems work together, using unique identification information such as a UUID as the user name can avoid duplication of user names and enable work together.

[0008] However, if unique identification information such as a UUID is output to an audit log that requires human confirmation, a human must match the unique identification information such as a UUID with the user. This matching process is extremely cumbersome.

[0009] The present invention has been made in consideration of the above circumstances, and has as its object to generate a log that can be checked without matching users while avoiding duplication of user names between systems. [Means for solving the problem]

[0010] As one aspect for solving the above-mentioned problem, there is provided an information processing system which cooperates with a coordination source system and processes a request received via the coordination source system and a request received directly without going through the coordination source system, the information processing system including a processor and a storage unit, the storage unit stores user information which associates and manages user identification information which uniquely identifies a user in the information processing system with coordination source user identification information which identifies the coordination source user in the coordination source system when the user is the coordination source user, the processor receives the request, and determines whether the coordination source user identification information corresponding to the user identification information included in the received request exists in the user information, When the source user identification information is present in the user information, the identification information is converted to the user identification information in the user information that corresponds to the source user identification information, the request is processed based on the user identification information, and when a log related to the processing of the request is output, it is determined whether the source user identification information corresponding to the user identification information is present in the user information, and when the source user identification information corresponding to the user identification information is present in the user information, the user identification information is converted to the source user identification information in the user information that corresponds to the user identification information, and the log including the source user identification information into which the user identification information has been converted is output. Effect of the Invention

[0011] According to the present invention, it is possible to avoid duplication of user names between systems, and to record operations performed from the source system in the audit log of the destination system under the user name of the source system. This makes it possible to check the audit log without matching UUIDs with users. [Brief description of the drawings]

[0012] [Figure 1] 1 is a block diagram showing a schematic configuration example of a linkage system according to a first embodiment. [Diagram 2]2 is a block diagram showing an example of a hardware configuration of a cooperation destination system according to the first embodiment. FIG. [Diagram 3] 2 is a block diagram showing an example of a functional configuration of a cooperation destination system according to the first embodiment. FIG. [Figure 4] 4 is a diagram showing a configuration of destination system user information held by the destination system according to the first embodiment. FIG. [Diagram 5] 2 is a block diagram showing an example of a functional configuration of a cooperation source system according to the first embodiment. FIG. [Figure 6] 4 is a diagram showing a configuration of cooperation source system user information held by the cooperation source system according to the first embodiment. FIG. [Figure 7] 5 is a flowchart showing a request process of the linkage system according to the first embodiment. [Figure 8] 13 shows, in the form of a table, an example of an audit log output by an audit log writing unit 305 of a destination system according to the first embodiment. [Figure 9] 10 is a flowchart showing a process performed by an audit log writing unit in a destination system according to the first embodiment. [Figure 10] 13 is a diagram showing a configuration of destination system user information held by the destination system according to the second embodiment. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] The following embodiments will be described with reference to the drawings. Note that the following embodiments do not limit the scope of the invention, and all of the elements and combinations thereof described in the embodiments are not necessarily essential to the solution of the invention.

[0014] In the following description, a program that realizes each processing function unit is executed by a processor (e.g., a CPU (Central Processing Unit)) to perform a predetermined process while appropriately using a storage resource (e.g., a memory) and / or a communication interface device (e.g., a port). Therefore, the process executed by each processing function unit may be a process performed by a processor or a computer having the processor.

[0015] In the following explanation, various information is expressed in table format, but the information is not limited to table format and may be in CSV (Comma Separated Values) or other formats. Since various information does not depend on the data format, for example, "XXX table" can be called "XXX information".

[0016] In addition, among the items in the various information, the names of items that include information to distinguish the corresponding record from other records, such as "identification information," "ID," and "name," may be interchangeable. For example, "user ID" may be interchangeable with "user identification information."

[0017] [Embodiment 1] (Configuration of the linkage system S according to the first embodiment) FIG. 1 is a block diagram showing a schematic configuration example of a linkage system S according to the first embodiment.

[0018] In FIG. 1, a collaboration system S includes a collaboration source system 101, a collaboration destination system 102, a client 103, and the Internet 104 connecting these systems.

[0019] A cooperation source system 101 is connected to a cooperation destination system 102 and a client 103. A user operates the client 103 to connect to the cooperation source system 101 via the Internet 104. Operations performed on the cooperation source system 101 are transferred to the cooperation destination system 102 via the Internet 104 as necessary and processed.

[0020] Note that the client 103 is not limited to a terminal that connects to the cooperation source system 101 by a user operation and transfers a request to the cooperation destination system 102. In other words, the client 103 also includes a terminal that connects to the cooperation destination system 102 by a user operation and directly transmits a request to the cooperation destination system 102.

[0021] Furthermore, the cooperation source system 101 holds cooperation source system user information 111 for authenticating and authorizing users who access the services it provides.

[0022] The destination system 102 can be operated from the source system 101 via the Internet 104, and can also be operated by directly accessing the destination system 102.

[0023] The destination system 102 also holds destination system user information 121 for authenticating and authorizing a user who performs an operation, and further has an audit log 122 for recording operations performed by the user.

[0024] The client 103 is a system that serves as an interface for a user to connect to and use the cooperation source system 101 via the Internet 104. Specifically, the client 103 is a computer or a smartphone and a web browser or application that runs thereon.

[0025] The Internet 104 is a network that mutually connects the cooperation source system 101, the cooperation destination system 102, and the client 103. The Internet 104 may be replaced with any network such as a LAN (Local Area Network).

[0026] (Hardware configuration of the cooperation destination system 102 according to the first embodiment) FIG. 2 is a block diagram showing an example of the hardware configuration of the cooperation destination system 102 according to the first embodiment.

[0027] 2, the cooperation destination system 102 includes a CPU (Central Processing Unit) 202, a memory 203, a drive 204, and a NIC (Network Interface Card) 205. The CPU 202, the memory 203, the drive 204, and the NIC 205 are connected to each other via a bus 201.

[0028] The memory 203 is a main storage device that can be read and written by the CPU 202. The memory 203 is, for example, a semiconductor memory such as an SRAM or a DRAM. The memory 203 can store programs that the CPU 202 is executing, and can provide a work area for the CPU 202 to execute the programs.

[0029] The drive 204 is a secondary storage device that can be read and written by the CPU 202. The drive 204 is, for example, a hard disk device or a solid state drive (SSD). The drive 204 can hold executable files of various programs, data used to execute programs, and user information. The drive 204 may be composed of multiple hard disk devices or SSDs using RAID (Redundant Arrays of Independent Disks) technology or the like.

[0030] The CPU 202 loads a program stored on the drive 204 into the memory 203 and executes it. The CPU 202 is connected to the NIC 205 via the bus 201, and can communicate with the cooperation source system 101 via the Internet 104.

[0031] The cooperation destination system 102 may be configured from a plurality of systems using clustering technology or the like.

[0032] (Functional configuration of the cooperation destination system 102 according to the first embodiment) 3 is a block diagram showing an example of a functional configuration of the link destination system 102 according to the first embodiment. The link destination system 102 is, for example, a storage system, but is not limited thereto, and may be any information processing system that receives a request from a user terminal via another system or directly from the user terminal, processes the request, and outputs a log related to the processing. The log is, for example, an audit log, but is not limited thereto, and may be any log that records the processing result of the request.

[0033] 3, the destination system 102 includes a collaboration request receiving unit 301 that receives an operation request from the source system 101 via the Internet 104, and a collaboration request processing unit 303 that processes the received operation request. The destination system 102 also includes a collaboration response sending unit 304 that returns a processing result of the operation request to the source system 101 via the Internet 104.

[0034] It also includes a linkage user creation unit 302 that creates a user (linkage user) who operates the linkage source system 101 in the linkage destination system 102, and linkage destination system user information 121 that stores user information of linkage users and normal users. A normal user is a user who operates the linkage destination system 102 directly from the client 103. The linkage destination system user information 121 is stored in a predetermined storage unit.

[0035] It also includes an audit log 122 that stores audit logs, and an audit log writer 305 that writes operations of the collaboration request processor 303 into the audit log 122 .

[0036] A gateway, a firewall, or the like may be present between the Internet 104 and the coordination request receiving unit 301 and the coordination response transmitting unit 304. The audit log 122 may be transferred to an external log data accumulation server (such as syslog).

[0037] (Configuration of Collaboration Destination System User Information 121 According to the First Embodiment) FIG. 4 is a diagram showing the configuration of the destination system user information 121 held by the destination system 102 according to the first embodiment.

[0038] The link destination system user information 121 is used to manage users (linkage users) used when linking with the link source system 101 and normal users of the link destination system 102.

[0039] The destination system user information 121 is managed as information including a user ID 401 for identifying a user, a collaboration flag 402 indicating that the user is for collaborating with the source system 101, and a source user name 403 indicating the user name in the source system. The destination system user information 121 may include information other than the above. The source user name 403 is an example of source user identification information.

[0040] Record 411 is an example of a user for collaboration. In this record 411, user ID 401 is a UUID, collaboration flag 402 is Yes (a user for collaboration), and collaboration source user name 403 is the user name used in collaboration source system 101. On the other hand, record 412 is a normal user used in collaboration destination system 102, in which case user ID 401 is a character string such as a name, collaboration flag 402 is No (not a user for collaboration), and collaboration source user name 403 is NULL.

[0041] (Functional configuration of the cooperation source system 101 according to the first embodiment) FIG. 5 is a block diagram showing an example of a functional configuration of the cooperation source system 101 according to the first embodiment.

[0042] 5, the cooperation source system 101 includes a request receiving unit 501, a response transmitting unit 502, a cooperation request transmitting unit 504, a cooperation response receiving unit 505, and a request processing unit 503.

[0043] The request receiving unit 501 receives an operation request from the client 103 via the Internet 104. The response sending unit 502 returns a processing result of the operation request to the client 103 via the Internet 104. The linkage request sending unit 504 sends an operation request to the link destination system 102 via the Internet 104. The linkage response receiving unit 505 receives a result of the operation request from the link destination system 102 via the Internet 104. The request processing unit 503 sends the operation request received by the request receiving unit 501 from the linkage request sending unit 504 to the link destination system 102 via the Internet 104. The request processing unit 503 then receives the transmission result of the operation request at the linkage response receiving unit 505 via the Internet 104, and returns it to the client 103 from the response sending unit 502 via the Internet 104.

[0044] Note that a gateway, a firewall, or the like may be present between the request receiving unit 501 , the response transmitting unit 502 , the linkage request transmitting unit 504 , and the linkage response receiving unit 505 and the Internet 104 .

[0045] (Configuration of cooperation source system user information 111 according to embodiment 1) FIG. 6 is a diagram showing the configuration of the cooperation source system user information 111 held by the cooperation source system 101 according to the first embodiment.

[0046] The cooperation source system user information 111 is used to manage users who use the cooperation source system 101. In the cooperation source system user information 111, each user is managed as information including a user ID 601 that identifies the user. The cooperation source system user information 111 may also have information other than the above.

[0047] (Request Processing of Linkage System S According to the First Embodiment) 7 is a flowchart showing request processing in the coordination system S according to embodiment 1. The request processing is started when the coordination source system 101 receives a request from the client 103.

[0048] First, the cooperation source system 101 receives a request from the client 103 via the Internet 104 (S711). Next, the cooperation source system 101 refers to the cooperation source system user information 111 based on the received request, and authenticates the user who sent the request using an ID, password, etc. (S712). The authentication method used at this time may be public key authentication, etc. Next, after completing user authentication, the cooperation source system 101 adds the user name that was authenticated and performed the operation in the cooperation source system 101 to the request, and sends the cooperation request to the cooperation destination system 102 (S713). Note that the information added in S713 may include information other than the user name, for example, the cooperation source system ID.

[0049] Next, the destination system 102 receives the federation request sent from the source system 101 via the Internet 104 (S721). Next, the destination system 102 checks whether a federation user for the user is registered in the destination system user information 121 from the user name of the source system 101 included in the federation request (S722). If the federation user is not registered (S722 No), the destination system 102 creates a federation user (S723) and registers it in the destination system user information 121 (S723). At this time, a UUID is used for the user ID 401 to avoid duplication with other users. Also, the federation flag 402 is set to Yes, and the user name in the source system 101 included in the federation request is stored in the source user name 403.

[0050] Note that the link flag 402 does not necessarily have to be set to Yes as long as it can be identified that the user is a user created to link with the link source system 101. Also, the link source user name 403 being "not NULL" may be substituted for the link flag 402 being set to Yes.

[0051] If the linked user has already been registered (Yes in S722), or after registration of the linked user has been completed in S723, the link destination system 102 processes the link request as an operation by the linked user on the link destination system 102 (S724). After completing the process of S724, the link destination system 102 transmits the processing result to the link source system 101 as a link response (S725). The link destination system 102 also outputs the result as an audit log (S726). The output of the audit log in S726 will be described later with reference to FIGS. 8 and 9.

[0052] Next, the coordination source system 101 receives a coordination response from the coordination destination system 102 (S714). After that, the coordination source system 101 transmits a response based on the received coordination response to the client 103 via the Internet 104 (S715). The above flow is repeated every time the client 103 transmits a request to the coordination source system 101 via the Internet 104.

[0053] 7, it is assumed that the request received by the destination system 102 is a request received via the source system 101. However, some of the requests received by the destination system 102 are directly sent from the client 103. Therefore, the request includes identification information of the requesting system. If the identification information of the requesting system included in the received request corresponds to the source system 101, the destination system 102 executes the processes of S722 to S723. On the other hand, if the identification information does not correspond to the identification information of the source system 101 (e.g., if the user is a user of the destination system 102), S722 to S723 are omitted, and the request is processed based on the user ID included in the received request in S724.

[0054] (Example of audit log 122 according to the first embodiment) FIG. 8 shows, in the form of a table, an example of the audit log 122 output by the audit log writing unit 305 of the cooperation destination system 102 according to the first embodiment.

[0055] The audit log 800 output by the audit log writing unit 305 does not have to be table data, and may be text data using a delimiter such as "," (comma) like the CSV format.

[0056] The audit log 800 includes a date and time 801, a user name 802, an operation source 803, an operation content 804, and an operation result 805. The order of these items may be changed. Also, some of these items may be missing, or additional items may be added.

[0057] 8, in record 811, the user name 802 "abcdefgh" of the destination system 102 is converted to the user name 802 "taro.Suzuki" of the source system 101 and output. In record 812, since the user name "jiro.ito" of the destination system 102 is a user specific to the destination system 102, the user name 802 is not converted and the user name "jiro.ito" of the destination system 102 is directly output.

[0058] (Processing performed by the audit log writing unit 305 according to the first embodiment) 9 is a flowchart showing the process performed by the audit log writing unit 305 of the cooperation destination system 102 according to the embodiment 1. FIG 9 shows a detailed flow of S726 in FIG.

[0059] First, the audit log writer 305 receives the contents to be written to the audit log 800 from the collaboration request processor 303 (S726a).

[0060] Next, when the audit log writing unit 305 receives the content to be written to the audit log 800, it searches the destination system user information 121 of the destination system 102 for the name of the user who performed the operation, and finds one with a matching user ID 401. The audit log writing unit 305 then checks the linkage flag 402 in the destination system user information 121 for the found user (S726b). If the linkage flag 402 is No (S726bNo), the audit log writing unit 305 writes out the content to be written to the audit log 800 received from the linkage request processing unit 303 as is (S726d).

[0061] On the other hand, if the collaboration flag 402 is Yes (S726b Yes), the audit log writing unit 305 converts the content to be written to the audit log 800 received from the collaboration request processing unit 303. That is, among the content to be written to the audit log 800, the audit log writing unit 305 converts the user name 802 to the collaboration source user name 403 and the operation source 803 to the collaboration source system 101 (S726c). The audit log writing unit 305 then writes out the audit log 800 with the converted content (S726d). The audit log writing unit 305 performs the process shown in the flow in FIG. 9 every time it receives content to be written to the audit log 800 from the collaboration request processing unit 303.

[0062] In the above operation flow, for an operation from the source system 101 to the destination system 102, the user name 802 is the user name of the source system 101, and the operation source 803 is the source system in the audit log 122 of the destination system 102. This can reduce the work of matching UUIDs and user names when checking the audit log 122 of the destination system 102.

[0063] (Effects of the First Embodiment) In the above-described first embodiment, when processing a request from the coordination source system 101, the user name of the coordination source system 101 included in the request is converted to a user ID (ID of the coordinated user) of the coordination destination system 102 and the request is processed. Then, when outputting a log during processing of the request, the ID of the coordinated user is converted back to a user name of the coordination source system 101, and the user name of the coordination source system 101 is output to the log.

[0064] Therefore, according to the first embodiment, after avoiding duplication of user names between systems by using a federated user, operations performed from the source system 101 can be recorded in the log of the destination system 102 under the user name of the source system 101. Therefore, during log auditing, it is possible to check without matching unique user identification information such as a UUID with the user name of the source system 101.

[0065] In the first embodiment, a log including the cooperation source system identification information as the identification information of the request source system of the request is output together with the cooperation source user identification information obtained by converting the user identification information. Therefore, the name of the cooperation source system 101 that sent the request can be identified on the log.

[0066] In addition, in the first embodiment, when a request is received, if the cooperation source user name corresponding to the user identification information included in the request does not exist in the cooperation destination system user information 121, the following process is performed. That is, this identification information is used as the cooperation source user name, and the cooperation source user name and new user identification information are associated and registered in the cooperation destination system user information 121. Furthermore, the identification information of the cooperation source system 101 included in the request may be associated and registered in the cooperation destination system user information 121. In particular, by setting the new user identification information to a UUID, it is possible to easily create a cooperation user that avoids duplication of user names between systems, thereby facilitating system cooperation.

[0067] [Embodiment 2] In the first embodiment, in the linking system S, one link source system 101 links with one link destination system 102. However, this is not limited to the above, and in the second embodiment, an example will be described in which a plurality of link source systems 101 links with one link destination system 102 in the linking system S.

[0068] (Configuration of linked system user information 121B according to the second embodiment) FIG. 10 is a diagram showing the configuration of destination system user information 121B held by the destination system 102 according to the second embodiment.

[0069] The destination system user information 121B differs from the destination system user information 121 of the first embodiment in that the ID (source system identification information) of the source system 101 is stored together with "Yes" in the collaboration flag 402. The ID of the source system 101 may be any information that can uniquely identify the source system 101 within the collaboration system S.

[0070] Record 411B indicates that the federation user name (user ID 401) in the destination system 102 of the user (source user name 403) "taro.suzuki" in the source system 101 identified by "SYSID1" is "abcdefgh1". Record 412B indicates that the federation user name in the destination system 102 of the user "Saburo.tanaka" in the source system 101 identified by "SYSID2" is "abcdefgh2". Record 412B indicates that the user with user ID 401 "jiro.ito" is a unique user in the destination system 102.

[0071] In the second embodiment, in S713 of the request process (FIG. 7) of the coordination system S, the coordination request is sent to the coordination destination system 102 with the ID of the coordination source system 101 added to the request together with the user name of the coordination source system 101.

[0072] In the second embodiment, in S722, the user ID 401 and the collaboration flag 402 in the collaboration destination system user information 121 are referenced based on the user name of the collaboration source system 101 and the ID of the collaboration source system 101 included in the collaboration request. Then, it is confirmed whether a collaboration user for a user corresponding to the combination of the user name of the collaboration source system 101 and the ID of the collaboration source system 101 has been registered.

[0073] In the second embodiment, in S725, the collaboration response is transmitted to the system identified by the ID of the collaboration source system 101 indicated in the collaboration request received in S721.

[0074] In the second embodiment, in S726c of the process (FIG. 9) performed by the audit log writing unit 305 of the destination system 102, when converting the user name to be written in the audit log into the user name of the source system, the operation source is converted into the ID of the source system 101. This ID of the source system 101 may be shared in advance between the source system 101 and the destination system 102 at the time of collaboration, or may be transmitted and received together with the collaboration request in S713 to S721 (FIG. 7).

[0075] In the second embodiment, when a request is received, if the coordination source user name corresponding to the user identification information included in the request does not exist in the coordination destination system user information 121, the following process is performed. That is, this identification information is used as the coordination source user name, and the coordination source user name, new user identification information, and identification information of the coordination source system 101 included in the request are associated with each other and registered in the coordination destination system user information 121. In particular, by setting the new user identification information to a UUID, even when multiple coordination source systems 101 exist, a coordination user that avoids duplication of user names between systems can be easily created, thereby facilitating system coordination.

[0076] (Effects of the second embodiment) In the above-mentioned second embodiment, when there are multiple coordination source systems 101, a log including coordination source system identification information of the corresponding coordination source system 101 among the multiple coordination source systems 101 as identification information of the request source system of the request is output together with coordination source user identification information. Therefore, even when there are multiple coordination source systems 101, it is possible to determine which coordination source system 101 sent the request from the log.

[0077] Although the embodiments of the present disclosure have been described above in detail, the present disclosure is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the present disclosure. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present disclosure is not necessarily limited to those having all of the configurations described. In addition, it is possible to add, delete, or replace part of the configuration of the above-described embodiments with other configurations.

[0078] Furthermore, the above-mentioned configurations, functional units, processing units, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. The above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC card, an SD card, a DVD, or other recording medium.

[0079] In addition, in each of the above figures, the control lines and information lines are shown as those considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the actual implementation. For example, it may be considered that almost all the components are actually connected to each other.

[0080] The above-mentioned arrangement of the functions and data of the coordination source system 101 and the coordination destination system 102 is merely an example. The arrangement of the functions and data can be changed to an optimal arrangement in terms of the performance of the hardware and software, processing efficiency, communication efficiency, and the like. [Explanation of symbols]

[0081] S: linked system, 101: source system, 102: destination system, 121, 121B: destination system user information, 122, 800: audit log, 202: CPU, 401: user ID, 403: source user name, 401: user ID, 403: source user name.

Claims

1. An information processing system that cooperates with a cooperation source system and processes a request received via the cooperation source system and a request received directly without going through the cooperation source system, A processor and a storage unit are included. The storage unit is Store user information that associates and manages user identification information that uniquely identifies a user in the information processing system and, if the user is a collaboration source user in the collaboration source system, collaboration source user identification information that identifies the collaboration source user in the collaboration source system; The processor, Accepting the request, determining whether the cooperation source user identification information corresponding to the user identification information included in the received request is present in the user information; When the collaboration source user identification information exists in the user information, the identification information is converted into the user identification information corresponding to the collaboration source user identification information in the user information; Processing the request based on the user identification information; When outputting a log related to the processing of the request, it is determined whether the cooperation source user identification information corresponding to the user identification information is present in the user information; When the collaboration source user identification information corresponding to the user identification information is present in the user information, the user identification information is converted into the collaboration source user identification information corresponding to the user identification information in the user information; Outputting the log including the cooperation source user identification information into which the user identification information has been converted An information processing system comprising:

2. 2. The information processing system according to claim 1, The user information is The user identification information, the collaboration source user identification information that identifies the collaboration source user in the collaboration source system when the user identified by the user identification information is the collaboration source user of the collaboration source system, and the collaboration source system identification information that identifies the collaboration source system are associated and managed; The processor, When outputting the log, it is determined whether the cooperation source user identification information corresponding to the user identification information is present in the user information; When the coordination source user identification information corresponding to the user identification information is present in the user information, the user identification information is converted into the coordination source user identification information corresponding to the user identification information in the user information, and identification information of a request source system of the request is converted into the coordination source system identification information associated with the coordination source user identification information in the user information; The log including the coordination source system identification information as identification information of the request source system together with the coordination source user identification information into which the user identification information is converted is output. An information processing system comprising:

3. 2. The information processing system according to claim 1, The processor, When the request is received from the coordination source system, if the coordination source user identification information corresponding to the identification information does not exist in the user information, the identification information is registered in the user information as the coordination source user identification information and the coordination source user identification information is associated with new user identification information. An information processing system comprising:

4. 4. The information processing system according to claim 3, The new user identification information is a Universally Unique IDentifier (UUID). An information processing system comprising:

5. 2. The information processing system according to claim 1, The processor, When the request is received without going through the cooperation source system, the request is processed based on the user identification information included in the request; Outputting the log including the user identification information An information processing system comprising:

6. A log recording method in an information processing system that cooperates with a cooperation source system and processes a request received via the cooperation source system and a request received directly without going through the cooperation source system, comprising: A processor and a storage unit are included. The storage unit is Store user information that associates and manages user identification information that uniquely identifies a user in the information processing system and, if the user is a collaboration source user in the collaboration source system, collaboration source user identification information that identifies the collaboration source user in the collaboration source system; The processor, Accepting the request, determining whether the cooperation source user identification information corresponding to the user identification information included in the received request is present in the user information; When the collaboration source user identification information exists in the user information, the identification information is converted into the user identification information corresponding to the collaboration source user identification information in the user information; Processing the request based on the user identification information; When outputting a log related to the processing of the request, it is determined whether the cooperation source user identification information corresponding to the user identification information is present in the user information; When the collaboration source user identification information corresponding to the user identification information is present in the user information, the user identification information is converted into the collaboration source user identification information corresponding to the user identification information in the user information; Outputting the log including the cooperation source user identification information into which the user identification information has been converted A log recording method comprising each process.

Images