07-01-2021 02:52 PM
Community,
Our EP3 environment currently leverages Advanced AD and ADFS and is migrating to OKTA.
We setup the HIdP default Tenant with a Provider configured for ADFS w/SAML in our DEV environment, and we were successfully able to login using that flow.
However, when I added a second Provider configured for OKTA w/SAML to the default Tenant, we received an error stating:
KeyNotFoundException: No Idp with entity id {UniqueID} found.
Removing the original ADFS Provider resolved the error, and were able to successfully login using the flow through OKTA.
So, it appears one can only have a single Provider for each type in each Tenant.
This training video for previous versions of the IdP indicates it is simple to setup a multi-tenant solution by just modifying the web.config:
OnBase Identity Provider Service (IdP) - Training.Hyland.com
However, looking for best practices and thoughts on how to go about creating the multi-tenant configuration in EP3?
07-02-2021 05:39 AM
Hi Cody,
There is a known limitation in Foundation that prevents multiple SAML providers from being configured for use with the Hyland IdP. This has been addressed for EP5 (IdP 2.9) and documented under CI-714.
In order to use multiple SAML providers in EP3, a second instance of the IdP server would have to be stood up and configured.
Hope this helps.
Jimmy
07-02-2021 05:39 AM
Hi Cody,
There is a known limitation in Foundation that prevents multiple SAML providers from being configured for use with the Hyland IdP. This has been addressed for EP5 (IdP 2.9) and documented under CI-714.
In order to use multiple SAML providers in EP3, a second instance of the IdP server would have to be stood up and configured.
Hope this helps.
Jimmy
07-02-2021 08:17 AM
Thanks Jimmy!
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.