Configuring SSO Deployment¶
Before you can start, you need details of the tenant's Azure app registration. This is external information and will be provided by the customer or by the consultant acting on their behalf.
Note: PKCE enabled for SSO.
You configure an SSO deployment for a tenant:
- Go to Admin Configuration > SSO.
Enter the details — you can update these details later if needed:
SSO Deployment Name A descriptive name of the SSO deployment. This will be displayed to users configuring providers. URL, Client Id, Client Secret The link to the Azure app registration, and the client Id and secret provided by the customer.
(Follow the URL format:
https:///auth/realms/ )
Note: Currently there is no notification that the client secret has expired. Expiry of the client secret will prevent the providers from working.Scope openid profile 3. Click Save. A task will be queued to update the tenant database and, once the task completes, the tenant will be able to configure providers using this SSO deployment in the designer.
Note: If required, you can disable the SSO deployment at any point, for example, if this sign-in method is no longer required.
Configuring SSO with a new IAM client¶
When configuring SSO with IFS Cloud, it is recommended that you create a new IAM Client. This is because redirect URLs are reset for clients with every IFS Cloud upgrade each month.
When you create a new IAM client and specify a custom redirect URI, it remains unchanged even after an IFS Cloud upgrade.
You can create a new custom IAM client
- In IFS Cloud, go to IAM Client.
- Select the option to create a new client.
a) Configure Client Settings
b) Enable the following options :
Enabled , Service Account, Direct Access Granted
c) Set Redirect URI : You need to enter the required redirect URI(s) for the client. 4. Save the configuration
Note: You can use SSO only with the Authenticated Portals.