BlackBerry Dynamics SDK for

iOS

Development Guide

10.1

2023-06-13Z

||2

Contents

What is the BlackBerry Dynamics SDK?............................................................ 6

BlackBerry DynamicsAPI reference..................................................................................................................... 6

User authentication...................................................................................................................................10

Administrative controls............................................................................................................................ 12

Advanced security features with BlackBerry Protect Mobile................................................................ 12

Data collection and metrics withBlackBerry Analytics......................................................................... 12

Dynamic security response withBlackBerry Persona............................................................................13

Requirements and support for platform-specific features............................... 14

Software requirements.........................................................................................................................................14

Using an entitlement ID and version to uniquely identify a BlackBerry Dynamics app................................... 16

Relationship between the entitlement ID and version and native identifiers........................................17

FIPS compliance...................................................................................................................................................17

Support for Face ID.................................................................................................................................. 20

Support for WKWebView..........................................................................................................................20

Support for SFSafariViewController........................................................................................................ 24

Support for the Apple Universal Clipboard............................................................................................. 25

Unsupported iOS features........................................................................................................................ 25

Supported TLS protocols and cipher suites...................................................................................................... 25

Steps to get started with the BlackBerry Dynamics SDK..................................26

Using the BlackBerry Dynamics SDK dynamic framework............................................................................... 26

Prepare an existing BlackBerry Dynamics app to use the dynamic framework...................................26

Configure a new or existing BlackBerry Dynamics app to use the dynamic framework......................27

||iii

Preventing password autofill in the app UI........................................................................................................35

Enforcing local compliance actions................................................................................................................... 35

Adding custom policies for your app to the UEM management console........................................................ 35

Add a watermark to the screens in a BlackBerry Dynamics app..................................................................... 36

Allow unencrypted data to be copied to the pasteboard..................................................................................37

Replace the default splash screen for inactive apps........................................................................................ 37

Prompt the user to update a BlackBerry Dynamics app...................................................................................38

Adding a custom logo and colorswith the branding API.................................................................................40

Using zero sign-on for SaaS services throughBlackBerry Enterprise Identity................................................ 40

Integrating BlackBerry Enterprise Mobility Server services.............................................................................. 40

Sample apps in Objective-C............................................................................ 47

Testing and troubleshooting........................................................................... 49

Implementing automated testing for BlackBerry Dynamics apps....................................................................49

Automated testing with theBlackBerry Dynamicssample apps.......................................................... 49

Preparing for automated testing............................................................................................................. 50

Components of a sample automated testing configuration................................................................. 51

Execute tests from the command line withXcodetools...................................................................... 51

Execute tests from theXcodeIDE.......................................................................................................... 53

Add automated testing to your BlackBerry Dynamics iOS app.............................................................53

Configure compliance settings so you can debug your app............................................................................ 53

Testing connectivity to application servers and diagnostic functions................................................. 57

Deploying your BlackBerry Dynamics app....................................................... 58

Configuring library version compliance..............................................................................................................58

Instructing users to trust the signing certificate............................................................................................... 59

Deploying certificates to BlackBerry Dynamics apps....................................... 60

Using Personal Information Exchange files.......................................................................................................60

Configuring support for client certificates..............................................................................................61

Certificate requirements...........................................................................................................................61

Using Kerberos..................................................................................................................................................... 62

||iv

Legal notice.................................................................................................... 63

||v

valuable services, including secure communication, securing data in file systems and databases, inter-app data

exchange, presence, push, directory lookup, single sign-on authentication, identity and access management, and

more.

This guide will provide:

• Information about supported features

• Development requirements and prerequisites

• Instructions for installing, configuring, and using the SDK

• Considerations for key platform features

• Information about the sample apps provided with the SDK

• Testing and troubleshooting guidance

resources/api-reference.html.

Key features of the BlackBerry Dynamics SDK

This section provides more information about key features of the BlackBerry Dynamics SDK. It does not detail the

complete feature set. For more information about the full list of supported features and APIs, see the BlackBerry

Dynamics SDK API reference for your platform.

For more information about the requirements and prerequisites to support platform-specific features, see

Requirements and support for platform-specific features.

The implementation of some of the features discussed in this section will depend on how the UEM administrator

has configured your organization’s servers, network, and other infrastructure components. Contact the

administrator to clarify whether there are components of a feature that are configured or managed using the

authorized and permitted to use the app.

