tree 19d623f046cc0d0205ed92bcb4debf77f827d3f4
parent c687ab7263146754db80be13d22fa3a9230848bc
author Marc Blank <mblank@google.com> 1342214449 -0700
committer The Android Open Source Project <initial-contribution@android.com> 1344017015 -0700

Don't set DPM password expiration unless it has changed

* Because we push the expiration value frequently (not only when
  policies change, but also after alerting the user to change his
  settings), we're pushing this value further and further into
  the future.
* In the referenced bug, the data IS being deleted, but then the
  expiration is pushed out, putting us back into compliance with
  policies (wrongly), which leads to the data syncing right back
  again
* The fix is to only push the expiration when it has changed; the
  fix is trivial

Bug: 6813598
Change-Id: Ibd238813e3f2f25e7f1f176c31cb31d00874dba6