This page helps you in exposing the metadata of multiple Identity Providers to Adeptia Connect. The steps may vary for different IdPs (e.g. SSO Circle, Keycloak, Okta, etc.). For a clustered set up, you can repeat the steps given in every node of the environment. Exposing IdP metadata to Adeptia Connect allows the Service Providers to read the details of IdP Server.
...
If you have configured multiple IdPs, the users are by default authenticated through the default IdP. In case you want the user to be authenticated through a non-default IdP, you need to specify the registration Id of that IdP in the application URL as shown below.
| Info |
|---|
Registration Id is the name provided by the user to the IdP. In case of multiple IdPs, you have corresponding registration Ids defined in their respective environment variables in the portal values.yaml file. You can use the environment variable SAML_SSO_IDPS_CONFIGURATION_0_REGISTRATION_ID to define the registration Id of one of the IdPs, and then use the number in incremental fashion in the variable to define the registration Id of the next IdP, for example, SAML_SSO_IDPS_CONFIGURATION_1_REGISTRATION_ID, and so on. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
| https://<Domain name or IP>/?registrationId=<registration_Id> |
...