|What is the BlackBerry Dynamics SDK?|6

Users can activate a BlackBerry Dynamics app manually using an activation password, QR code, or access key

provided by the administrator or obtained from UEM Self-Service, by using the UEM Client, or by using the Easy

Activation feature described below.

For more information about activating BlackBerry Dynamics apps, see the Activation section in the GDAndroid

class reference or GDiOS class reference and Managing BlackBerry Dynamics apps in theUEM Administration

content.

Easy Activation simplifies the process of activating multiple BlackBerry Dynamics apps on a user’s device. With

Easy Activation, a device user only needs to activate the first BlackBerry Dynamics app on their device; when the

user installs additional BlackBerry Dynamics apps, the user can choose to delegate the activation process to the

previously activated app. Any BlackBerry Dynamics app can be an activation delegate, but priority is given to the

app that is configured as the authentication delegate.

Easy Activation is automatically enabled for all BlackBerry Dynamics apps that are produced by BlackBerry.To

For more information, see the Easy Activation section in the BlackBerry Dynamics Security White Paper.

The BlackBerry Dynamics SDK for iOS version 8.0 and later and UEM version 12.13 and later feature the following

activation enhancements for iOS user enrollment and DEP:

• MDM enrollment and the activation of BlackBerry Dynamics apps doesn’t require the UEM Client.

• After a new device is enrolled on UEM, UEM prompts the user to install the BlackBerry Dynamics app that is

configured as the authentication delegate(that app must be assigned to the user). When the user opens this

app for the first time, it activates automatically. The user can then activate additional BlackBerry Dynamics

apps using Easy Activation.

|What is the BlackBerry Dynamics SDK?|7

short period.

|What is the BlackBerry Dynamics SDK?|8

The provider can bea client-side service, which is a BlackBerry Dynamics app that uses the GDService

APIs(Android/iOS), or aserver-side service that is provided by an application server or other remote system. The

service is consumed by a BlackBerry Dynamics app that communicates with the provider using AppKinetics (a

proprietary BlackBerry ICC protocol) for client-side services or a protocol such as HTTPS for server-side services.

The typical steps that are required to consume a service:

1. Service discovery: The BlackBerry Dynamics app (the consumer) queries for service providers using the

GDAndroid.getServiceProvidersFor API or the GDiOS.getServiceProvidersFor API. Service discovery is

optionalbut recommended for both types of services because it respects user entitlements and permissions.

|What is the BlackBerry Dynamics SDK?|9

BlackBerry Dynamics Launcher

Library

• Identification

• If you are not using a default xcconfigfile, create one nameddefault.xcconfigand configure your build options

to use it.

"invalidarchname'-

archarmv7s'"linker error

when building fromXcode

Declaring a URL type to support BlackBerry Dynamics features

A BlackBerry Dynamics app for iOS devicesmust declare a URL type so that it can be discovered by other apps on

the same device. This enables AppKinetics, which is required for many BlackBerry Dynamics features.The URL

type and schemes are declared in theapp's Info.plist file.

The URL type must be the same as the app's native bundle ID. Within the URL type declaration, the following URL

and the schema declarations are as follows:

App UI restrictions

The BlackBerry Dynamics Runtime monitors the app UI to enforce the configuration of enterprise profiles or

policies from BlackBerry UEM. For example, a BlackBerry Dynamics profilemay require the user to enter a

password when the app transitions from the background to the foreground, or it may lock the app UI after a

certain period of inactivity.

This section provides specific requirements or considerations to support features of theiOSplatform in

yourBlackBerry Dynamicsapps.

Touch ID is a fingerprint recognition system for some iOS devices.

Touch ID can be allowed for user authentication in BlackBerry Dynamics apps in addition to standard password

authentication. For more information about Touch ID, see BlackBerry Dynamics and Fingerprint Authentication in

the BlackBerry Developers for Enterprise Apps portal.

disable the feature in a BlackBerry Dynamics profile.

Each app must add the NSFaceIDUsageDescription key to the Info.plist file. For more details about Face ID, see

the Build-Time Configuration appendix in the API Reference.

Support for WKWebView

The BlackBerry Dynamics SDK for iOS version 4.2 and later supports secure WKWebView for displaying interactive

web content.

Note the following support details:

• The SDK supports multiple WKWebView instances. The instances must be created programmatically.

