[midPoint] validityStatus changing validTo date

[Nicolas Rossi]

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/20170122/afb7cc6e/attachment.htm>