- Managing secure connections with BlackBerry UEM
- Managing work connections using profiles
- Setting up work Wi-Fi networks for devices
- Setting up work VPNs for devices
- Enabling and assigning per-app VPN settings
- Setting up proxy profiles for devices
- Using BlackBerry Secure Connect Plus for connections to work resources
- Server and device requirements for BlackBerry Secure Connect Plus
- Enable BlackBerry Secure Connect Plus
- Updating the BlackBerry Connectivity app
- Update the BlackBerry Connectivity app for Samsung Knox Workspace and Android Enterprise devices that don't have access to Google Play
- Enterprise connectivity profile settings
- Specify the DNS settings for the BlackBerry Connectivity app
- Optimize secure tunnel connections for Android devices that use BlackBerry Dynamics apps
- Troubleshooting BlackBerry Secure Connect Plus
- Using BlackBerry 2FA for secure connections to critical resources
- Setting up up automatic authentication for iOS devices
- Specify DNS servers for iOS and macOS devices
- Specify email and web domains for iOS devices
- Control network usage for apps on iOS devices
- Create a web content filter profile on iOS devices
- Create an AirPrint profile for iOS devices
- Create an AirPlay profile for iOS devices
- Create an Access Point Name profile for Android devices
- Using PKI certificates with devices or apps
- Integrating BlackBerry UEM with your organization's PKI software
- Connect BlackBerry UEM to your organization’s Entrust software
- Connect BlackBerry UEM to your organization’s Entrust IdentityGuard server to use smart credentials
- Connect BlackBerry UEM to your organization's OpenTrust software
- Connect BlackBerry UEM to a BlackBerry Dynamics PKI connector
- Connect BlackBerry UEM to your organization’s app-based PKI solution
- Providing client certificates to devices and apps
- Sending certificates to devices and apps using profiles
- Sending CA certificates to devices and apps
- Sending client certificates to devices and apps using user credential profiles
- Create a user credential profile to connect to your BlackBerry Dynamics PKI connector
- Use Intercede MyID to provide derived credentials certificates to devices
- Sending client certificates to devices and apps using SCEP
- Send the same client certificate to multiple devices
- Specify the certificate used by an app using a certificate mapping profile
- Managing client certificates for user accounts
- Integrating BlackBerry UEM with your organization's PKI software
- BlackBerry Docs
- BlackBerry UEM 12.21
- Managing secure connections
- Using PKI certificates with devices or apps
- Integrating BlackBerry UEM with your organization's PKI software
- Connect BlackBerry UEM to your organization's OpenTrust software
Connect BlackBerry UEM to your organization's OpenTrust software
BlackBerry UEM
to your organization's OpenTrust
softwareTo extend
OpenTrust
certificate-based authentication to devices, you must add a connection to your organization's OpenTrust
software. BlackBerry UEM
supports integration with OpenTrust
PKI 4.8.0 and later and OpenTrust CMS
2.0.4 and later. This connection is not supported by BlackBerry
Dynamics
apps.Contact your organization’s
OpenTrust
administrator to obtain the URL of the OpenTrust
server, the client-side certificate that contains the private key (.pfx or .p12 format), and the certificate password.- On the menu bar, clickSettings > External integration > Certificate authority.
- ClickAdd an OpenTrust connection.
- In theConnection namefield, type a name for the connection.
- In theURLfield, type the URL of theOpenTrustsoftware.
- ClickBrowse. Navigate to and select the client-side certificate thatBlackBerry UEMcan use to authenticate the connection to theOpenTrustserver.
- In theCertificate passwordfield, type the password for theOpenTrustserver certificate.
- To test the connection, clickTest connection.
- ClickSave.
- When you use theUEMconnection withOpenTrustsoftware to distribute certificates to devices, there may be a short delay before the certificates are valid. This delay might cause issues with email authentication during the device activation process. To resolve this issue, in theOpenTrustsoftware, configure theOpenTrustCA and set "Backdate Certificates (seconds)" to 180.