The data of member property (vrt_member@UCIUser) was not transferred

We have a SCIM connector where the user-membership is on the /User schema and for the handling of memberships we are using the virtual property vrt_member (Members of M:N schema types) that refers the table UCIUserHasGroup. In the virtual property, the checkbox "Enable relative complement handling (required for member rules)" is not checked. When we check it, we receive the error message "Object matching rule (vrt_member <-> value) from the system map (User) uses schema properties with a different data type. If you apply this rule, an error will occur.  Solution   Disable the option "Enable relative complement handling" on the virtual property (UCIUser.vrt_member)."

All operations regarding user membership work when we don't have this checkbox enabled. For instance, adding 2 groups to the user account and removing 1 group from the user account. However, we receive the error message when an employee loses the account definition and One Identity tries to remove the user-membership. 

Process that fails: UCI_User_Update

Error: [2134028] The data of member property (vrt_member@UCIUser) was not transferred. Possible reasons are configuration issues or an invalid object state

I have tried to change the condition of the mapping, but in all possible scenarios, the error message still occurs. For us, this message seems like a false-alarm and we noticed that even when ignoring the message, the functionality of removal of user-membership in the SCIM API Target System seems to work.

 

Does anyone have an idea on how to minimize this error?

Parents
  • Hi Chysoula,

    does the process of loosing the account definition delete or deactivate the user and the remove of groups is not allowed anymore?

    Regards,

       Tino

  • Hello Tino,

    When the user account loses the account definition, the process UCI_User_Update runs twice. One with the error message "[2134028] The data of member property (vrt_member@UCIUser) was not transferred. Possible reasons are configuration issues or an invalid object state" that fails, and one that actually deactivates the user account in the Target System. 

  • Hi Chrysoula,

    so I think you have two options: a) synchronize the processes and let the remove operation run before deactivation comes to execution or b) Set the option "Retain groups if user account disabled" at Manage level your Account definition is using - this will prevent the update process trying to remove the groups.

    Regards,

      Tino

Reply
  • Hi Chrysoula,

    so I think you have two options: a) synchronize the processes and let the remove operation run before deactivation comes to execution or b) Set the option "Retain groups if user account disabled" at Manage level your Account definition is using - this will prevent the update process trying to remove the groups.

    Regards,

      Tino

Children