https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/system/identity_provider/index.html Recent content in 3.6.2 Identity provider on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/system/identity_provider/idp_common/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/system/identity_provider/idp_common/index.html This section explains the settings for [User Data Reuse Policy] and [Default Identity Provider]. These settings are executed from [Identity Providers] - [Common Settings]. For details on [Identity Providers], see “Identity provider”. (1) User data reuse policy Even if a customer user or a user who has accessed OTOBO is deleted from Ops I, the relationship between that user and the resources created by that user will not be deleted and will remain on OTOBO as a user who existed in the past. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/system/identity_provider/idp_template/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/system/identity_provider/idp_template/index.html The [Identity Provider Mapping] window is used to configure mapping rules between IdP user information and Ops I user information. Using template strings to assign values allows you to specify mapping targets even if the group, role, and attributes in Ops I do not perfectly match the values of conditions, Claim (for OIDC), or attributes (for SAML). As a result, you can set mapping targets that meet various conditions in one operation without having to register multiple mappings.