Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Current »

This page helps you in configuring multiple IDPs in Adeptia Connect. The steps may vary for various IDP providers (e.g. SSO Circle, Keycloak, Okta, etc.). This page guides the multiple IDP configuration through an example of SSO circle. For a clustered set up, you can repeat the steps given in every node of the environment.

Configure Multiple IDP in Adeptia Connect

To configure multiple IDP in Adeptia Connect, configure SAML SSO using IDP provider (for example, SSO circle). Click here to get more details.

  • Save the multiple idp.xml file and rename it (for example, idp_1.xml and idp_2.xml).

Placing Multiple IDP Metadata in Adeptia Connect

Placing IdP metadata information within Adeptia Connect allows Service Provider to read the details of IdP Server from a particular location.

After you have placed both idp.xml file, you need to set up the bean for both idp.xml files. By default there will be one bean in the file, you may copy-paste the bean and change the file name. Refer to the image below (securityContext.xml file). 




Setting Default SAML SSO IDP

  1. Go to …<ConnectPortalInstallFolder>\resources_config\saml location.
  2. Open securityContext.xml file. Add the following property as below:


    Where,

    • Value is the entityID value from idp.xml file.
    • To get the entityID, go to  …<ConnectPortalInstallFolder>\resources_config\saml location and open the IDP metadata file that you want to set as default.

  3. Restart Connect Portal.

Configure IDP Initiated SSO

Open the browser and type the below URL using IDP initiated SSO (for SSO Circle).

For Example, https://<IDP Server Host>/sso/idpssoinit?metaAlias=/publicidp&spEntityID=<value of SP entity Id>

Where,
spEntityID is the name that is specified in the metadata of your service provider.

In case of multiple IDP providers, the log out from SAML will happen only through the provider that has been set up as default. Even if you logout from a secondary provider, the log-out call will be directed to the default provider only.

  • No labels