Scenario 1: Himsa IdP
This is the most basic setup where the member app is configured to only trust the Himsa IdP.
Scenario 2: 3rd Party IdP is federated to Himsa IdP
In this case one or more 3rd party IdPs are set up as federated providers in the Himsa SSO account via the Account Management Portal.
An administrator will need to add each existing user in the 3rd party IdPs as users in the Himsa SSO account via the Account Management Portal.
Users will then be able to log into the member app using their existing credentials and MFA methods offered by the 3rd party IdPs.
The member app does not need any knowledge of or special configuration to support the 3rd party IdPs.
Scenario 3: Himsa IdP is federated to a 3rd party IdP
In this case the 3rd party IdP is configured to trust Himsa IdP.
Users will then be able to log into the member app using their existing HIMSA SSO credentials and MFA methods.
The member app does not need any knowledge of the Himsa IdP or any configuration changes if it is already set up to trust the 3rd party IdP.
Note that the access token for accessing the Users API (https://api.qa.eu.noah-es.com/swagger/index.html?urls.primaryName=Noah%20Cloud%20App%20Users%20API%20v1, for obtaining a list of users and a list of Associated Locations) will have to be passed by the 3rd party IdP to the member app in a secure manner.