OUID System 1 Set

2026-11-03

Classification of the products to be procured : 1 Nature and quantity of the products to be rent : OUID System Set Type of the procurement : products to be rent Basi requirements of the procurement : A.This system consists of an Integrated ID Authentication System and an Integrated ID Management System. B.The Integrated ID authentication infrastructure shall have the following functions. B-1.Single Sign-On (SSO) Functions a.A single sign-on function compliant with OASIS-SAML 2. and OIDC for services (web applications) that support authentication/authorization federation, including SPs participating in academi authentication federations. b.A portal site that lists links to systems that support single sign-on, and a user guideline web page that includes FAQs and other information. c.A single logout function that, when a user logs out from a federated SP/RP, logs the user out from all federated SPs/RPs. B-2.Authentication Functions a.Authentication functions including : password plus multi-factor authentication using a secondary factor with an ID or email address as the username ; passkey authentication ; certificate authentication ; and social account authentication. b.A function that allows users to change their passwords and secondary authentication methods by themselves. c.If authentication is not possible due to a forgotten password, etc., functions including : online password reset/reconfiguration by the user using a recovery email address and a My Number Card ; a temporary secondary-authentication bypass function when secondary authentication cannot be performed ; and a user self-service password reset function. d.A function to maintain authentication sessions between users and between SPs/RPs for a specified period of time. B-3.Authentication Information Management Functions a.A function to retain, for each ID, the attributes received via federation from the Integrated ID management infrastructure. b.A function to send to an SP/RP the attributes held by the ID linked to the username, using the username specified by the user at the time of authentication as the key. c.A function to control which SPs/RPs can be used according to the attribute information held by the ID used for authentication. B-4.Administrator Functions a.A function that allows administrators to add, modify, and delete SPs/RPs to be federated for authentication. b.A function to acquire user's authentication logs and allow administrators to view them. c.A function that allows administrators to reset user's authentication information. C.The Integrated ID management infrastructure shall have the following functions. C-1.ID Management Functions a.A function to assign each user a unique ID within the University's systems. b.A function to manage role-specifi information separately from user information when a user holds multiple positions (Role ID function). c.A function to manage attribute information linked to IDs and Role IDs, and in response to inquiries keyed by username, return the attributes held by one of the multiple Role IDs possessed by a user. C-2.Data Import Functions a.A function to automatically or manually import data (CSV) provided from source systems that serve as the origin of user information and register users. There are multiple source systems, and the key information differs depending on the system. b.A function to generate attribute information linked to IDs based on generation rules at the time of data import. c.A function to identify candidates that may refer to the same person when information for one user is registered in duplicate in the database at the time of data import (candidate record linkage function). d.If an administrator determines that entries in the record-linkage candidate list refer to the same person, a function to overwrite the user information while keeping role information separated. C-3.Master Data Management Functions a.For master data of attribute information to be granted to users (e.g., department master, position master), a function that allows administrators to register and update it via CSV import. C-4.Workflow Application Functions a.For users not included in the source systems, a function whereby designated staff apply for ID issuance and administrators approve it, thereby issuing, changing, or revoking IDs. b.A function that allows administrators and designated staff to search past applications. c.A function to grant application privileges to designated staff. C-5.Administrator Functions a.A function that allows administrators to search for user information and edit it individually. b.A function that allows administrators to search user information and output it in a specified report format and in CSV format. c.A function that allows administrators to reset user's passwords and secondary authentication. d.A function to set permission management according to administrator accounts (e.g., overall administration, user registration, password reset). e.A function to control and manage remote access to servers. C-6.Audit Trail Functions a.A function to store operation history on user information and provisioning records as audit logs. b.A function that allows administrators to search, view, and output audit logs by user. C-7.User Functions a.A function that allows users to edit their own attribute information. b.A function that allows users to edit and reset their own passwords. C-8.ID Provisioning Functions a.A function to acquire, process, and synchronize updated user information according to the federation conditions of each system. D.In the event of a system failure, implement measures (e.g., server and network redundancy) to prevent suspension of this system's services. E.For work accounts on servers and accounts for data federation, restrict unnecessary operational privileges from a security perspective (specifi restrictions shall be discussed and implemented with the University). F.Periodically obtain backu data for each server and ensure that the obtained backu data can be evacuated/stored off-site for emergencies such as disasters. G.Provide functions for monitoring and failure detection such as service availability checks for critical services using SNMP, etc. In addition, during maintenance, introduce mechanisms with sufficient security considerations, such as restricting source IP addresses and devices and/or using security tokens. H.Be able to provide a sufficient maintenance structure to prevent system failures, prompt response when failures occur, and a support structure for system operations. I.Respond to questions and inquiries from the University to the system maintenance staff. J.If it becomes necessary to change system settings, etc. triggered by inquiries from the University or by issues raised by system maintenance staff, perform the required work. In addition, if it is discovered that this system is affected by vulnerability, carry out vulnerability remediation. K.For systems currently federated for authentication and data integration with the existing university-wide IT authentication infrastructure, perform migration work so that equivalent federation is achieved in the next system. If, during migration, changes arise in the configuration of federated systems or in user operating procedures, clarify them at the proposal stage. Time limit for the submission of the requested material : 1 : 1 2 June, 202 Contact point for the notice : YOSHIHIRO Shuhei, Accounting and Contracts Division, Department of Accounting, The University of Osaka, 1- Yamadaoka Suita shi Osaka 565-087 Japan, TEL 06-6879-4010

Japan

2026-05-21