[midPoint] Understand constraint violation: Found conflicting existing object

[Pavol Mederly]

Hello Fabian,

this is because midPoint compares normalized names, see 
https://docs.evolveum.com/midpoint/reference/schema/polystring-normalization/.

Best regards,

-- 
Pavol Mederly
Software developer
evolveum.com

On 28/07/2022 11:13, Fabian Noll-Dukiewicz via midPoint wrote:
>
> Hi everone,
>
> I'm trying to understand why the names “OD:CORPAD:1E-S__IdM” and 
> “OD:CORPAD:1ES__IdM” are the same in midpoint.
>
> I got the following error:
>
> Error processing 
> focus(role:fbb1df46-1dc1-4c1e-88e0-be37d30e5564(OD:CORPAD:1E-S__IdM)): 
> constraint violation: Found conflicting existing object with property 
> name = 
> PP({.../common/common-3}name):[PPV(PolyString:OD:CORPAD:1E-S__IdM)]: 
> role:2cdc1387-a47d-4a09-a876-13145f5b840f(OD:CORPAD:1ES__IdM)
>
> My customer runs midpoint 4.3.1.
>
> The scenario is, that we import AD groups and create roles from these 
> groups. The name is build with prefix “OD:CORPAD:” and the 
> samaccountname. If I replace the dash (-) with underscore (_) it works 
> but this is not what I want, because I need the original name with 
> prefix for another connected system.
>
> Thanks in advance.
>
> Kind regards,
>
> Fabian
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> https://lists.evolveum.com/mailman/listinfo/midpoint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20220728/91aaf988/attachment.htm>