- 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 Face ID
- Support for certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- Requirements
- BlackBerry Dynamics software versions
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Requirements: Frameworks and libraries
- Requirement: URL scheme
- Required build-time declarations: URL type
- Using NSURLSystem for KCD
- GDAssets.bundle required in build phase
- Compatibility with the BlackBerry Dynamics Launcher Library
- App UI restrictions
- Supported and unsupported features on iOS
- Link for FIPS in Objective-C or C++
- Steps to get started with the BlackBerry Dynamics SDK
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps in Objective-C
- BlackBerry Dynamics and the Swift programming language
- Testing and troubleshooting
- Readying your app for deployment: server setup
- Details of support for client certificates
Support for certificates
Type | Description |
|---|---|
PKI certificates | BlackBerry
Dynamics supports many popular uses of client-side Public Key Infrastructure (PKI) certificates to secure apps and communications:
For more information, see Details of support for client certificates. |
SCEP | BlackBerry UEM version 12.10 and later support certificate enrollment using SCEP with Entrust and Microsoft NDES for BlackBerry
Dynamics apps. Administrators can configure and assign a SCEP profile for BlackBerry
Dynamics apps in the UEM management console.For more information, see “SCEP profile settings” in the UEM Administration Guide. |