Identity V2 authentication and provisioning requirements

Requirements for integrating with Verint Identity V2.

Mandatory or Optional	Requirement	Description
Mandatory for federated authentication	Authentication through an Identity Provider (IdP) that supports OpenID Connect (OIDC) or SAML (Security Assertion Markup Language) 2.0	Identity V2 uses an industry-standard identity platform which supports OIDC and SAML 2.0 for exchanging authentication information with an IdP.
Mandatory for federated authentication	Fully Qualified Domain Names (FQDNs)	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.
Optional	Verint domains whitelisted	Whitelisting Verint domains in your network or firewall ensures that Verint can exchange user and machine-to-machine (M2M) authentication information with your company or organization.
Mandatory	User provisioning	Supported provisioning options: SCIM 2.0 For automated user provisioning from an IdP, Verint Identity requires SCIM 2.0 enabled in the IdP. Verint Identity does not support SCIM automated provisioning combined with WFE Sync. Verint Identity Management For manual user provisioning (non-SCIM), Verint Identity requires user details added to the Identity Management portal. WFE Sync For existing Verint cloud Workforce Engagement (WFE) customers, WFE Sync synchronizes all user create, update, and delete operations from WFE to the Identity Service. Verint Identity does not support WFE Sync for on-premises WFE customers, or WFE Sync combined with SCIM automated provisioning.