- About this guide
- BlackBerry Dynamics background
- BlackBerry Dynamics API reference
- FIPS 140-2 compliance
- Easy Activation
- Securing cut-copy-paste on devices (Data Leakage Prevention, or DLP)
- Shared Services Framework
- Support for fingerprint authentication
- Support for certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- BlackBerry Dynamics software versions
- Requirements
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Supported launchModes
- Compatibility with the BlackBerry Dynamics Launcher Library
- Supported CPU architectures
- Supported and unsupported Android and third-party features
- FIPS-linking on Android: automatic
- Restricted key prefix
- Steps to get started with the BlackBerry Dynamics SDK
- Installing the BlackBerry Dynamics SDK for Android
- Integrating the BlackBerry Dynamics SDK in .aar format
- Using the branding API to add a custom logo and colors
- Info: Add Samsung Pass to your BlackBerry Dynamics app
- Info: APIs for secure clipboard management
- Info: Preventing autobackup to Google Drive
- Info: APIs for network status
- BlackBerry Dynamics SDK for Android: Wearable Framework
- Implementing SafetyNet attestation for BlackBerry Dynamics apps
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps
- Testing and troubleshooting
- Implementing automated testing for BlackBerry Dynamics apps
- Automated testing with the BlackBerry Dynamics sample apps
- Preparing for automated testing
- Components of a sample automated testing configuration
- Execute all tests from the command line with Gradle
- Execute specific tests from the command line with Gradle
- Execute tests from the Android Studio IDE
- Add automated testing to your BlackBerry Dynamics Android app
- Disable compliance settings that check for a compromised OS
- Emulators and the rooted OS compliance policy
- Using enterprise simulation mode
- Logging and diagnostics
- Implementing automated testing for BlackBerry Dynamics apps
- Readying your app for deployment: server setup
- Details of support for client certificates
Completing SafetyNet registration
SafetyNet
registrationYou must obtain an API key from Google and add it to the app’s AndroidManifest.xml file. The API key has a quota limit of 10,000 requests each day. If necessary, you can use this online form to request an increase to this quota.
For the following sections of the form, select these answers:
- Method of validating SafetyNet Attestation API responses: Server side - by verifying the signing certificate chain.
- Method of retrying in case of errors: Something else (or unknown). In the “Anything else that you want to tell us” field, type the following: If the SafetyNet Service responds to the device with a transient error, then the device will retry with an exponential back-off. If the SafetyNet Service responds with a valid blob, but the blob is found to contain an error value when it is decoded, then attestation is retried after 15 minutes.
In the AndroidManifest.xml file, add the following to the <application> element:
<meta-data android:name="com.blackberry.attestation.ApiKey" android:value="YOUR_API_KEY" />