diff options
| author | Eran Messeri <eranm@google.com> | 2018-04-30 16:16:39 +0100 |
|---|---|---|
| committer | Eran Messeri <eranm@google.com> | 2018-05-01 14:12:23 +0100 |
| commit | 9ecde42164cf1a3d24878d52411f12fcb348092e (patch) | |
| tree | 4701e347eae3601960c0350b1ac09c9c0a0a8170 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | e4d1cabe457d1e5435377015d5511520ca582a87 (diff) | |
Save password requirements on the right user
When changing the password requirements, two changes have to be saved:
(1) Whether the current password complies with the new password
requirements.
(2) The new password requirements themselves.
(1) is stored on the credential owner of the user, (2) is stored on the
user itself.
In ag/3729963 (Change-ID: Ide5b2e53cf100b087822844ca51b3bc69e7ddf82),
we've switched from saving the password sufficiency flag (1) in the
user to the credential owner.
A side effect was that the password requirements themselves, (2), which
were changed on the original user the call related to, were not saved.
This fixes the bug introduced in the aforementioned CL.
Bug: 78499736
Test: Manual with TestDPC.
Change-Id: I11faef37fa6f0e8e8e558069e77021c48ee36cd4
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions