Skip to main content

 

Eptura Knowledge Center

Supported and unsupported scenarios for migration

  1. Last updated
  2. Save as PDF
This guide describes the scenarios supported for migration to SCIM and the recommended actions, and the scenarios which are unsupported.

Supported scenarios

The following existing configurations are supported for migration.

Scenario 1 – Eptura Engage customers with Forms users created by Eptura Engage.

  1. Choose Forms as the user type.
  2. Push existing users as new users via the SCIM “CreateUser“ endpoint. When done, only SCIM can sync/map the user internally.

Existing Forms users are not available automatically via SCIM until they are pushed as new users as per the SCIM standard.

When complete the users are available via the SCIM API to perform actions such as get, update, delete, etc.

Scenario 2 – Eptura Engage customers using SSO and the user source is Azure AD

  1. Choose SSO as the user type.

Existing AD users are not available automatically via SCIM until the customer performs the steps below.

  1. Configure the SCIM application in Azure AD by following the “Admin Guide”, and start user provisioning.
  2. When the initial sync is complete, all Azure AD users are synced/mapped internally with SCIM.

The Eptura Engage user record now synchronizes automatically with the Azure AD user record.

Scenario 3 – Eptura Engage customers using SSO and the user source is Azure AD – users have registered for Eptura Engage via the Eptura Engage Self Registration page.

For SSO users, each user account must have the associated Azure AD GUID stored in the Condeco user record. However, users who registered for Condeco via the Self Registration page, do not have the Azure AD GUID stored.

  1. Update your Eptura Engage users with the related Azure AD GUID.
  2. When the GUIDs are stored in Eptura Engage, refer to Scenario 2.

Scenario 4 – Eptura Engage customers using SSO and the user source is a hybrid Azure AD environment.

Eptura has tested and verified the following scenario for a hybrid on-premises/Azure AD environment.

  1. First, synchronize user data from the on-premises AD to Azure AD using Azure AD Connect.

Passwords and password settings:
a) Ensure user passwords are synchronized from on-premises AD to Azure AD, otherwise the user login from Eptura Engage will fail.
b) The User must change password at next logon setting in the user’s AD profile must be unchecked when synchronizing from on-premises AD to Azure AD.

  1. Then synchronize user data from Azure AD to Eptura Engage via the SCIM application.

Unsupported scenarios

The following scenarios are not supported for migration.

Not supported – Scenario 5 – Eptura Engage customers using SSO and the user source is HR feed (on-premises Active Directory)

Hosted AD does not support SCIM.