Duplicate Key error on insert into sys_import_set table for every user loginIssue When logging in via Multi Provider Single Sign On, a duplicate key error is thrown indicating an attempt to insert a duplicate primary key entry into the sys_import_set table. In addition, a new row is created in the list of sys_import_set records that is labeled '(empty)'.ReleaseNew York ReleaseCauseThe IDP record in ServiceNow was initially set to do user synchronization. Since attribute data was including in the SAML Response object, the platform created a default user provisioning transform map. The transform map fields mappings were not set to map the attributes returned in the SAML Response object. Therefore, at run time the transformation failed a null values were passed into the transformation. This caused the error observed. ResolutionIf you don't want to use the user provisioning/synchronization mechanism for SSO, then just make the user provisioning transform map inactive. This will avoid the error and the empty import set. If you want to use the user provisioning/synchronization mechanism then use the mapping assist from the transform and map the fields as you need. While doing the mappings, use the source fields with names starting with "https://.." , which are the ones related to SAML Response attributes.