[midPoint] Writing a boolean attribute as activation configured capability

[Radovan Semancik]

Hi,

Try to force the value type using the standard xsi:type mechanism. Like 
this:

<cap:enableValue xsi:type="xsd:boolean">false</cap:enableValue>

However, this is quite an old code that originated some 4-5 years ago 
and as far as I know it was never reviewed. So there is that does not 
work then you are most likely hitting a bug. In that case please report 
the issue in Jira.

-- 
Radovan Semancik
Software Architect
evolveum.com



On 06/01/2016 11:29 PM, Gustavo J Gallardo wrote:
> We're working with the GoogleApps connector, which does not support 
> activation, so we set up a configured capability to set the boolean 
> 'suspended' attribute.
> We can read and interpret the value correctly, however when writing 
> the attribute from <capabilities>, it is sending a String instead of a 
> boolean.
> If I map the account attribute to a user attribute, we can write it 
> correctly.
>
> <capabilities>
> ...
> <configured>
> <cap:activation>
> <cap:status>
> <cap:attribute>ri:suspended</cap:attribute>
> <cap:enableValue>false</cap:enableValue>
> <cap:disableValue>true</cap:disableValue>
> </cap:status>
> </cap:activation>
> </configured>
> </capabilities>
>
> Is there any way inside the 
> .../capabilities/configured/cap:activation/cap:status/cap:enableValue/ 
> to indicate it has to be treated as a boolean?
> We are working with 3.4-SNAPSHOT.
>
>
> Thanks,
>
> GJG
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20160616/83b35109/attachment.htm>