[midPoint] validityStatus changing validTo date

[Nicolas Rossi]

Hi guys, we have reproduced this issue on a fresh install of midPoint 3.5.
These are the steps to reproduce it:

   1. Extended the schema with 2 attributes (a flag and a date) → user.xsd
   2. Created a UserTemplate mapping the custom date to the validTo if the
   flag is active. → user_template.xml
   3. Assigned the UserTemplate as the default template for users.
   4. Create a user
   5. Modify the user setting the flag and a date before today

Result:

   - The validTo date is mapped correctly
   - The user is still enabled

Regards,



Ing Nicolás Rossi
Identicum S.A.
Jorge Newbery 3226
Tel: +54 (11) 4552-3050
www.identicum.com

On Sun, Jan 22, 2017 at 8:30 AM, Nicolas Rossi <nrossi at identicum.com> wrote:

> Hi guys, we have a User Template that defines the validTo date evaluating
> 2 different dates. When a user is active and the calculated validTo date is
> before today the user is not being disabled by midpoint as we expected. I
> found a little difference between this user and other one not handled by
> the user template, on the activation node it has validityStatus=in instead
> of validityStatus=after:
>
> User disabled OK (changed from GUI, not from the UserTemplate):
>
> <activation>
>       *<effectiveStatus>disabled</effectiveStatus>*
>       *<validTo>2017-01-15T00:00:00.000-03:00</validTo>*
>       *<validityStatus>after</validityStatus>*
>       <disableTimestamp>2017-01-22T08:24:48.970-03:00</disableTimestamp>
>       <enableTimestamp>2017-01-22T08:24:31.529-03:00</enableTimestamp>
>       <validityChangeTimestamp>2017-01-22T08:24:48.970-03:00</
> validityChangeTimestamp>
>    </activation>
>
> User not being disabled (changed from UserTemplate):
>
> <activation>
>      * <effectiveStatus>enabled</effectiveStatus>*
> *      <validTo>2017-01-15T00:00:00.000-03:00</validTo>*
> *      <validityStatus>in</validityStatus>*
>       <disableTimestamp>2017-01-22T08:13:40.530-03:00</disableTimestamp>
>       <enableTimestamp>2017-01-22T08:13:58.962-03:00</enableTimestamp>
>       <validityChangeTimestamp>2017-01-22T08:13:58.962-03:00</
> validityChangeTimestamp>
>  </activation>
>
> ​Should I set the validityStatus on the UserTemplate?
>
> Regards,
>
>
> Ing Nicolás Rossi
> 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/20170123/37734b24/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: user_nrossi.xml
Type: text/xml
Size: 3495 bytes
Desc: not available
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170123/37734b24/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: user_tempalte.xml
Type: text/xml
Size: 1859 bytes
Desc: not available
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170123/37734b24/attachment-0001.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: user.xsd
Type: application/octet-stream
Size: 1354 bytes
Desc: not available
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170123/37734b24/attachment.obj>