[midPoint] multivalue attribute updating

[Samuel Harmon]

We're pulling in address information from a database (using a
ScriptedSQL resource) as colon separated strings (i.e.
line1;line2;city;state;postalCode)- this is then split into a
multivalue attribute in midPoint which is then provisioned out to
LDAP/AD attributes using some complicated rules about address
precedence and suppression, and for most uses this is working
properly.

We've run into an issue when the address field in the database
changes. Right now, when a new address comes in, its split-out
components just get appended to the multivalue attribute after the old
values, so the old address information keeps getting provisioned out
and the new is ignored.

I tried setting the predefined "all" set option on the attribute in
the database resource to try to fix this. When I attempted to
reconcile an affected user, it then removed the old values, but ended
up scrambling the order of the updated values, which causes all of the
downstream provisioning to have incorrect values (city going into
postalCode, etc.).

Has anyone run into issues like this before? Any thoughts on how to
maintain the order of attribute multivalues when updating them?

Sam Harmon
Case Western Reserve University