[midPoint] Issue with inbound mapping from singled-valued to multi-valued attribute

[Javier Martinez]

Hello,
thank you for your reply!
I will try to change it to 'model' and I'll let you know the outcome.

Regards!

On Thu, Jun 25, 2020 at 5:28 AM Musliu Atdhe <atdhe.musliu at zhdk.ch> wrote:

> Hi, Have you tried to change the Layer to ‘model’ or ‘schema’ ?
>
> I would try to change it to ‘model’ and then test it again.
>
>
>
> https://wiki.evolveum.com/display/midPoint/User+Interface+Form+Fields :
>
> ‘Model layer means application of schema constraints inside the IDM Model
> Subsystem <https://wiki.evolveum.com/display/midPoint/IDM+Model+Subsystem>.
> This is the value that the midPoint identity management logic will be
> using. It will be used by mappings and similar mechanisms.
>
> E.g. LDAP attributes uid, cn, sn are formally multi-valued in the LDAP
> schema. But vast majority of systems are using them as single-valued
> attributes. Setting multiple values for these attributes can easily ruin
> interoperability. Therefore these attributes can be defined as single
> valued (maxOccurs=1) in the model layer. Then any mapping that produces
> multiple values for these attributes will fail which makes the diagnostics
> and troubleshooting much easier.
>
> ‘
>
>
>
> Best Regards
>
> Atdhe
>
> —
>
> —
>
> Zürcher Hochschule der Künste
>
> Zurich University of the Arts
>
> —
>
> Atdhe Musliu
>
> Mitarbeiter Informationstechnologie-Zentrum
>
> ——
>
> www.zhdk.ch
>
> http://www.zhdk.ch/?itz
>
>
>
> *Von:* midPoint <midpoint-bounces at lists.evolveum.com> *Im Auftrag von *Jason
> Everling
> *Gesendet:* Wednesday, 24 June 2020 19:03
> *An:* midPoint General Discussion <midpoint at lists.evolveum.com>
> *Betreff:* Re: [midPoint] Issue with inbound mapping from singled-valued
> to multi-valued attribute
>
>
>
> Yes, it doesn’t fix the inbound stuff, it is merely a fix to prevent an
> end user from adding multiple values
>
>
>
> *From: *Javier Martinez <jmartinez at identicum.com>
> *Sent: *Wednesday, June 24, 2020 11:58 AM
> *To: *midPoint General Discussion <midpoint at lists.evolveum.com>
> *Subject: *Re: [midPoint] Issue with inbound mapping from singled-valued
> to multi-valued attribute
>
>
>
> Hi Jason,
>
> Thank you very much for your answer, we tried with this approach and when
> we tried to change the value of a user, we got the error "Expected one
> value for attribute organization, got 2".
>
>
>
> It worked with the solution given by Ivan.
>
>
>
> Regards!
>
>
>
>
>
>
>
> On Mon, Jun 22, 2020 at 5:02 PM Jason Everling <jeverling at bshp.edu> wrote:
>
> You can also remove the multi-value capability from the gui using the
> default user template, it just prevents some user from adding an additional
> value if you really want it to be single-valued only
>
>
>
>     <item>
>
>         <c:ref>c:organization</c:ref>
>
>         <limitations>
>
>             <layer>presentation</layer>
>
>             <minOccurs>0</minOccurs>
>
>             <maxOccurs>1</maxOccurs>
>
>         </limitations>
>
>     </item>
>
>
>
> *From: *Javier Martinez <jmartinez at identicum.com>
> *Sent: *Monday, June 22, 2020 2:16 PM
> *To: *midPoint General Discussion <midpoint at lists.evolveum.com>
> *Subject: *Re: [midPoint] Issue with inbound mapping from singled-valued
> to multi-valued attribute
>
>
>
> Hi,
>
> I added the the range as mentioned above:
>
>
> *<set>      <predefined>all</predefined>*
>
> *</set>*
>
>
>
> and it's working correctly, it now replaces the previous value instead of
> adding a new one.
>
>
>
> Thank you!
>
> Regards
>
>
>
> On Fri, Jun 19, 2020 at 1:01 PM Paulo Fernandes de Souza Junior <
> PFSJ at senado.leg.br> wrote:
>
> Hi,
>
>
>
> Take a look at
> https://wiki.evolveum.com/display/midPoint/Inbound+Mapping#InboundMapping-RangeOfInboundMappings
> ​
>
>
>
> *Paulo Fernandes de Souza Júnior*
>
> *NQPPPS *Senado Federal - PRODASEN
> Fone: 61 3303.3924
>
>
>
> *De:* midPoint <midpoint-bounces at lists.evolveum.com> em nome de Javier
> Martinez <jmartinez at identicum.com>
> *Enviado:* quarta-feira, 17 de junho de 2020 11:23
> *Para:* midPoint General Discussion
> *Assunto:* [midPoint] Issue with inbound mapping from singled-valued to
> multi-valued attribute
>
>
>
> Hi,
>
> We are having an issue when having an inbound mapping from a single-valued
> attribute to a multi-valued attribute. When modifying the value from the
> resource, instead of replacing the value, it is adding new values to the
> attribute in midPoint. Tested with attributes "organization" and "subtype".
>
> Working OK in midpoint 3.9, but failing with midpoint 4.0.1 and above.
>
> Is there any way to keep this issue from happening?
>
> Regards
>
> --
>
> Javier Martínez
>
> Identicum S.A.
> Jorge Newbery 3226
> Tel: +54 (11) 4552-3050
> www.identicum.com
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> https://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
>
> --
>
> Javier Martínez
>
> Identicum S.A.
> Jorge Newbery 3226
> Tel: +54 (11) 4552-3050
> www.identicum.com
>
>
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> https://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
>
> --
>
> Javier Martínez
>
> Identicum S.A.
> Jorge Newbery 3226
> Tel: +54 (11) 4552-3050
> www.identicum.com
>
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> https://lists.evolveum.com/mailman/listinfo/midpoint
>


-- 
Javier Martínez
Identicum S.A.
Jorge Newbery 3226
Tel: +54 (11) 4552-3050
www.identicum.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20200626/e74fea7b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 144 bytes
Desc: not available
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20200626/e74fea7b/attachment.png>