Edit

Configure Identity Providers

You can set up the WorkFusion (WF) User Management component (Keycloak) to authenticate users based on identities from external providers.

The WF User Management supports integration with identity providers (IdP) using either of the protocols:

• SAML v2.0

• OpenID Connect v1.0

Integrate IdP based on SAML v2.0

To integrate with an IdP using the SAML protocol, follow the steps below:

1. Prepare the IDP client for integration with the WF User Management.
2. Create and configure a SAML IdP provider in WF User Management.
3. Authenticate in Control Tower with IdP credentials.
4. Map client roles to IdP users.

Configure IdP client

The configuration flow is as follows:

1. Import the WF User Management IdP settings (the IdP entity descriptor) using either of the two methods:

   • Paste the following URL in your browser line: https://{{keycloak_dns}}/auth/realms/{{workfusion_realm}}/protocol/saml/descriptor, where:

     • keycloak_dns is the DNS address of your User Management instance.

     • workfusion_realm is the name of the realm where you manage clients, roles, groups, users, and so on. Typically, it is WorkfusionRealm.

   • Go to Realm Settings > General > Endpoints > SAML 2.0 Identity Provider Metadata.

   

   Whichever method you use, this brings you to XML containing the IdP metadata, including the certificates.

   

2. Use the IdP settings from Step 1 to configure the IdP client for integration with the WF User Management.

3. Get the entity descriptor for your IdP client. Retrieve the IdP client data (Single Sign-On Service URL, Single Logout Service URL, certificates, and so on) essential for further configuration of the SAML IdP in the WF User Management.

Create SAML IdP

Before creating a SAML IdP, enable username editing:

1. Select Realm settings.

2. Go to the Login tab.

3. Make sure the Edit username toggle is on. If it is off, turn it on.

   

Then, create a SAML IdP as instructed below:

1. On the left menu, select Identity Providers.

2. On the right, click the drop-down box and select SAML v2.0.

   

   The action brings you to the screen where you need to configure the IdP settings.

Configure SAML IdP

To configure the SAML IdP you created in the previous step, follow the instructions below:

1. Fill in the fields and switch toggles on or off as shown in the screenshot below:

   

   Pay attention to the following recommendations:

   • Single Sign-On Service URL: the field is required, specifies the SAML endpoint to start the authentication process.

   • Single Logout Service URL: the field is optional, specifies the SAML logout endpoint.

   • Validating X509 Certificate: contains the public certificate to validate the signatures of SAML requests and responses from the configured IdP.

   • Principal Type: the setting must match the Identity Provider configuration. If you are unsure which parameter is sent, you can use SAML troubleshooting tools for investigation, for example, SAML Chrome Panel.

     note

     The values for the configuration fields above are specified in the IdP entity descriptor mentioned in Configure IdP client.

Set authentication flow

To set an authentication flow for the configured IdP, follow the steps below:

1. On the left menu, select Authentication.

   

2. In the drop-down box on top of the Flows tab, select Browser.

   

3. On the same tab, go to the Identity Provider Redirector line > Actions and select config.

   

4. Specify the SAML alias for the IdP you are matching to the authentication flow.

   

After you complete the authentication flow setup, user authentication in all clients (Control Tower, WorkSpace, Kibana) will be based on the credentials stored in the IdP. Your next step is to sign in to Control Tower with IdP credentials.

Authenticate in Control Tower

The authentication is essential for IdP users to appear as WF User Management entities. Follow the steps below:

1. Go to the Control Tower URL. From the URL, you are redirected to the following IdP login form.

   

2. To log in, enter the credentials for a valid IdP user. The following form appears on the screen:

   

   You can set the form to update automatically using an Identity Provider mapper. For instructions and a sample project, see the Create IdP mapper section.

3. Fill in the Username, Email, First name, and Last name fields (all fields are mandatory) and submit.

Two authentication outcomes are possible:

• If the username of the IdP user does not exist in the WF User Management, it is created. However, the Control Tower authentication attempt fails. To make the authentication a success, configure a Control Tower role for the created user as described in the Map roles to IdP users section.

• If the username of the IdP user already exists in the WF User Management, you see the following screen:

  

  If you click Review profile, this brings you back to the login page where you need to change the value in the Username field.

  If you click Add to existing account, this brings you to the below email verification page. The verification is essential for you to be able to add the IdP credentials to an existing WF User Management user.

  

  To verify, sign in to the email assigned to the respective WF User Management user and click the email verification link.

important

If an existing WF User Management user doesn't have a wf-control-tower client role, you get an authentication error message. To proceed, configure Control Tower roles. For the configuration details, refer to the Map roles to IdP users section.

Create IdP mapper

To create an IdP mapper, go to Identity Providers > SAML > Identity Provider Mapper and click Create. In the form that follows, select Mapper Type and fill in the fields.

