Audit Log User Identification via UUID Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In information processing systems that cooperate with cloud services, the overlap of user names between systems makes it impossible to determine which user performed an operation, even when viewing the audit log, due to the use of universally unique identifiers (UUIDs) that require manual matching.
Innovation Solution
An information processing system that includes a processor and a storage unit to manage user identification information and cooperation source user identification information, allowing the system to convert identification information into user identification information corresponding to the cooperation source user identification information, thereby enabling the output of logs with user names from the cooperation source system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If unique identification information such as UUID is used to identify users in cooperative systems, then user name overlapping between systems is avoided, but manual matching of UUID with user becomes necessary and complicated
Solution Approach 1:
The patent introduces a mapping table that stores the correspondence between UUID and user name as an intermediary data structure. This mapping table acts as a mediator that connects the unique identifier (UUID) with the human-readable user name, allowing the system to maintain both the uniqueness of UUID for reliable identification and the readability of user names for easy audit log confirmation without manual matching.
2Reliability
If UUID is used for user identification in audit logs, then user name collision is prevented, but the audit log becomes difficult to confirm without matching work
Solution Approach 1:
The patent performs preliminary action by pre-establishing the mapping between UUID and user_name in a mapping table before the audit log confirmation process. This mapping relationship is created and stored in advance, so when audit logs need to be confirmed, the system can directly retrieve the user_name from the mapping table using the UUID, eliminating the need for time-consuming manual matching work at the time of audit log review.
3Adaptability or versatility
If cloud service cooperation increases, then system functionality is enhanced, but user name overlap between systems occurs making operation attribution impossible
Solution Approach 1:
The patent segments the user identification system into two distinct parts: a unique identifier (UUID) that ensures global uniqueness across cooperative systems, and a human-readable user_name that provides meaningful identification. The mapping table segments the storage by maintaining separate UUID and user_name fields, allowing each system to maintain its own user naming conventions while ensuring unique identification through UUID, thus preventing user name overlap issues in cooperative environments.
Data Source
AI summary
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 converts the identification information of the user included in the request into a user ID corresponding to the cooperation source user name in a cooperation destination system user information. The cooperation destination system processes the request based on the user ID and determines whether or not 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.