summaryrefslogtreecommitdiffstats
path: root/src/com/android/settings/ConfirmLockPattern.java
Commit message (Collapse)AuthorAgeFilesLines
* Clean up choose lock intent creationMaurice Lam2017-05-121-570/+0
| | | | | | | | | | | | Consolidated the many variants of ChooseLock*.createIntent, so that it will take the same set of arguments. Also modified SetupChooseLock*.createIntent to modifyIntentForSetup, which will take the intent created by ChooseLock* and modify it for use with setup. Test: cd tests/robotests && mma Change-Id: I5ff033f459c33ec9980872a536b3996d89f2bbbb
* Prevent fingerprint from bypassing work challengeCharles He2017-04-191-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | After too many incorrect attempts at entering the user credential (PIN, password, or pattern) for the work profile, a timeout will be triggered to limit the rate of retries. At the same time, fingerprint should no longer be allowed to unlock the work profile, until the user unlocks it with the correct user credential. Previously, fingerprint was not banned from unlocking the work profile during and after the said timeout. (Pattern lock screen only had a partial fix which removed the fingerprint UI, but still allowed fingerprint to unlock.) This CL fixes the issue. It also replaces the following fields with equivalent getter methods: - mIsStrongAuthRequired, - mAllowFpAuthentication. Otherwise, we would have to rely on these internal states being always up-to-date, which is less maintainable. Test: make SettingsGoogle and manually enter incorrect PINs/patterns Bug: 36912481 Change-Id: Id6ac6b5c78bdc19078ce8dd7acb4ec41329e57c3
* Use GLIF theme for screen lock confirmationMaurice Lam2017-03-151-18/+21
| | | | | | | | | | | | | | Theme the confirm password screen similar to setup wizard and screen lock enrollment flow, so that we can start showing it during setup wizard. The new layouts are called "internal" because it's supposed to be used only when another settings screen starts it. For external intents from CONFIRM_DEVICE_CREDENTIAL, the existing theme and layout are unchanged. Bug: 32373672 Test: Run ConfirmLockPasswordTest with `am instrument` Change-Id: Ib887a763a073e6e4b96264d08846827b2e5cbf52
* Update package names to work with the proto3 compilerTamas Berghammer2016-11-081-1/+1
| | | | | Bug: b/28974522 Change-Id: I5f3adf4946ee4ba1e09e4f40afe83c151405972a
* Eliminate useless 'isManagedProfile' utils methodRobin Lee2016-09-121-3/+1
| | | | | | This exists in UserManager now Change-Id: If35326a1fe0de3c7bfde842c5c170899dc5d819b
* Log visibility change for all fragments.Fan Zhang2016-08-181-1/+1
| | | | | | | | | | Bug: 30681771 Test: SettingsUnitTests Refactor visibility logging from InstrumentedFragment into a mixin. And apply mixin in remaining fragments. Change-Id: Ibbb59904336254a3e4bb9e8c7d0b36e5a6bc2622
* Should not report unsuccessful attempt if pattern size < minimal sizeTony Mak2016-07-201-1/+2
| | | | | | | It is to align the behavior in personal side lock screen. Change-Id: I811e72405615fbed85c2a4dc6b6cec51e4ad54f0 Fix: 30215101
* Refresh screenlock UI after password verification failedRicky Wai2016-06-271-0/+1
| | | | | Bug: 28314264 Change-Id: Ibd715d70bbee728a887f779a24bb99ad32d8d2ed
* Fix Continous loop in unifed screenlock when trying to Trust a CA certVictor Chang2016-05-201-4/+6
| | | | | | | | | | | | | | | | | | | | | | Cause: with unified screenlock, ConfirmDeviceCredentialActivity didn't forward result with FLAG_ACTIVITY_FORWARD_RESULT Also, fixed that ConfirmDeviceCredentialActivity didn't allow fingerprint authenication in unified screenlock after keystore unlocked. In ChooseLockSettingsHelper, add one new util function to allow extra option to set returnCredentials to false while external to true. Set StrongAuth to "not required" when it has been successfully unlocked. Test: 1. PO Unified Screenlock/Work Challenge x fingerprint -> ok to trust cert (Also, no credential is returned in intent) 2. WorkMode off -> Reboot -> turn on Work mode -> no fingerprint option, PIN unlock successful to turn work mode on Bug: 28752364 Change-Id: I6dc8865e8f005545f8577d7731afb4495647062b
* New UI to hint user about strong authTony Mak2016-04-211-14/+15
| | | | | | | | | Instead of having a separate textview, we now reuse the detail textview to show the hint. Fix: 28204828 Change-Id: I3eff3240bf7ecb1495fbf11a073a273a0de603ae
* Hint user that fingerprint cannot unlock FBE keysDaniel U2016-04-081-0/+7
| | | | | | | | | | | | Show a hint text to user noting that pattern/PIN/password is required when decrypting the credential based storage when file based encryption is turned on. The hint text is the same as that of the device unlock screen after device reboot. Bug: 27964055 Change-Id: I0d5a493bab69eae5ce4742bd07d4851387863cac
* Fingerprint should confirm device lock when unifiedRicky Wai2016-04-071-19/+23
| | | | | | | | When unified and adding a fingerprint, the user is prompted to set up a backup Bug:27419438 Change-Id: I6cfa8c276ae69a0af51580be390c3da4e9596874
* Call reportFailedPasswordAttempt from Work ChallengeClara Bayarri2016-02-171-7/+22
| | | | | | | | | | | | | | | | Entering the wrong credential in ConfirmDeviceCredentials should also count as failed attempts for the password, after which the DPC have set a restriction to wipe the work profile. Fixed related issues, such as the CredentialChecker re-sending the result after onResume causing additional attempts to be counted. The new error message String is also displayed initially when there are pending attempts to inform the user that they are not starting from fresh. Bug: 26677759 Change-Id: I70cfae4c05e705ad7fe93bc071426459b79e7d0c
* port settings over to new metrics enumChris Wren2016-01-271-2/+2
| | | | Change-Id: I0b3efd2f4db773ccbc52bfe59ee8eb0dab9584fb
* Profile Challenge Fingerprint SupportClara Bayarri2016-01-261-5/+0
| | | | Change-Id: Ic83c479f645776dd0678721bfb732b399f09c992
* Fix Confirm/Choose Credentials strings related to profileClara Bayarri2016-01-251-1/+6
| | | | | | | | | | | | | | | The messages in ConfirmDeviceCredentials have been updated to inform the user that the pattern/pin/password to be entered is the profile one. The strings in the confirmation dialog when the user removes the lock have also been updated. Ideally we would have a parametrized approach to strings here, but capitalization makes it a hard problem. Bug: 26706338, 26709116 Change-Id: I9f5508d6f449f9e572d65e5b2dcb15cca23832b3
* Add background image for work challengeBenjamin Franz2016-01-211-1/+1
| | | | | | | If the challenge shown is for a work profile, add the default image and color to the background of the fragment. Change-Id: I148c6cd3a835a84c7bac78b020839dfdae4a6c36
* Fire pending intent from Confirm Credentials flowClara Bayarri2015-12-151-0/+2
| | | | | | | | | Add support in the Confirm Credentials flow to read an Intent extra and fire it when authentication succeeds. This is part of the Separate Work Challenge feature. Change-Id: I52c203735fa9b53fd2f7df971824747eeb930f36
* Refactor Choose/Confirm Lock flow to take user idClara Bayarri2015-10-161-1/+3
| | | | | | | This is a first step to allow this flow to be reused for setting a work profile-specific lock, to be used with the work challenge. Change-Id: Iaa65fdab9021cda5f0a1d3bc526a6b54f8a7dd16
* Depend on support lib preferencesJason Monk2015-10-131-15/+15
| | | | | Bug: 24576551 Change-Id: Ic6190bacd3f7582c9bbc8de972da4612bd92421e
* Fix races in ConfirmPassword/PatternXiyuan Xia2015-08-311-37/+57
| | | | | | | | | | | | | | - Add a CheckLockResultTracker to track result of async lock check so that it can finish on configuration change; - Let the pending lock check finish and ignore subsequent check requests; - Add a mDisappearing flag to prevent running disappear animation multiple times; - Check whether activity is still active after disappear animation before setting result and finishing it; - Remove no longer used mNumWrongConfirmAttempts; Bug:23190499 Change-Id: If1784d3d1fcc152ac06137b12748b9def5726692
* [ConfirmPattern] use correct user id for stealth modeAndres Morales2015-08-111-1/+1
| | | | | Bug: 23027554 Change-Id: I9582dab3a0355f613d0ce1c943b0eeba2694dddd
* fix CC for work profilesAndres Morales2015-08-051-10/+17
| | | | | Bug: 22257554 Change-Id: I09f62956d01f91d3014d9fa250aaff68ab5e1a9b
* Use pattern visibility setting on confirm pattern screen.Julia Reynolds2015-07-281-12/+4
| | | | | Bug: 22683055 Change-Id: Icc4c0c20175e09a0079f7a6bab93d3de6862f1a3
* Move PIN/Pattern appear animation to RenderThread (2/2)Jorim Jaggi2015-07-211-34/+6
| | | | | Bug: 22205322 Change-Id: Idd16de04701c330b7559bb403316f691a9a717e9
* Talkback improvements for Settings screens.Julia Reynolds2015-07-091-0/+1
| | | | | Bug: 21164141 Change-Id: I7444261ccf967f6db70c9fe44a00bd3f19ceb975
* Animations/success state for external confirm device credentials (2/2)Jorim Jaggi2015-06-101-6/+149
| | | | | Bug: 20929186 Change-Id: I4489dd37f1148fb03315ec337a546eee04660cb5
* Use accessibilityLiveRegion for ConfirmLockPassword/Pattern errorTextXiyuan Xia2015-06-021-11/+2
| | | | | | | | | - Revert previous "Add announceForAccessibility to ConfirmLockPattern"; - Add android:accessibilityLiveRegion="polite" for errorText in ConfirmLockPassword/Pattern; Bug:20282779 Change-Id: I4b9c0d461d0dd0504bd88a8a2144e09a42d5f64e
* Add announceForAccessibility to ConfirmLockPatternXiyuan Xia2015-06-011-3/+11
| | | | | | | | This makes Talkback in ConfirmLockPattern works similarly as in ConfirmLockPassword to read out error messages. Bug:20282779 Change-Id: Ied05c284e959539cfbff965f33edd51c3bdfc9f9
* [ConfirmCredential] fix issue where patterns of length 4 are not checkedAndres Morales2015-05-271-1/+1
| | | | Change-Id: I2bfcae01be88001a6a9bafa4908305d464522302
* [LockSettings] pipe through HW throttle timeoutAndres Morales2015-05-261-11/+13
| | | | | Bug: 21118563 Change-Id: I23f5af2ebef9dac981281fb04c055a02f3b159b8
* Migrate settings UI to use async security checkXiyuan Xia2015-05-131-21/+78
| | | | | Bug: 20697812 Change-Id: Ieb0090ddb61198a60abb1e34ff9c6e8476c33789
* Require explicit userId in LockPatternUtilsAdrian Roos2015-04-281-5/+8
| | | | | Bug: 18931518 Change-Id: Ie2faa18918aaadf17a84287898438549a693b0cc
* Unbreak CC screenAndres Morales2015-04-161-2/+4
| | | | | | Re-add logic in authenticationSucceeded Change-Id: Iac1925f5e2f2f67dd5d7c7f5d454f32691d51b61
* Request enroll or verify lock before FP enrollAndres Morales2015-04-141-9/+1
| | | | | | Also pipe through challenge token Change-Id: I9d6afdbadf3832aeeb18a0b5a9620277e2070872
* pipe auth token through confirm and set passwordAndres Morales2015-04-141-1/+28
| | | | | | | | | | ConfirmDeviceCredentialsActivity and ChooseLockGeneric now understand CLSH.EXTRA_KEY_HAS_CHALLENGE and CLSH.EXTRA_KEY_CHALLENGE in their launching intents. If present, they return a hw_auth_token_t verifying the challenge passed in as a field in keyed by CLSH.EXTRA_KEY_CHALLENGE_TOKEN in their result intents. Change-Id: I0b4e02b6a798a9e57d02522880a180dffadfcde1
* Update confirm device credentials to spec, add fingerprintJorim Jaggi2015-04-131-59/+49
| | | | | | | | | | | - New strings in the screen. - New layout/style. - Clean up internal API's around it. - Add fingerprint support if launched from externally - Separate theme if launched from externally - If launched from above Keyguard, use SHOW_WHEN_LOCKED flag Change-Id: Icdf9bf9e0506841f24e8aab5f0f1d1f4b688951f
* log visibility of viewsChris Wren2015-03-271-1/+7
| | | | | Depends-On: I5b1dccb5d103ece3112acf38889bae16273b092f Change-Id: I116aed2bb805f723a5bf2ec9eb94257de0b4a7b5
* Remove usages of LPU.savedPatternExistsAdrian Roos2015-01-091-1/+1
| | | | | | | | | | The correct method to call is isLockPatternEnabled, which also checks whether we've actually selected a pattern. Also removes the code for the obsolete pattern enabled setting. Bug: 18931518 Change-Id: I6f369eb60f8f6bb1e33384cd06534c713ab52e79
* Don't put credentials in results from externally accessible activitiesPaul Lawrence2014-07-101-4/+9
| | | | | | | | | ConfirmLockPattern and ConfirmLockPassword return an intent that contains the password, and as such are dangerous. Create internal versions that are locked down, and don't put this info in the externally accessible versions. Bug: 13741939 Change-Id: I0df4d1e720b3c33d2c9ca086636dc54f17b19bf0
* Mode code cleaning: remove obsolete references to EXTRA_NO_HEADERSFabrice Di Meglio2014-05-131-1/+0
| | | | | | | | - the EXTRA_NO_HEADERS flag as no more meaning as we are showing the Tiles (previously named "Headers") only in the Dashboard (which is the main Settings screen) Change-Id: I55656de0d28ca9c84adbe6647d870838b4ac230b
* Allow encryption when keyguard is set to pattern or no protectionPaul Lawrence2014-04-031-0/+3
| | | | | | | | | Don't block based on keyguard type, and pass type to encryption function. Circular dependency on https://googleplex-android-review.git.corp.google.com/#/c/444200/ Bug: 13749169 Change-Id: Ica95713adca9552ae56341ff33badd1d4b748af8
* Use Drawer in Settings appFabrice Di Meglio2014-02-031-3/+2
| | | | | | | | | | | | | | | | | | | | - get rid of PreferenceActivity as much as we can and use fragments instead - add Drawer widget - add Dashboard high level entry into the Drawer (but this is work in progress and would be done in another CL) - add bypass of fragment's Header validation when launched from the Drawer but *force* validation if external call thru an Intent Be aware that WifiPickerActivity should remain for now a PreferenceActivity. It is used by SetupWizard and should not trigger running the SettingsActivity's header building code. SetupWizard is a Home during the provisionnig process and then deactivate itself as a Home but would make the Home header to appear in the Drawer (because momentarily we would have two Home). Also, verified that: - the WiFi settings still work when called from SetupWizard - when you have multiple Launchers, the Home header will appear in the list of Headers in the Drawer Change-Id: I407a5e0fdd843ad7615d3d511c416a44e3d97c90
* Whitelist fragments appropriate for an activityAmith Yamasani2013-07-301-0/+6
| | | | Change-Id: If4f8c4e9d9949b652946cffe0ebb09b587e5a042
* Announce dynamic content changes in lock confirmation settings.alanv2012-10-031-1/+4
| | | | | | | | Also re-orders updateStage() and setText/Selection calls so that text events don't flush announcements. This does not change functionality. Bug: 7256500 Change-Id: I8b10d66e9f73c7a630a8c3c5128372e18f26234c
* Bulletproof CredentialStorage state handlingBrian Carlstrom2011-06-021-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As noted by the class javadoc, CredentialStorage has seen the number of cases to cope with grow. This change tries to address those cases. src/com/android/settings/CredentialStorage.java Added ChooseLockSettingsHelper.EXTRA_KEY_PASSWORD to coordinate additional producer and consumer. constant declaration here, since its used by callers of ChooseLockSettingsHelper.launchConfirmationActivity src/com/android/settings/ChooseLockSettingsHelper.java old producer src/com/android/settings/ConfirmLockPassword.java new producer (CredentialStorage wants passwords and patterns) src/com/android/settings/ConfirmLockPattern.java new consumer src/com/android/settings/CredentialStorage.java old consumer src/com/android/settings/CryptKeeperSettings.java Made class final and removed protected from method to make it clear ChooseLockSettingsHelper is not to be used by subclassing. src/com/android/settings/ChooseLockSettingsHelper.java Change-Id: Ib2d65398fe44573168a6267a0376c3b0388b16c8
* Fix 3281395: Fix duplicate title in LockScreen Settings.Jim Miller2011-01-071-0/+7
| | | | Change-Id: I3c53d1864e521f4245b94d39664266891a728615
* Fix 3148496: Initial pass at fragmentizing lockscreen settings.Jim Miller2010-12-081-187/+210
| | | | | | | | | | This converts most of the existing activities to fragments and wraps them in PreferenceActivities so they can be launched as before (e.g. by a DevicePolicyManager) Upload after sync/rebase. Change-Id: I4f351b75d9fca0498bcb04b4e11ff3b70765a4ba
* Fix 2593312: Screen does not get stuck in locked out mode.Konstantin Lopyrev2010-05-131-0/+5
| | | | Change-Id: Ib32db339a0d6b47119da94e56a14405c5ea63eb6
* Fix 2385283: Add DevicePolicyManager calls to LockScreen.Jim Miller2010-01-201-4/+4
|