• The SDK supports loading WKWebView from UIStoryBoard. To avoid any possible data leaks, you must

loadUIStoryBoard with the WKWebView componentafter the SDK is initialized.

• The supported versions of iOS require JavaScript injection by the BlackBerry Dynamics Runtime.

• The secure Fetch API is supported.

• Redirection

• Basic, Digest, NTLM, Kerberos, and ClientCertificate authentication

• Cookies

• Video and audio playback

• Asynchronous XHR requests

• HTML5 non-persistent local storage

• Sending the following types of body data using XMLHttpRequest: ArrayBuffer, Blob, FormData,

URLSearchParams, USVString

• The JavaScript sendBeacon API

• The following Data Leakage Prevention (DLP) settings from BlackBerry UEM for long-press or 3D touch

• Do not allow copying data from BlackBerry Dynamics apps into non BlackBerry Dynamics apps

• WebRTC

• HTTP/2

WKContentWorld.pageWorld:.

WKDownload is new in iOS 14.5 and is not yet supported by the SDK.If a developer attempts to use WKDownload

via a 3rd party framework,the console will produce the following error messages:

webView(_:authenticationChallenge:shouldAllowDeprecatedTLS:) This method is new in iOS 14 and

WKPDFConfiguration is new in iOS 14 and is not yet supported by the SDK.

addScriptMessageHandler:contentWorld:name: This method is new in iOS 14.The SDK supports only

WKContentWorld.pageWorld.

addScriptMessageHandlerWithReply:

contentWorld:name:

This method is new in iOS 14.The SDK supports only

removeScriptMessageHandlerForName:contentWorld:.

removeAllScriptMessageHandlers New in iOS 14.You should remove

the handler by name using

removeScriptMessageHandlerForName:contentWorld:.

evaluateJavaScript:inFrame:inContentWorld:

completionHandler:

This method isnew in iOS 14. The SDK

supports only WKContentWorld.pageWorld.

callAsyncJavaScript:arguments:inFrame:inContentWorld:

This method isnew in iOS 14. The SDK

through the network, use NSURLSession.

createWebArchiveDataWithCompletionHandler: After calling this function, the user gets

NSData in the completion handler. To

store data in the secure container, use

GDFileManager.To securely send data

through the network, use NSURLSession.

findString:withConfiguration:completionHandler: This method is new in iOS 14 and is not yet

supported by the SDK.

loadFileURL(_:allowingReadAccessTo:) Files can be loaded from a bundle or from the

encrypted, secured container that is protected

supported by the SDK.

printOperationWithPrintInfo: This method is for macOS only and is not

currently supported by the SDK.

resumeDownloadFromResumeData:completionHandler: This method is new in iOS 14.5 and is not

supported by the SDK.The SDK generates a

warning when it is called.

serverTrust The SDK returns nil for this property.

startDownloadUsingRequest:completionHandler: This method is new in iOS 14.5 and is not

supported by the SDK.The SDK generates a

warning when it is called.

supported by the SDK.

shouldPerformDownload This property is new in iOS 14.5 and is not supported

by the SDK.

WKNavigationActionPolicyDownload This enumeration case is new in iOS 14.5 and is not

supported by the SDK.

WKNavigationResponsePolicyDownload This enumeration case is new in iOS 14.5 and is not

Note the following support details:

|Steps to get started with the BlackBerry Dynamics SDK|32

|Steps to get started with the BlackBerry Dynamics SDK|33

|Steps to get started with the BlackBerry Dynamics SDK|34

Password autofill is aniOSfeature that automatically provides suggestions for a user’s password or other privacy

data in an app. This feature does not satisfy the security standards of theBlackBerry Dynamicsplatform and can

but it does not block the feature in the app UI.BlackBerryprovides an open source sample onGitHubthat

For instructions for uploading the file to the management console, see Manage settings for a BlackBerry

This watermark deters users from taking photos of potentially sensitive information, while also giving your

organization a means to trace the source of a data leak.

blackberry.security.EnableDLPWatermark and the default value should be false.

3. Include the DLP watermark policy setting in the structural section of the file. The pview elements must not

include a key attribute.

4. Coordinate with the UEM administrator to upload the app policy for your app in UEM. See Manage settings for

The BlackBerry Dynamics platform offers comprehensive data leakage prevention controls, but in certain cases

you may want to allow an app to copy unencrypted data to the pasteboard so that it can be consumed by another

