ADHOC/replicant-packages_apps_Email
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Password history changes do NOT require user intervention

Browse Source 
* A change in history requirement is not intended to force a new
  password immediately; we just tell the DPM what the new
  requirement is...
* This is one cause of the below-referenced bug

Bug: 5221119
Change-Id: I890b42d4eab4fbd9d34665fbea138f179d5d3215
This commit is contained in:
Marc Blank 2011-08-28 16:34:28 -07:00
parent 9bcdd58a09
commit e86d8af163
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/com/android/email/SecurityPolicy.java
View File

@ -397,7 +397,8 @@ public class SecurityPolicy {
} }
if (policy.mPasswordHistory > 0) { if (policy.mPasswordHistory > 0) {
if (dpm.getPasswordHistoryLength(mAdminName) < policy.mPasswordHistory) { if (dpm.getPasswordHistoryLength(mAdminName) < policy.mPasswordHistory) {
reasons |= INACTIVE_NEED_PASSWORD; // There's no user action for changes here; this is just a configuration change
reasons |= INACTIVE_NEED_CONFIGURATION;
} }
} }
if (policy.mPasswordComplexChars > 0) { if (policy.mPasswordComplexChars > 0) {