Hello!
Is it possible to map a single metaverse attribute to multiple data source attributes during export flow? Each person object has a multi-value string attribute containing string-encoded account information and we need a way to map it during export to the corresponding account objects. Unfortunately, it is not possible to select multiple data source attributes in the export flow configuration window, multiple MV attributes are fine on the other side (but not what we need).
Creating the account object and connecting it to the person (provisioning) already works but we cannot export our account attributes. It is not possible to set the attributes during export with code (rules extension) because they are read-only except the
one that is currently scheduled for export. And mapping each attribute 1:1 means splitting/parsing the account string for every single exported attribute which is from a performance point of view suboptimal. It would be better if there is a way to parse the
string only once and set all affected attributes.
If that doesn't work, is there another way to properly manage user accounts? We have a very heterogenous organization and our current IDM solution supports managing accounts via LDAP and workflows (e. g. triggering scripts to create accounts on target machines). But it works quite different from the way FIM does (for example event based vs. state based).
Thanks in advance!