non-BlackBerry Dynamics app.

the GDNativePasteboardAccess class reference for details about the client-side implementation.

1. Create a BlackBerry Dynamics app policy definition file for your app.For implementation details and more

2. Add a setting definition for the Native Pasteboard Access policy. The name of the key must be

blackberry.security.EnableNativePasteboardAcess and the default value should be false.

Example:

Example:

• Replace the splash screen at build-time: In your app’s plist file, add a value using the key

UILaunchStoryboardName. The BlackBerry Dynamics Runtime will try to instantiate a splash screen from the

storyboard with this name. By default, the name in Xcode will be LaunchScreen.

• Replace the splash screen at runtime: Customize the splash screen during the life-cycle of

the app (for example, to handle the user experience for specific system events) by using the

classGDSplashScreenCustomizer.hand its associated delegate. This class allows you to replace the splash

screen with a custom view controller.Follow the instructions below to create anapp specific policy so the

UEM administrator can enable or disable the custom splash screen.

information about the file format and elements, see the Application Policies Definition appendix in the API

Reference and the BlackBerry Dynamics App Policies Technical Brief.

BD_SDK_AllowCustomSplashScreen.The default value should be false.

Example:

3. Include the custom splash screen policy setting in the structural section of the file.

Example:

4. Coordinate with the UEM administrator to upload the app policy for your app in UEM. See Manage settings for

a BlackBerry Dynamics apps (App configuration > Upload a template). The administrator can now enable the

custom splash screen feature.

todetect whether the user should upgrade to the latest available version. The BlackBerry Dynamics Runtime

provides a notification using the ThreatStatus interface only if the user is running an older version of the app.

To implement this feature, you must use BlackBerry Dynamics SDK version 8.0 or later, and you must implement a

BlackBerry Dynamics application policy in UEM. Note that the UEM administrator cannot view or change the policy

configuration. The minimum required version and the app download URL are configured using hidden fields in the

application policy.

The ThreatApplicationSecurity(Android/iOS)class inthe ThreatStatusAPI(Android/iOS)providesawarning.

TheisAppVersionOutOfDate()method(Android/iOS)indicates if the current version of the app that is installed

on the device is lower than the minimum required version. A string with the URL to download the latest version is

returned usinggetAppUpdateURL()(Android/iOS).

1. Create a BlackBerry Dynamics app policy definition file for your app.For implementation details and more

information about the file format and elements, see the Application Policies Definition appendix in the API

Referenceand the BlackBerry Dynamics App Policies Technical Brief.

• blackberry.security.appInfo.android.appUpdateURL: This is the URL that the user can use to download

3. Include thesettings in the structural section of the file.

Example:

4. Coordinate with the UEM administrator to upload the app policy for your app in UEM. See Manage settings for

a BlackBerry Dynamics apps (App configuration > Upload a template).

You can use the branding API to add a custom logo and colors to the app UI.For more information, see (void)

configureUIWithLogo in theAPI Reference.

Using zero sign-on for SaaS services throughBlackBerry Enterprise

Your customBlackBerry Dynamicsapps can leverage zero sign-on (ZSO) for SaaS throughBlackBerry Enterprise

Identity. For more information, see theBlackBerry Enterprise Identity docs.

Integrating BlackBerry Enterprise Mobility Server services

This section covers the general approach for programming with the BlackBerry Dynamics SDK and the BlackBerry

Enterprise Mobility Server services. The approach consists of two parts:

• Programming an app to interact with the desired BEMS services

• Entitling users to the necessary applications

entitlement ID and version to uniquely identify a BlackBerry Dynamics app). The BlackBerry Dynamics SDK has

functions to discover services, and each BEMS service has specific programming interfaces.

in other sections of this guide and in the BlackBerry Dynamics API reference.

After your consumer app discovers the service, the way the app communicates with the service depends on the

service definition.

Note: Most BEMS services run over SSL (HTTPS) on port 8443. Be sure your consumer application connects to

the correct server and port.

Described here is a general approach to using the BlackBerry Dynamics SDK and Server-based Services

RSS Reader Demonstrates how to use the BlackBerry Dynamics Secure Communications

The BlackBerry Dynamics SDK includesthe BlackBerry Dynamics Automated Test Support Library (ATSL)to

support automated testing for your BlackBerry Dynamics apps. The library is delivered as a dynamic framework.

