Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge \\"docs: Updating N Preview \\"behavior changes\\" doc for DP5\\" into nyc-dev am: 9d3bc86207

Browse Source 
am: 72022a691a

Change-Id: I4c85652bbc4d67507c419b5362341e993f932866
This commit is contained in:
Andrew Solovay
2016-07-16 00:41:33 +00:00
committed by android-build-merger
parent f00bbba326 72022a691a
commit 45368cd044
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/html/preview/behavior-changes.jd
View File

@@ -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.
</li>
<li>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
<strong>Settings &gt; Security &gt; Work profile security</strong>.
</li>
<li>A new encryption status <code>ENCRYPTION_STATUS_ACTIVE_PER_USER</code> is
returned by <code>DevicePolicyManager.getStorageEncryptionStatus()</code>, 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, <code>ENCRYPTION_STATUS_ACTIVE</code>
is returned, even if the encryption key is specific to the user or profile.
</li>
</ul>
<p>