I'm trying to activate an internal developed app to iOS device via BES12. However the activation seems only work with Easy Activation (acticated with email address and access key generated in BES12). Our goal is to use delegation authentication instead of easy activation approach. We've been using UEM Client as DA in our environment, and it's working fine on other Blackberry apps such as Word, Access, Task etc. But we are really having a hard time to get the delegation authentication working on our internal developed app.
I've read another post in this forum
which mentioned about bundle ID etc should have something to do with the DA. So i reckon it has something to do with the configuration in the plist. here is some properties in our plist, can someone give me a hint on what might be wrong?
BundleIdentifier: $(PRODUCT_BUNDLE_IDENTIFIER). <- which points to something like "Company-Name.App-Name"
i tried using GPApplicationID as the BundleIdentifier, but then the app couldn't be built in xcode.
Anyone has idea what i'm mssing?
In order to use Easy Activation and Authentication Delegation, the application's native identifiers (Bundle ID on iOS and Package Name on Android) must be configured in BlackBerry UEM. To do so, select Apps on the left side menu in BlackBerry UEM and then click on your app. Navigate to the iOS tab and populate the Bundle ID, and on the Android tab enter the Package Name (if you also have an Android variant of the app).
Once that is populated you should be able to use Easy Activation and Authentication Delegation.
Note that the GDApplicationID and Bundle ID do not have to be the same.