activation and authorization. The configuration and structure of the library is compatible with the tools offered by

• Accessibility identifiers

For more information about these components and iOS user interface testing, see Apple Documentation Archive:

User Interface Testing.

You canuse the BlackBerry Dynamics library and the native library components mentioned above toautomate the

building, execution, and reporting of your application tests.

Since the BlackBerry Dynamics ATSL is delivered as a framework, you cannot make your own changes to it. If

you want to review the implementation and customize it, you can see the source in GitHub at https://github.com/

blackberry/BlackBerry-Dynamics-iOS-Samples/tree/master/AutomatedTestSupportLibrary.

You can get the ATSL framework using Cocoa pods (see Configure a new or existing BlackBerry Dynamics app to

use the dynamic framework).

ownBlackBerry Dynamicsapps. Note the following details about ATSL integration:

Use of ATSL for

interactions

As part of your automated testing you must activate a new installation of your BlackBerry Dynamics app or log

in to an already activated app. This requires a user identifier (typically an email address), anaccess key, and a

password.The ATSL can read activation or login credentials from a file in JSON format in the application resource

bundle.

The file does not have any naming restrictions and must contain a single object with the following fields:

• GD_TEST_PROVISION_EMAIL: String that specifies the user's email address

• GD_TEST_PROVISION_ACCESS_KEY: String that specifies the access key

• GD_TEST_PROVISION_PASSWORD: String that specifies the user's password after provisioning or during login

• GD_TEST_UNLOCK_KEY: Specifies the unlock key, if necessary (optional)

For example:

• Manually generate an access key for a user in themanagement console, then manually edit the file.

• Manually generate and store a number of access keys in advance, then automatically edit the file and consume

a key from the store.

• Automatically generate an access key, and optionally a user, with the BlackBerry Web Services APIs, then

automatically edit the file.

Use the option that best suits your needs, based on your access to the management console and administrator

level permissions, your familiarity with the BlackBerry Web Services APIs, and your preference for using a new

activation for every test or running subsequent tests on the same app as an upgrade.

Please note the following:

• In the JSON file, the access key and unlock key have to be 15 characters and cannot have dashes.

• Automated testing works in Enterprise Simulation mode, but will have the same restrictions (for example, the

app cannot connect to any back-end servers).

• Every BlackBerry Dynamics app needs a one-time initialization to complete activation. To ensure that this is

executed first, define a dedicated test method that executes BlackBerry Dynamics activation and have that

• The source code is provided in Objective-C. If any of the app or test code is written in Swift, you must configure

the code according to Apple standards for mixing Swift and Objective-C.

simulator, and record the results. You can run the command from a continuous integration system such as

Jenkins.

Run the following command:

Define the following variables:

XCODE_PROJ_PATH The path to your project.

APP_SCHEME The name of your app scheme.

TEAM_ID The unique identifier of the team used for signing, as provided by

DESTINATION A string that describes the device that will be used to run the tests.

APP_TARGET The target for user interface tests.

CLASS The test class to be executed. This value is optional. If it is omitted, all test

TESTCASE The method within the test class to be run. This value is optional. If it is

Test results are printed on standard output in the OCUnit format, and can be saved by a continuous integration

system. You might need to convert the format to JUnit or another format that is suitable for your continuous

integration system.

The tests that you can run from the command line (Execute tests from the command line withXcodetools)can

also be run fromwithin theXcodeIDE. This can be useful for investigating test failures with breakpoints orfor

running tests as you write the code.

The tests in theBlackBerry Dynamicssample applications foriOScan be run fromwithin the IDE in the same way

as any other tests that use the XCTests framework. Test results will be available in the Result view.

For more information, seeApple Documentation Archive: Running Tests and Viewing Results.

Add automated testing to your BlackBerry Dynamics iOS app

The following steps assume that the target app is already configured to use the BlackBerry Dynamics SDK.

During the development and testing of your BlackBerry Dynamics app, you can run the app in enterprise

simulation mode to verify its execution and functionality. This mode runs the app on an emulator (for example,

the emulator that is supplied with the SDK). The user authentication process is simulated, so there is no direct

communication with your organization’s UEM server. As a result, a valid activation key is not required to activate

the app.

Enterprise simulation mode is intended for development environments only. Note that even though there is no

communication with the management server, communication with the BlackBerry Dynamics NOC still occurs

during the initial activation of the app. The BlackBerry Dynamics NOC must be accessible from your testing

