From 68c33d52bfa8aa8c36859799d649b10f0eac3d33 Mon Sep 17 00:00:00 2001 From: Alex Klyubin Date: Fri, 8 May 2015 08:44:59 -0700 Subject: [PATCH] Switch to KeyguardManager.isDeviceSecure. isKeyguardSecure also returns true when SIM PIN is required. We don't care about that because entering SIM PIN does not unlock keys requiring user authentication. isDeviceSecure returns true only if secure lock screen is set up, which is exactly what we want. Bug: 18088752 Change-Id: I47b21f3351f55c11e8e9bcfd7654762973dd9271 --- docs/html/training/articles/keystore.jd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/html/training/articles/keystore.jd b/docs/html/training/articles/keystore.jd index 217db8149aee1..fea3b2c8a7df1 100644 --- a/docs/html/training/articles/keystore.jd +++ b/docs/html/training/articles/keystore.jd @@ -129,7 +129,7 @@ of the two modes: for use as soon as the user unlocks the secure lock screen or confirms their secure lock screen credentials using the {@link android.app.KeyguardManager#createConfirmDeviceCredentialIntent(CharSequence, CharSequence) KeyguardManager.createConfirmDeviceCredentialIntent} flow. Each key specifies for how long the authorization remains valid for that key. Such keys - can only be generated or imported if the secure lock screen is enabled (see {@link android.app.KeyguardManager#isKeyguardSecure Keyguard.isKeyguardSecure}). + can only be generated or imported if the secure lock screen is enabled (see {@link android.app.KeyguardManager#isDeviceSecure()}). These keys become permanently invalidated once the secure lock screen is disabled or forcibly reset (e.g. by a Device Admin).
  • User authentication is required for every use of the key. In this mode, a specific operation