Support for the "Do not require password" setting
The
BlackBerry Dynamics Runtime
supports the "Do not require password" setting in a BlackBerry
Dynamics
profile in UEM
or in a security
policy in standalone Good Control
. When this setting is enabled by an administrator, users cannot set a password for a BlackBerry
Dynamics
app or BlackBerry
Dynamics
container. Note that
this setting does not apply to the device password.This setting is available in
BlackBerry UEM
12.7
or later and standalone Good Control
3.0.50.70 or later.Security considerations
- Consider the security impact to your organization's environment before an administrator enables this setting. If enabling this feature does not meet security standards, consider other options, including authentication delegation or assigning the profile to specific users or groups that are already assigned device management profiles or other controls.
- Do not enable the "Do not require password" setting and authentication delegation in the same policy set.
- When the "Do not require password" setting is enabled, authentication can be accomplished only through user interaction or autonomously. For more information, see "canAuthorizeAutonomously" in the SDK programming reference for iOS or Android.
User experience when the rule is enabled or disabled
If a
BlackBerry
Dynamics
app requires a password and the administrator enables the "Do
not require password" setting, the next time the user opens the app, the app displays a
message that a password is no longer required. As long as the feature is enabled, the user
is not prompted for a password.If the administrator disables the "Do not require password" setting, the
next time the user opens the app, the app displays a message that a password is required.
The user is prompted to specify a password.
Android: Optional APIs for the "Do not require password" policy rule
Android
: Optional APIs for the "Do not require password" policy ruleYou can call the
GDAndroid.getInstance().canAuthorizeAutonomously()
method to determine whether this
feature is enabled for a BlackBerry
Dynamics
app.Call
GDAndroid.serviceInit()
to start the
authorization process when the app has received a GCM message or background broadcast/explicit
intent.The GDInteraction sample app illustrates the use of these methods.
For syntax and details, see the SDK programming reference.