Identity V1 authentication and provisioning requirements

If you want your IdP to authenticate users, there are two options:

• Microsoft Entra ID B2B collaboration
  If your primary IdP is Microsoft Entra ID, or your IdP domain name is DNS-verified in Microsoft Entra ID, Identity V1 requires B2B (business to business) collaboration with your IdP.

• SAML 2.0
  Identity V1 supports SAML 2.0 configurations for any IdP except Microsoft Entra ID. To use SAML 2.0, your DNS configuration must include an authentication URL.

  If the primary IdP for your company or organization is Microsoft Entra ID, use Identity V2 for direct SAML 2.0 integration.

Verint Identity is a cloud service that requires user names in FQDN format so that the service can redirect authentication requests. Verint Identity requires each user to have:

• An account with the IdP.

• A user name in FQDN format such as UserName@example.company.com.

Cross-tenant access settings in Microsoft Entra ID manage how your IdP collaborates with other Microsoft Entra ID organizations such as Verint, and how your IdP trusts multi-factor authentication (MFA) and device claims from other organizations.

Supported provisioning options:

• SCIM 2.0
  For automated user provisioning from an IdP, Identity V1 requires SCIM 2.0 enabled in your IdP. Verint does not support SCIM automated provisioning in combination with WFE Sync.

• Verint Identity Management
  For manual user provisioning (non-SCIM), Verint Identity requires user details added to the Verint Identity Management portal.

• WFE Sync
  For existing Verint cloud Workforce Engagement (WFE) customers, WFE Sync synchronizes all user creation, update, and delete operations from WFE to the Identity Service. Verint Identity does not support WFE Sync for on-premises WFE customers, and does not support WFE Sync combined with SCIM 2.0 automated provisioning.