- 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
- BlackBerry Docs
- BlackBerry Dynamics SDK for iOS 5.0
- BlackBerry Dynamics SDK For iOS Development Guide
- Details of support for client certificates
- Client certificate sharing among BlackBerry Dynamics-based applications
Client certificate sharing among BlackBerry
Dynamics-based
applications
BlackBerry
Dynamics
-based
applicationsThe
BlackBerry Dynamics SDK
supports the "sharing" of a single client
certificate among all BlackBerry
Dynamics
-based applications for an end-user. If the security policy for authentication via client certificates is enabled in
Good Control or UEM and one or more client certificates have been uploaded to the server, those
certificates are used for user authentication by all
BlackBerry
Dynamics
-based applications on
the user's device.- No programming is required.
- Client certificates must be enabled in Good Control or UEM and at least one PKCS 12 certificate for a user must be uploaded to server.