● Use case 1: A case where specific attributes are read and authentication is delegated to each company's IdP

In the case of the above configuration, the login flow for each company's users is as follows.

[Login flow for each company]

Sort by a specific attribute (assuming that an attribute called Company was created on Okta this time)

Example) Company A: Company attribute = Company A, Company B: Company attribute = Company B, Company C: Company attribute = Company C​

・A社（各社同様のフロー）

1. Access to company-wide common SaaS
2. You will be redirected to Okta and enter your ID
3. Redirect to Company A's Idp because Company attribute is A
4. Enter credential information on Company A's IdP
5. When authentication is completed, login to Okta and company-wide common SaaS is completed

● Use case 2: A case where the domain of the user ID is read and distributed to the IdP

In the case of the above configuration, the login flow for each company's users is as follows.

[Login flow for each company]

・A社 “GroupA.com”のドメインのユーザー（B社も同様）

1. Access to company-wide common SaaS
2. You will be redirected to Okta and enter your user ID
3. Redirect to Company A's IdP because the domain is GroupA.com
4. Enter credential information in Company A Idp
5. When authentication is completed, login to Okta and company-wide common SaaS is completed

・Users in the “@mycorp.com” domain

1. Access to company-wide common SaaS
2. Redirect to Okta
3. Enter your credentials into Okta
4. Login to SaaS completed