Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry UEM 12.19
  3. UEM Overview and Architecture
  4. Data flows: Activating devices and BlackBerry Dynamics apps
  5. Data flow: Activating a BlackBerry Dynamics app when one is already activated on the device

Data flow: Activating a
BlackBerry Dynamics
 app when one is already activated on the device

This data flow describes how data travels when a
BlackBerry Dynamics
 app is activated on a device and the
BlackBerry UEM Client
 or another
BlackBerry Dynamics
 app is already activated and acts as an easy activation delegate.
Diagram showing the steps and components mentioned in the following data flow.
  1. An administrator assigns one or more
    BlackBerry Dynamics
     apps to a user.
  2. The user installs the app on the device.
  3. The app performs the following actions:
    1. Queries the
      BlackBerry Dynamics NOC
       and identifies another app that is activated on the device
    2. Requests the activation credentials from the previously activated app
  4. The user approves the activation request from the previously activated app on the device.
  5. The previously activated app sends the credentials to
    BlackBerry UEM
    .
  6. BlackBerry UEM
     sends the credentials request and
    BlackBerry UEM
     URL to the existing app.
  7. The previously activated app returns the credentials and the URL to the new app.
  8. The new app completes the following actions:
    1. Activates with the
      BlackBerry Dynamics NOC
    2. Connects to
      BlackBerry UEM
       through the
      BlackBerry Infrastructure
       and establishes an end-to-end encrypted session with
      BlackBerry UEM
       using the EC-SPEKE protocol.
      This session can only be decrypted by the
      BlackBerry UEM
       instance that issued the activation credentials.
    3. Sends the activation request through the secured session
  9. BlackBerry UEM
     verifies the activation request and sends encrypted activation response to the app. The activation response includes data required by the app to communicate with
    BlackBerry UEM
    , including a client certificate, master session key, list of
    BlackBerry Proxy
     instances, and trusted certificate authorities.