BlackBerry Dynamics Entitlement ID and Version Best Practices

BlackBerry Dynamics has specific rules for GD Entitlement ID and GD Entitlement Version. Some apps do not conform to these regulations and may have issues when uploading and deploying them via the UEM servers

This Knowledge Base article provides helpful tips,  tricks, and recommended best practices when working with BlackBerry Dynamics Entitlement ID and Bundle IDs.

We hope you find it useful and enjoy using Appdome.

About GD Entitlement ID and GD Entitlement Version

Appdome is a mobile integration platform as a service (iPaaS) that allows users to add a wide variety of features, SDKs and APIs to Android and iOS apps. Using a simple ‘click to add’ user interface, Appdome allows anyone to easily implement and modify the BlackBerry Dynamics Entitlement ID and Entitlement Version to any mobile app – instantly, no code or coding required.

Using Appdome, there are no development or coding prerequisites. For example, there is no Appdome SDK, libraries, or plug-ins to implement. Likewise, there is no requirement to implement the BlackBerry Dynamics SDK  or change the application version or bundle identifier for altering the BlackBerry Dynamics Entitlement ID and Entitlement Version for Android or iOS apps. Using Appdome, mobile apps will have the BlackBerry Dynamics Entitlement ID and Entitlement Version capabilities as if they were natively coded into the app.

Prerequisites for changing an apps BlackBerry Dynamics entitlement:

In order to use Appdome’s no-code integration with BlackBerry Good SDK, you’ll need:

Every app has a bundle ID and bundle version. The app bundle ID is a string usually resembling a reverse domain like com.appdome.awesomeapp.mobile. The app bundle version is usually in a dotted segment form like 1.0.1.20.

When building an app with the BlackBerry Dynamics SDK, you are required to enter a GD App ID and GD App Version (now called the BlackBerry Dynamics Entitlement ID and BlackBerry Dynamics Entitlement Version). In some cases, the app bundle ID and version can be the same as the BlackBerry Dynamics Entitlement ID and Version, but this depends on whether the app is built in-house, or if it is an app from an Independent Software Vendor (ISV). The app you are Building on Appdome can be built with any tool such as xCode for iOS and Android Studio using any mobile development frameworks such as Xamarin, Cordova, and React Native.

These values can be edited while Building an App on Appdome under the Management tab after you select BlackBerry SDK as you EMM Service and edit the GD Entitlement ID and GD Entitlement Version:

Click Management under the Build tab.
Then, find EMM Services under the Enterprise Mobility Management heading.

  1. Enable or turn “ON” EMM Services and open the drop-down list.
  2. Next, choose BlackBerry Dynamic SDK from the drop-down list.
  3. Change the App Bundle ID (optional).
  4. Change the App Version (optional).
  5. You can use the match BB Entitlement Version and BB Entitlement ID with the application’s bundle identifier and bundle version. This will, in fact, change the application to be a different application. Some applications are not suitable for this change. For most apps this is required for touch ID authentication within the BB Dynamics SDK

BlackBerry has a great guide explaining the BlackBerry Dynamics Entitlement ID and Version here BlackBerry Dynamics SDK Dev Guide.

The GD App ID for an app must be Exclusive. If you are not the exclusive distributor of the app, you must change the app bundle-id to a unique one. Otherwise, you may encounter problems when you will try to provision the Blackberry Good policy on your secure app.

Please make sure the bundle-id you are using is unique.

For example, Cisco Jabber has an app bundle ID: com.cisco.jabberIM. When a user imports an app into BlackBerry Dynamics Good Control or UEM, the BlackBerry Entitlement ID for an app must be unique in the world. Appdome lets you change the GD App ID (BlackBerry Entitlement ID) while Building before uploading the app to Good Control or UEM. This will ensure there are no conflicts.

For example, when Building the Cisco Jabber app, a new GD App ID was entered to ensure it is unique in the world. In this case com.appdome.jabberim is used as shown below (1). The GD App ID is just a name to identify the app in Good Control or UEM, so you can use any name you like. By using the reverse domain prefix com.appdome in this example, this app should not conflict with apps uploaded by any other organization or company. That is, no other company should be using com.appdome.

Note, the GD App ID must be below 32 characters, it cannot have uppercase letters, and it cannot have special characters. Appdome will automatically correct uppercase letters to lowercase if uppercase letters are entered for the BlackBerry Dynamics Entitlement ID.  

Optionally you can change the GD App Version (BlackBerry Dynamics Entitlement Version).
The GD App Version may contain only digits and dots. It can have 4 or less segments of 4 or less numbers separated by dots.  Leading zeros are not allowed.

Allowed: 1.22.3.333 or 10.22.0.233 or 1.2323.4321.23

Not allowed: 1.02.3.33 or 10.22(mdm).1.2 or 1.2.3.4.5

Note: You cannot use letters and you must use numeric digits.

For more information on Appdome for BlackBerry please visit this resource.

To zoom out on this topic, visit  Appdome for Enterprise Mobility on our website.

How Do I Learn More?

Appdome provides additional alternatives for No Code Microsoft Authentication in Mobile Apps.  Appdome also has other no code implementations for MicroVPN and enterprise mobility, all of which can be combined with Modern Authentication on Appdome.

Thank you!

Thanks for visiting Appdome! Our mission is to make mobile integration easy. We hope we’re living up to the mission with your project. If you don’t already have an account, you can sign up for free.

Paul Levasseur

Have a question?

Ask an expert

GilMaking your security project a success!