From 469f8a5c807a2b9e457444eec8970fcedd109b12 Mon Sep 17 00:00:00 2001 From: Andrew Solovay Date: Thu, 14 Jul 2016 19:08:11 -0700 Subject: docs: Updating N Preview "behavior changes" doc for DP5 See first comment for doc stage location. Change-Id: I11720bdabca78fdbaca82c7e3467f47b51e60f15 --- docs/html/preview/behavior-changes.jd | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'docs') diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd index 3a3729534462..48dc053116f6 100644 --- a/docs/html/preview/behavior-changes.jd +++ b/docs/html/preview/behavior-changes.jd @@ -748,6 +748,23 @@ JavaVM::AttachCurrentThread from <jni.h>. to the trusted credentials storage via Settings UI separately, with a DER-encoded format under a .crt or .cer file extension. + +
  • Starting in Android N, fingerprint enrollment and storage are managed per user. + If a profile owner’s Device Policy Client (DPC) targets pre-N on an N device, + the user is still able to set fingerprint on the device, but work + applications cannot access device fingerprint. When the DPC targets N and + above, the user can set fingerprint specifically for work profile by going to + Settings > Security > Work profile security. +
    • + +
  • A new encryption status ENCRYPTION_STATUS_ACTIVE_PER_USER is + returned by DevicePolicyManager.getStorageEncryptionStatus(), to + indicate that encryption is active and the encryption key is tied to the + user. The new status is only returned if DPC targets API Level 24 and above. + For apps targeting earlier API levels, ENCRYPTION_STATUS_ACTIVE + is returned, even if the encryption key is specific to the user or profile. +
    • +

    -- cgit v1.2.3-59-g8ed1b