Skip Navigation

Considerations for changing
BlackBerry Dynamics
certificates

If you want to change any of the
BlackBerry Dynamics
SSL certificates, keep the following considerations in mind. If problems occur when you change a certificate, communication between
BlackBerry UEM
components and between
BlackBerry UEM
and
BlackBerry Dynamics
apps could be disrupted. Plan and test certificate changes carefully.

Add new certificates to any peripheral equipment

If you have added any
BlackBerry Dynamics
certificates to peripheral equipment on your network, add the new certificate to peripheral equipment before adding it to
BlackBerry UEM

Update
BlackBerry Dynamics
apps

If you are replacing the
BlackBerry Dynamics
certificate for application management or
Direct Connect
, ensure that users'
BlackBerry Dynamics
apps are updated to the most recent versions before you replace the certificate.
Any
BlackBerry Dynamics
apps developed by your organization must be built with version 3.2 or later of the
BlackBerry Dynamics
SDK. Older apps can't receive the new certificate from
BlackBerry UEM
.

BlackBerry Dynamics
apps must be open to receive a certificate

Users must open a
BlackBerry Dynamics
app for the app to receive a certificate from
BlackBerry UEM
. If you are replacing the
BlackBerry Dynamics
certificate for application management or
Direct Connect
and the change becomes effective before
BlackBerry UEM
pushes the certificate to all
BlackBerry Dynamics
apps, any apps that did not receive the certificate must be reactivated. Apps do not receive certificates while they are suspended on
iOS
devices or while
Android
devices are in Doze mode.

Ensure the
BlackBerry Connectivity Node
is accessible

If any
BlackBerry Proxy
instances are unreachable by
BlackBerry UEM
when
BlackBerry Dynamics
certificates are replaced,
BlackBerry Dynamics
apps will not be able to connect to those instances following the certificate replacement.

Schedule certificate changes appropriately

If you are replacing the certificate for
BlackBerry Dynamics
servers, choose a period of low activity to restart the servers.
Allow sufficient time for new certificates to propagate to
BlackBerry Proxy
and
BlackBerry Dynamics
apps. If you are replacing only the certificate for
BlackBerry Dynamics
servers, allow at least 10 minutes before the server restarts.
If you are replacing the
BlackBerry Dynamics
certificate for application management or
Direct Connect
, it is recommended that the time until the effective date be longer than the Connectivity verification "Last contact time" setting in the compliance profile.
If you are replacing both the
BlackBerry Dynamics
certificates for application management and
Direct Connect
, set the effective times at least 30 minutes apart. If you have a large number of users and
BlackBerry Dynamics
apps, you should wait longer than 30 minutes between each certificate.