environment.

You will notice the following differences when you run the app in enterprise simulation mode:

• Any email address and activation key (PIN) is accepted for enterprise activation.

You should also note the following:

• If you run an app that was built for enterprise simulation mode on an actual device and not on an emulator, the

app will be wiped.

• If you try to change to simulation mode when the app is already installed on a device, the app will be wiped.

• The Secure Storage, Secure Communication, and Push Channel APIs(Android/iOS) are all available in

The prefix of the file includes the project name. For example, if the project name is FirstProject,the .plistfile is

named FirstProject-Info.plist. The file consists of a number of key-value pairs, including type.

• Value:GDEnterpriseSimulation

Provisioning error The email address or access key (PIN) has been incorrectly entered,

For BlackBerry Dynamics apps running SDK version 5.0 or later, console logs are generated only if this setting is

turned on or if the app is running in enterprise simulation mode.

Different targets can have different activity logging configurations. You can configure the logging to be detailed or

selective. Changes to the console logging configuration take effect the next time the target is built and run, and do

not affect the container log.

1. Open the app’sInfo.plistfile.

• Upload resumed after suspension

• Actions for managing a log upload (cancel, suspend, resume)

• Enable detailed logging withdetailedLoggingFor (Android/iOS)

API (Android/iOS). If detailed logging is enabled, present the log upload progress UI or any other related UI.

The following sample apps that are included in the BlackBerry Dynamics SDK for iOS demonstrate how to

useGDLogManager:

• All Swift samples

Testing connectivity to application servers and diagnostic functions

You can use the GDDiagnostic class to test connectivity to application servers and other diagnostic functions.

The GreetingsClient sample app that is provided with the SDK demonstrates how to use the GDDiagnosticclass.

WERE FORESEEN OR UNFORESEEN, AND EVEN IF BLACKBERRY HAS BEEN ADVISED OF THE POSSIBILITY OF

SUCH DAMAGES.

HAVE NO OTHER OBLIGATION, DUTY, OR LIABILITY WHATSOEVER IN CONTRACT, TORT, OR OTHERWISE TO

YOU INCLUDING ANY LIABILITY FOR NEGLIGENCE OR STRICT LIABILITY.

THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVE OF THE NATURE

OF THE CAUSE OF ACTION, DEMAND, OR ACTION BY YOU INCLUDING BUT NOT LIMITED TO BREACH OF

CONTRACT, NEGLIGENCE, TORT, STRICT LIABILITY OR ANY OTHER LEGAL THEORY AND SHALL SURVIVE A

FUNDAMENTAL BREACH OR BREACHES OR THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS AGREEMENT

OR OF ANY REMEDY CONTAINED HEREIN; AND (B) TO BLACKBERRY AND ITS AFFILIATED COMPANIES, THEIR

DIRECTORS, EMPLOYEES, AND INDEPENDENT CONTRACTORS.

providers might not offer Internet browsing functionality with a subscription to the BlackBerry

Internet Service.

or use of Third Party Products and Services with BlackBerry's products and services may require one or more

are solely responsible for determining whether to use Third Party Products and Services and if any third party

licenses are required to do so. If required you are responsible for acquiring them. You should not install or use

Third Party Products and Services until all necessary licenses have been acquired. Any Third Party Products and

Services that are provided with BlackBerry's products and services are provided as a convenience to you and are

provided "AS IS" with no express or implied conditions, endorsements, guarantees, representations, or warranties

of any kind by BlackBerry and BlackBerry assumes no liability whatsoever, in relation thereto. Your use of Third

and other agreements applicable thereto with third parties, except to the extent expressly covered by a license or

other agreement with BlackBerry.

BlackBerry applicable thereto. NOTHING IN THIS DOCUMENTATION IS INTENDED TO SUPERSEDE ANY EXPRESS

WRITTEN AGREEMENTS OR WARRANTIES PROVIDED BY BLACKBERRY FOR PORTIONS OF ANY BLACKBERRY

PRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION.

BlackBerry Enterprise Software incorporates certain third-party software. The license and copyright information

BlackBerry Limited

2200 University Avenue East

Waterloo, Ontario

Canada N2K 0A7

BlackBerry UK Limited

Ground Floor, The Pearce Building, West Street,

Maidenhead, Berkshire SL6 1RL

United Kingdom

|Legal notice|64