[midPoint] midPoint Digest, Vol 87, Issue 8
Ivan Noris
ivan.noris at evolveum.com
Wed Jul 10 08:16:07 CEST 2019
Hi Keith,
you have overriden the employeeType attribute to act as single value
here in schema handling:
<attribute id="25">
<c:ref>ri:employeeType</c:ref>
<limitations>
<maxOccurs>1</maxOccurs>
</limitations>
...
So even if the employeeType attribute is multi-value in schema, the
schema handling overrides it to a single-valued one.
You may either:
1. remove the <limitations> element with <maxOccurs>1</maxOccurs> from
the "ri:employeeType" attribute definition in schema handling
or
2. make sure you are not trying to push two different values to a
single-value attribute.
midPoint is really complaining only because you are putting two values
("Staff" and "Alumni") to the attribute which is configured to act as a
single-valued. If the attribute is without this limitation, it should work.
Best regards,
Ivan
--
Ivan Noris
Senior Identity Engineer
evolveum.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20190710/69c7492b/attachment.htm>
More information about the midPoint
mailing list