Defect #3388
openCopnfiguraiton of allowedAutoMappingOnExistingAccount=false is ignored when systemEntity exists and is not "wish"
0%
Description
In my environment, I synchronized AD accounts and linked them to identities in IdM through standard synchronization. Accounts that were not linked to identities remained in AD, and IdM created its SysSystemEntity
objects with the "wish" attribute set to false
. To prevent automapping and avoid linking the new user to the old existing account, I have set idm.sec.acc.provisioning.allowedAutoMappingOnExistingAccount=false
. However, a new user with the same login (identifier for AD) as an existing, non-linked account in AD was created. Instead of throwing an exception, IdM automapped and linked the account to the identity. This behavior occurs because the prepare-connector-object-processor
runs the same code as if I had configured idm.sec.acc.provisioning.allowedAutoMappingOnExistingAccount=true
, when a SysSystemEntity
with the same identifier and "wish" attribute set to false
exists.
Related issues
Updated by Vladimír Kotýnek over 1 year ago
- Related to Task #864: Parameter for disable account reusing added