<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>2.7 Setting up IdP linkage on JP1 Cloud Service/Operations Integration User&#39;s Guide</title>
    <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/index.html</link>
    <description>Recent content in 2.7 Setting up IdP linkage on JP1 Cloud Service/Operations Integration User&#39;s Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>2.7.1 Setting up OIDC connection</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_oidc/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_oidc/index.html</guid>
      <description>This section describes the connection setup procedure when using OIDC as the protocol for authentication for IdP linkage.
When using OIDC, the following conditions must be met.
The IdPs support authorization code flows User ID (username), first name, last name, and e-mail address can be obtained with an ID token or UserInfo endpoint The following is the procedure for setting up OIDC connection.
(Figure) Setting up OIDC connection
&amp;#9312; Providing IdP linkage information set in Ops I to the IdP</description>
    </item>
    <item>
      <title>2.7.2 Setting up SAML connection</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_saml/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_saml/index.html</guid>
      <description>This section describes the connection setup procedure when using SAML as the protocol for authentication for IdP linkage.
When using SAML, the SAML assertion must be able to obtain the user ID (username), first name, last name, and e-mail address.
The following is the procedure for setting up an IdP using SAML.
(Figure) Setting up SAML connection
&amp;#9312; Providing information set in the IdP to Ops I
The IdP administrator provides the Ops I security administrator with information such as the IdP&#39;s identity provider entity ID and single sign-on service URL (AuthnRequest URL).</description>
    </item>
    <item>
      <title>2.7.3 Mapping attributes/groups/roles</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_mapping/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_mapping/index.html</guid>
      <description>To link IdP users with Ops I users, map attribute information, groups, and roles of Ops I users based on information of IdP users.
Multiple mapping configurations can be registered for each OIDC or SAML connection setting.
The mappings are configured by Ops I security administrators.
(Figure) Mapping outline
The following attributes are required in Ops I user profiles and must be assigned values by manual or automatic mapping. If any of the values are missing, a login error will occur.</description>
    </item>
    <item>
      <title>2.7.4 Log in/log out</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_login_logout/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/setting/external_idp/idp_login_logout/index.html</guid>
      <description>This section describes logging in to and logging out of Ops I through IdPs.
The following are the prerequisites for logging in to Ops I through IdPs.
The information of IdP users can be obtained
To map a user between IdPs and Ops I, user attribute information needs to be mapped between them. The following is the attribute information that needs to be mapped. If the value is missing, a login error will occur.</description>
    </item>
  </channel>
</rss>