Project

General

Profile

Actions

Defect #2424

closed

Synchronization creates a new identity with the default value in EAV instead of the mapped value

Added by Alena Peterová over 4 years ago. Updated over 4 years ago.


Description

Version 10.4.1

When synchronization of identities creates a new identity and some of the mapped EAVs have default value, then the default value is saved in the identity, instead of the mapped value.
The second run of the synchronization updates the identity correctly.

Steps to reproduce:
  • Create an EAV of IdmIdentity with some default value - "false" in our case.
  • Map the EAV in the synchronization of identities, set "Transformation from" to some different value - Boolean.TRUE in our case
  • Run the synchronization
  • Identity was created, but the value of the EAV is "false". (wrong)
  • Run the synchronization again
  • The EAV was changed to "true". (OK)

(Our use case: We want to "flag" identities created by one special synchronization as "System accounts". By default, the identities are not system accounts.)

Tested for Boolean and ShortText, the result is the same.


Files

form_attribute.png (41.5 KB) form_attribute.png Alena Peterová, 08/04/2020 02:40 PM
sync_mapping.png (42.6 KB) sync_mapping.png Alena Peterová, 08/04/2020 02:40 PM

Related issues

Related to IdStory Identity Manager - Task #2248: Synchronization: save extended attribute values together with entityClosedVít Švanda05/12/2020

Actions
Related to IdStory Identity Manager - Task #1267: Support save EAV with EntityClosedRadek Tomiška09/24/2018

Actions
Actions

Also available in: Atom PDF