- Basics
- The Knox Ecosystem
- White Paper
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- For IT admins
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Knox Configure
- Mobile
- Wearables
- Shared Device
- FAQ
- KBAs
- Knox Capture
- Introduction
- How it works
- How-to videos
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Video: Getting started with Knox Manage
- Integration with Managed Service Provider
- Access Knox Manage
- Configure basic environments
- Create user accounts
- Create groups
- Create organization
- Set up devices and profiles
- Set up Knox Manage deployment with a Knox Suite license
- Manage Chromebooks
- Manage Android devices with the Android Management API
- Manage Shared iPads
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQ
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox E-FOTA On-Premises
- Legacy Knox E-FOTA products
- Knox Guard
- Introduction
- How-to video
- Get started
- Using Knox Guard
- Dashboard
- Manage devices
- Device management
- Accept or reject devices
- Upload devices
- Delete devices
- Complete device management
- Send notifications
- Enable or disable SIM control
- Download devices as CSV
- View device log
- View device deletion log
- Start and stop blinking reminder
- Lock and unlock devices
- Update lock message
- Send relock timestamp
- Turn on/off relock reminder
- Manage policies
- Manage licenses
- Manage resellers
- Manage admins and roles
- Activity log
- Knox Deployment App
- Release notes
- FAQ
- KBAs
- Support
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
Password compliance check returning the wrong result on device
Environment
- Knox Platform for Enterprise (KPE)
- Full-disk encryption (FDE)-based devices
Overview
You may encounter an issue where your managed devices perform a password compliance check and return the wrong result, causing them to be quarantined.
Cause
This is a known issue impacting only FDE-based devices. If the password requirements are changed after the device is booted up, the current password will no longer meet the requirements. Due to changes introduced in Android P, the API that checks if the active password is sufficient may return an incorrect value before the password is entered on a device for the first time.
isActivePasswordSufficient() will only return the last known state of password sufficiency. If the password requirement is changed before the user unlocks the device for the first time, the value returned by isActivePasswordSufficient() will not reflect the new password requirement until the user locks and unlocks the device.
Resolution
This behavior is by design. To avoid compromising your potentially sensitive data, the full set of active password metrics is not stored on your device.
Workaround
For IT admins:
Please consult with your UEM provider for further information on how they have implemented the password sufficiency policy.
For UEMs:
To handle this password compliance issue, the Device Policy Manager (DPM) can take one of three actions:
- Postpone updating the password requirement until the user locks and unlocks the phone for the first time.
- Skip updating altogether if the password requirement will not change.
- Simply disregard the value of isActivePasswordSufficient() during the window of time when the password requirement is being modified.
Additional Information
For a detailed breakdown of what code changes were made in AOSP to address this issue, head to the Android Git repository.
To learn more about FDE and FBE, see Full-disk encryption (FDE) and file-based encryption (FBE).