Knox Authentication Manager v1.7 release notes
Last updated January 8th, 2025
New
Ability to show device serial number on sign in screen
With Knox Authentication Manager v1.7, you can now display a device’s serial number on the Knox Authentication Manager sign in screen by enabling the Show device serial number policy. This helps device users to identify the device they picked up, without signing in.
Time out for failed sign-in attempts
Previously, if a user entered an incorrect PIN three times, they could return to the sign in screen and attempt to sign in again with no restrictions. With Knox Authentication Manager v1.7, if device users fail during six consecutive sign-in attempts, they are temporarily timed out and can’t attempt to sign in for a short duration of time. Additionally, the time-out duration increases with successive failed sign-in attempts.
Ability to disable device-to-device syncing
Previously, user credential data was always synced across devices. With Knox Authentication Manager v1.7, you can now disable device-to-device data syncing for non-shared devices. Set the Enable syncing policy to False to turn off device-to-device syncing.
Updates
Ability to send device logs through emails
Previously, users could send device log files to the Knox Authentication Manager team by tapping the Give feedback button on the Debug mode menu. With this release, device logs can only be shared only by email. If an email app is installed on the device, users can tap Email log file in the Knox Authentication Manager app menu and enter the recipient email(s) and message. The device log file is automatically attached to the email.
PIN and Face required for reverification
Previously, after a session timed out or if a device with the Use KAM authentication to unlock device policy set to True was locked using the power button, users with the PIN and Face authentication mode were able to reverify their sign in with just their face. With the v1.7 release, for a more secure experience, both PIN and face verification are required to sign back in to the Knox Authentication Manager app.
The Use KAM authentication to unlock device policy is not applicable to customers with Microsoft Intune with Managed Home Screen (MHS) or VMware Workspace ONE with launcher UEM configurations.
Improvements to the Knox Authentication Manager user interface
To align Knox Authentication Manager with the Samsung One UI 6 update, the v1.7 release brings updates to the user interface, including new fonts, colors, dark mode, and broad support for custom UI for tablet UIs.
Fixes for Microsoft Intune Managed Home Screen (MHS) integration
In September 2024, an update to Microsoft Managed Home Screen (MHS) introduced issues when trying to save or use credentials in the Knox Authentication Manager app. The Knox Authentication Manager v1.7 release includes fixes for these issues to enable Microsoft Intune customers to continue using Knox Authentication Manager with Microsoft MHS.
Additionally, the v1.7 release also includes an update to the Microsoft Intune sample JSON configuration file, available on the Get started as an IT admin page. Intune admins can download this file to help configure the Knox Authentication Manager for devices running the v1.7 app.
Updates to required VMware Workspace ONE activities
With Knox Authentication Manager v1.7, Omnissa Workspace ONE (previously known as VMware Workspace ONE) admins must add several new activities to the Workspace ONE console. For more information, see Update to required VMware Workspace ONE activities.
Deprecations
Notice of removal of Debug mode
Previously, users could use Debug mode to send device logs and bug reports to the Knox Authentication Manager team. The Knox Authentication Manager v1.7 release removes support for Debug mode. For more information on how to send device logs with this release, see Ability to send device logs through emails, mentioned previously.
In addition, device users could previously only view the Knox Authentication Manager policies from their app’s About screen if Debug mode was enabled by their IT Admin. With this release, all users will be able to view the app configuration policies on their device.m For more information, see View policies on device.
On this page
Is this page helpful?