Below is a sample of how you can create an IDP mapper:

1. Specify any name for the mapper.

2. Specify the sync mode override. Possible values include:

   • legacy to keep the behavior as it was before you selected the option.
   • import to only import the user once at their first login with the IdP credentials.
   • force to constantly update the user after every login under the identity provider.
   • inherit to use the sync mode defined in the identity provider for this mapper.

3. Select a mapper type based on the table below:

   Mapper type	Description
   Advanced Attribute to Role	If the set of attributes exists and can be matched, grant the user the specified realm- or client-level role.
   Username Template Importer	Format the username to import.
   Hardcoded User Session Attribute	When a user is imported from an IdP, hardcode the mapper value to a specific user session attribute.
   Attribute Importer	Import the declared SAML attribute, if it exists in the assertion, to a specified user property or attribute.
   Hardcoded Role	When a user is imported from an IdP, hardcode a role mapping for the user.
   Hardcoded Attribute	When a user is imported from an IdP, hardcode the mapper value to a specific user attribute.
   SAML Attribute to Role	If an attribute exists, grant the user the specified realm or application role.

   The rest of the parameters are specific to the mapper type you’ve chosen.

For more information, refer to the Keycloak documentation.

Map roles to IdP users

The user-to-role mapping is essential for users to access User Management clients—Control Tower, WorkSpace, and Kibana. You have two mapping alternatives:

• Automatic
• Manual

Automatic role mapping

If the underlying organizational structure allows, you can configure an IdP provider to send user attributes in SAML assertions and the WF User Management to map new users to specific roles based on those. For instance, the IdP can send the Department, Organization Unit, Job Title attributes, and the WF User Management will map users to specific client roles based on their values.

Below is an example of how a job title is mapped to the Control Tower Administrator role:

Alternatively, you store users in LDAP and can't use the attribute-to-role mapping or if you need more fine-grained management of groups or roles, configure User Federation with your LDAP and then set group and role mappings. For details, refer to Configure LDAP.

Manual role mapping for IdP users

Manual role mapping becomes possible after IdP users are already on the Users list in the WF User Management system. To map manually, follow the steps below:

1. On the left menu, select Users.

   

2. In the list of users on the right, select a user and click its ID.

3. On the user settings page, go to the Role Mappings tab.

   

4. In the Client Roles box, enter the WorkFusion client to which you want the user to have access—wf-control-tower, wf-kibana.

   

5. In the Available roles field, select required roles and click Add to assign them to the user. When assigned successfully, the roles appear in the Assigned Roles and Effective Roles fields.

In about 10 minutes (max), the new setup is synced with Control Tower or another client. This means users can log in to Control Tower or another client with their IdP credentials.

Sign and encrypt certificates

To generate certificates for signing and encrypting SAML assertions, complete the following steps:

1. In the WorkFusion realm, select Realm Settings > Keys > Providers.

   

2. To add a provider, click the Add keystore drop-down box and select rsa-generated.

   

3. Fill in the following form with the desired keystore priority, length, and so on.

   

   Changing the priority for a provider does not cause the keys to be re-generated. If you want to change the Key size, you can edit the provider, which entails generating new keys.

4. Save the provider. The generated certificates appear in the WF User Management SAML entity descriptor mentioned in Configure IdP client.

It is also possible to use existing keypair and certificates. For details, visit the Keycloak official documentation.

Disable automated user creation

By default, when a user authenticates using IdP credentials and there is no record for them in the internal WF User Management database, such a record is created. This saves you the trouble of creating users but may not be suitable for specific setups.

For instance, if you cannot completely trust an IdP, you may want to pre-create users in the WF User Management and disable the automated user creation to provide an additional authentication layer with a separate set of credentials. In this case, even if the credentials you specified on the login screen pass the IdP's authentication, you will not sign in successfully to the IA Cloud Enterprise.

important

Disabling the automated user creation is only possible after you complete the SSO configuration.

To disable the automated user creation, follow the steps below:

1. To create an authentication flow, click Authentication > Flows > New.

   

2. Set any alias name for further usage and click Save.

   

3. On the Identity Providers page, choose the configured IdP and click Edit.

   

4. To modify the existing authentication, in the First Login flow drop-down box, select the Empty flow created at Step 2.

   

5. At the bottom of the Settings page, click Save.

6. Go to the Users page and click the user you want to link to the IdP.

   

7. Go to the Identity Provider Links tab and click Create.

8. On the displayed page, fill in the fields as described below:

   

   • Identity Provider: choose an alias of the enabled and configured IdP.

   • Identity Provider User ID: specify SAM-Account-Name from the IdP.

   • Provider Username: type in the IdP username from the WF User Management in the lower case.

9. Click the Save button.

Integrate based on OpenID Connect v1.0

For the instructions to create and configure an OIDC IdP, refer to the Keycloak official documentation.