Call this function to initiate SDK authorization processing.

Authorization involves a number of exchanges with various servers in the BlackBerry Dynamics proxy infrastructure, and may involve user interaction. The following processing items are the most significant.

Infrastructure activation

The BlackBerry Dynamics Runtime registers the device as a terminal with the BlackBerry Limited Network Operation Center (NOC). The NOC issues registration credentials, which are encrypted and stored on the device. Infrastructure activation is not processed if registration credentials are already present.

Enterprise activation

Enterprise activation is the completion of the Enterprise Provisioning process, which begins on the enterprise's BlackBerry management console. During enterprise provisioning, an activation key will have been made available to the end user, either by email or in the BlackBerry management console self-service interface. During enterprise activation, the user enters the activation key, in a BlackBerry Dynamics Runtime user interface. The runtime then sends the key to the NOC. If the key is recognized, the device is registered as being associated with the provisioning enterprise. Enterprise registration credentials are then issued, encrypted and stored on the device.

Enterprise activation is not processed if enterprise registration credentials are already present.

Note that successful enterprise activation has the effect of consuming the activation key. This will be the case even if a later stage of authorization processing fails, or if the user is found to be not entitled to this application.

Entitlement checking

The enterprise that provisioned the end user can later withdraw the user's entitlement to the application. Withdrawal is flagged in the enterprise's BlackBerry management console. The BlackBerry Dynamics Runtime checks the end user's ongoing entitlement to the application every time authorization is processed. In addition, withdrawal may be notified to the runtime by the BlackBerry Dynamics NOC.

In the BlackBerry Dynamics management console, entitlement is given to particular versions of particular applications. The version and BlackBerry Dynamics Entitlement ID values must match exactly with a version and BlackBerry Dynamics Entitlement ID to which the user has been given entitlement in the the BlackBerry Dynamics management console. If there is not an exact match, then user entitlement is assumed to have been withdrawn.

If the user is found not to be entitled, then the BlackBerry Dynamics container will be wiped of all application data and authentication credentials.

Policy update

Policies govern many aspects of the BlackBerry Dynamics user experience. For example, the minimum characteristics of the end user's security password with respect to length and types of character are governed by a BlackBerry Dynamics policy. So is the need for the end user to set a security password. The BlackBerry Dynamics Runtime checks for and retrieves updated policies every time authorization is processed.

Policy checking

The BlackBerry Dynamics Runtime checks for compliance with the most up-to-date policies every time authorization is processed.

Configuration retrieval

The BlackBerry Dynamics Runtime retrieves a set of application configuration settings from the enterprise BlackBerry management console during authorization processing. These will have been entered in the BlackBerry management console console. See under GetApplicationConfig for a list of settings.

Unlock secure store

The BlackBerry Dynamics secure store is unlocked during authorization. If the store is protected by an end-user password, then the user must enter their password for authorization processing to complete. Password entry is a BlackBerry Dynamics Runtime user interface.

Note that BlackBerry Dynamics Runtime user interfaces, such as Enterprise activation and Password entry, are opened and closed as needed, without reference to the application.

This function must be called before any of the principal BlackBerry Dynamics API functions.

Authorization is asynchronous. When authorization processing completes, the GDAppEvent is sent using HandleGDMessage.

For instructions on how to set up applications and users for development purposes, see BlackBerry management console overview for application developers and Enterprise Simulation mode mode below.

Reference