BlackBerry AppSecure SDK User Guide
- June 8, 2024
- BlackBerry
Table of Contents
BlackBerry AppSecure SDK
What is the BlackBerry AppSecure SDK?
The BlackBerry AppSecure SDK is a development tool that allows you to
integrate advanced security features with your Android and iOS apps. The SDK
gives any mobile app the ability to leverage BlackBerry security services that
detect, evaluate, and respond to environmental risks and a wide range of cyber
threats in real time. The BlackBerry AppSecure SDK enables you to build apps
that are resistant to sophisticated mobile attacks while offering the highest
level of protection for your organization’s users and data.
The BlackBerry AppSecure SDK provides APIs that perform device security checks
to ensure protection against security vulnerabilities, as well as APIs that
initiate calls to the BlackBerry Infrastructure and dedicated cloud services
to assess and respond to threats. For example, the mobile threat detection
capabilities of the SDK initiate calls to the BlackBerry Protect cloud
services, which use sophisticated AI and machine-learning to provide a real-
time evaluation of whether an Android app is safe or potentially malicious.
When you integrate the BlackBerry AppSecure SDK, you can decide which device
checks and security services you want to implement and how you want your app’s
functionality, user experience, and UI to respond to the analysis and
evaluation of security risks.
Any Android or iOS app can integrate the BlackBerry AppSecure SDK. The
features and services offered by the SDK do not require the installation of
any BlackBerry software or product. The SDK does not provide management
capabilities for apps or user accounts, or any level of device control or
administration. If you are interested in secure mobile app development in
combination with the advanced controls offered by BlackBerry UEM, visit
BlackBerry Docs to learn more about the BlackBerry Dynamics SDK.
Note: The BlackBerry AppSecure SDK is currently available as a public beta
release that is subject to further testing and changes by BlackBerry. Some SDK
features might not yet be available or may require further development. The
SDK has been made available for early testing and evaluation purposes, with a
full release to follow in the near future. Before you use the SDK, review and
agree with terms and conditions of the beta release.
Key features of the BlackBerry AppSecure SDK
The following features are available in the current release of the BlackBerry
AppSecure SDK:
| Feature | Platform | Description |
|---|
Device security checks
Jailbreak detection| iOS| Detect whether the device is jailbroken.
Root detection| Android| Detect whether the device is rooted.
Debugging detection| iOS Android| Detect whether debug mode is enabled on the
device.
Inline hooking detection| iOS Android| Detect inline hooking, a method used by
malicious software to intercept calls to target functions.
Emulation detection| Android| Detect whether the app is running on an
emulator.
Screen lock check| iOS Android| Detect whether a screen lock is enabled on the
device (for example, a password or PIN).
Feature| Platform| Description
---|---|---
Developer mode check| Android| Detect whether developer mode is enabled on the
device.
Disk encryption check| Android| Detect whether disk encryption is enabled on
the device.
App authorization| iOS Android| Require users to set a password or PIN to
access the app. Optionally, enable a user to unlock the app using biometrics.
Software security
Minimum OS check| iOS Android| Check whether the device satisfies a minimum OS
requirement that you can configure.
Minimum security patch level check| Android| Check whether the device
satisfies a minimum security patch level that you can configure.
Malicious app detection| Android| Use the local machine learning models that
are built into the SDK or send the app files to the BlackBerry Protect cloud
services to determine whether an app is safe or potentially malicious.
Sideloaded app detection| Android| Detect whether the app is installed from a
trusted source (for example, Google Play or the Samsung Galaxy Store); apps
from an untrusted source are considered sideloaded.
User identity
Malicious URL detection| iOS Android| Send URLs, including URLs in text
messages (if access is permitted), to the BlackBerry Protect cloud services to
determine whether the URLs are safe or potentially malicious.
Data security
Secure app file system and storage| iOS Android| Use secure data storage,
allowing your app to store encrypted data that can be read by your app only.
App data backup to public cloud services| iOS Android| Block app data backup
to public cloud services such as iCloud and Google Cloud.
Application Authorization| iOS Android| Require users to set a password or PIN
to access the app.
Biometric authentication| iOS Android| Require users to use a biometric
authentication method (for example, a fingerprint).
Network security
Feature| Platform| Description
---|---|---
Network security check| iOS Android| On Android and iOS devices, if the SDK is
unable to connect to the BlackBerry Protect cloud services, it determines that
the current network is not safe.
Insecure Wi-Fi check| Android| On Android devices, the SDK periodically checks
the properties of the current Wi-Fi access point to determine if it is secure.
The following features are implemented in the sample apps that are included in the SDK:
- Safe browsing (iOS, Android)
- Root detection (Android)
- Debugging detection (Android)
- Screen lock check (iOS, Android)
- Developer mode check (Android)
- Disk encryption check (Android)
- Minimum OS check (iOS, Android)
- Minimum security patch level check (Android)
- Malicious app detection (Android)
- PIN creation and entry (Android)
- Biometric authentication (iOS, Android)
- Network security check (iOS, Android)
- Insecure Wi-Fi check (Android)
Sharing data and feedback with BlackBerry
Your data and feedback are valuable to help deliver new features and
enhancements in new versions of the SDK. We encourage you to activate the data
collection API (see the DataCollectionRules class reference) that will allow
BlackBerry to receive information about the environments, risks, and threats
that you encounter. This API does not provide BlackBerry with any information
that can be used to identify users or organizations and meets all privacy-
related requirements. BlackBerry will not use the information that it receives
for any purpose other than the improvement of the BlackBerry AppSecure SDK.
To submit feedback, visit BlackBerry Developer Support and access the
BlackBerry Beta Community.
If you encounter any issues while using the SDK, you can share your log files
with BlackBerry Support. Visit BlackBerry Developer Support to access the
BlackBerry Beta Community, and see the Diagnostics Class in the API reference.
Getting started with the BlackBerry AppSecure SDK
Before you download, install, or use the SDK, you must read the SDK Development License Agreement. By downloading, installing, and using the SDK, you agree to the terms and conditions of the license agreement.
Step Description
Review the Software requirements.
Register the app with BlackBerry.
Register the identity provider for your app.
Add the App Client ID to your app.
• Add the BlackBerry App Client ID to your Android app
• Add the BlackBerry App Client ID to your iOS app
Integrate the BlackBerry AppSecure SDK into your app.
• Integrate the BlackBerry AppSecure SDK into your Android app
• Integrate the BlackBerry AppSecure SDK into your iOS app
Initialize the BlackBerry AppSecure SDK.
• Initialize the BlackBerry AppSecure SDK in your Android app
• Initialize the BlackBerry AppSecure SDK in your iOS app
Review the integration levels of the SDK.
Explore the API reference.
Software requirements
Platform Requirements
Android • Android Studio 3.6.3 or later
• Gradle 3.6.3 or later
• Android SDK API level 26 or higher
• Android OS 8 or later
Platform Requirements
iOS • Swift 5 or later
• Xcode 11.3 or later
• CocoaPods 1.7 or later
• iOS 14 or later
Register the app with BlackBerry
You must register your app with BlackBerry through your BlackBerry Online
Account. If you don’t have an account, you can create one.
-
Browse to the following URL: https://account.blackberry.com/a/organization//applications/add?capability=mtd
-
Log in using your BlackBerry Online Account (myAccount) credentials.
-
Enter the following information:
-
Application Name: The name of your app (for example, MyApp).
-
Entitlement ID: It is recommended that you use the package name of your app (for example,com.company.myapp).
-
Version: 1.0.0.0
Note: The version number does not need to be updated when you upgrade your app and does not need to match your native app version. -
Management: Clear the Application will be managed by BlackBerry UEM option. You must remove this option so that you can use your own identity provider for authentication.
-
Capabilities: Select BlackBerry Protect. This enables your application to utilize the BlackBerry Protect threat models.
-
-
Click Add application.
After you finish: Register the identity provider for your app.
Register the identity provider for your app
The BlackBerry AppSecure SDK reuses the existing user identity within your
application to facilitate getting the latest security threat information from
the BlackBerry Cloud. The library works with your user identity and management
systems to provide strong authentication and authorization.
In practice, an OpenID Connect Identity Token belonging to the user that is
currently logged in is provided to the BlackBerry AppSecure SDK runtime.
BlackBerry validates this token against your identity provider’s token
introspection endpoint. This process avoids the need to rely on an
application-specific API key.
You can use any identity provider as long as it is compliant with OpenID
Connect (https://openid.net/connect/). For more information, see Information
about compliant IDPs.
If you don’t have an identity provider, you can use Firebase as your identity
provider (IDP).
When the IDP is registered, you are provided a BlackBerry App Client ID which
you add to your app.
Before you begin:
- Register the app with BlackBerry.
- Verify that you have the following information:
- The discovery URL of your IDP
- The Authorized Client ID for your app
-
In your organization’s BlackBerry Online Account, on the navigation menu, click Applications.
-
Click your app.
-
On the IDP tab, in the Identity Provider section, do the following:.
a) In the Discovery URL field, type the discovery URL of the identity provider.
b) In the Client ID field, type the Authorized Client ID.
No other fields are required. -
Click Register IDP.
A BlackBerry App Client ID is created.
After you finish:
- Add the BlackBerry App Client ID to your Android app
- Add the BlackBerry App Client ID to your iOS app
Information about compliant IDPs
You can integrate the BlackBerry AppSecure SDK into your app using any
identity provider (IDP) over the internet as long as it is compliant with
OpenID Connect (https://openid.net/connect/).
The following table lists a few examples of IDPs that are compatible and how to determine the discovery URLs and authorized client IDs:
| Identity provider | Discovery URL | Authorized Client IDs |
|---|---|---|
| Firebase | https://securetoken.google.com/ ${Project-ID} /.well- known | |
| /openid-configuration | ${Project-ID} |
The Project ID in Firebase.
Okta| https:// ${yourOktaOrg} /.well-known/openid- configuration| One of your app’s OAuth
2.0 client IDs registered with Okta.
Google| https://account.google.com/.wellknown/openid- configuration| In your app’s Google- Services.json file, use the value at ‘client > oauth_client > client_id’.
If you don’t have access to your IDP to determine the discovery URL or authorized client ID, but you do have a JWT Identity token, you can use a third-party token inspection tool to examine the token (for example, https://jwt.io).
- ‘iss’ is the token issuer which you can use to determine the discovery URL by adding /.well-known/openid-configuration
- ‘aud’ is the intended audience of the token and is the Authorized Client ID.
Integrating the IDP and BlackBerry AppSecure SDK into your Android app
This section describes how to add the IDP and integrate and initialize the
BlackBerry AppSecure SDK with an Android app.
Add the BlackBerry App Client ID to your Android app
Before you begin: Register the identity provider for your app and copy the
BlackBerry App Client ID.
In Android Studio, in the AndroidManifest.xml file, include the App Client ID.
For example:
After you finish: Integrate the BlackBerry AppSecure SDK into your Android app.
Integrate the BlackBerry AppSecure SDK into your Android app
Use Gradle to integrate BlackBerry AppSecure SDK into your Android Studio
project. Before you begin: Add the BlackBerry App Client ID to your Android
app.
- In your root-level (project-level) Gradle file (build.gradle), add a rule to include the BlackBerry Maven repository.
- In the app-level module of your Gradle file (usually app/build.gradle), declare a dependency on the BlackBerry AppSecure SDK for Android.
- Sync your app to ensure that all dependencies are downloaded.
After you finish: Initialize the BlackBerry AppSecure SDK in your Android app.
Initialize the BlackBerry AppSecure SDK in your Android app
Before you begin: Integrate the BlackBerry AppSecure SDK into your Android app.
-
Import the BlackBerry AppSecure SDK into an activity.
-
Call enableSecurity.
-
Retrieve the identity token of your authenticated user from your IDP.
The ID token is a JSON Web Token (JWT), which is a cryptographically-signed, Base64-encoded JSON object. To retrieve the ID token from your IDP, you must have already authenticated the user.
If you are using Firebase, the ID token can be retrieved by following the Firebase instructions to retrieve ID tokens on clients. Other IDPs that are compliant with OpenID Connect typically provide an endpoint and client library which returns the ID token. -
Provide the identity token to the BlackBerry AppSecure SDK runtime.
-
Confirm that the InitializationState of the runtime is ‘active’.
After you finish: Using the BlackBerry AppSecure SDK API reference, configure your application to be notified when a threat is detected.
Integrating the IDP and BlackBerry AppSecure SDK into your iOS app
This section describes how to add the IDP and integrate and initialize the BlackBerry AppSecure SDK with an iOS app.
Add the BlackBerry App Client ID to your iOS app
Before you begin: Register the identity provider for your app and copy the
BlackBerry App Client ID.
In Xcode, add the App Client ID to your application’s ‘info.plist’.
For example:
After you finish: Integrate the BlackBerry AppSecure SDK into your iOS app.
Integrate the BlackBerry AppSecure SDK into your iOS app
In Xcode, you can add the BlackBerry AppSecure SDK as a dependency using
CocoaPods. Before you begin: Add the BlackBerry App Client ID to your iOS app.
In Xcode, do the following to integrate the BlackBerry AppSecure SDK into the
project:
After you finish: Initialize the BlackBerry AppSecure SDK in your iOS app.
Initialize the BlackBerry AppSecure SDK in your iOS app
Before you begin: Integrate the BlackBerry AppSecure SDK into your iOS app.
-
Import the BlackBerrySecurity module into your class.
-
Initialize the BlackBerrySecurity framework and invoke enableSecurity.
-
Retrieve the identity token of your authenticated user from your IDP.
The ID token is a JSON Web Token (JWT), which is a cryptographically-signed, Base64-encoded JSON object. To retrieve the ID token from your IDP, you must have already authenticated the user.
If you are using Firebase, the ID token can be retrieved by following the Firebase instructions to retrieve ID tokens on clients. Other IDPs that are compliant with OpenID Connect typically provide an endpoint and client library which returns the ID token. -
Provide the identity token to the BlackBerry AppSecure SDK runtime.
-
Confirm that the InitializationState of the runtime is ‘active’.
After you finish: Using the BlackBerry AppSecure SDK API reference, configure your application to be notified when a threat is detected.
Integration levels of the BlackBerry AppSecure SDK
You can leverage any of the following integration levels of the BlackBerry AppSecure SDK to fit your security needs. For more information about the APIs and features discussed below, see the AppSecure SDK API reference.
| Integration level | Description |
|---|---|
| Baseline | You register your app as a threatStatusListener and use |
getOverallThreatStatus( ) to get an overall enumerated threat level that the
library has determined (critical, high, medium, low, null). The application
layer can then determine what this threat level means for the app and take
action. For example, the app can display a graphic or warning message to the
user, it can send the threat level to a server to be recorded or factored into
a risk engine, or it can restrict certain features until the threat level is
reduced.
Detailed threat| This level of integration is recommended if you want to
gather more information about each type of threat so that your app can execute
the most appropriate action in response. You can configure the app to query
information about individual threat types (for example, AppMalware,
AppSideLoad, DeviceSecurity, and so on). Each threat type has an associated
threat level to allow the app
to gather and act on more detailed information. For example, based on the detailed information gathered, your app can display different graphics or warning messages to the user.
Customized threat| This level of integration provides even more granular control over threat detection and response. You can use ManageFeatures to customize which threats to detect (for example, you can disable checks that are not relevant for your app). You can use ManageRules to configure how you want to run specific checks (for example, you can run malware checks more frequently).
Using the BlackBerry AppSecure SDK API reference
The BlackBerry AppSecure SDK API reference describes how to use the principal interfaces, packages, and classes of the SDK:
- BlackBerry AppSecure SDK for Android API reference
- BlackBerry AppSecure SDK for iOS API reference
The following table highlights key sections of the API reference:
| Item | Description |
|---|---|
| SecurityControl Class Reference | Initializes the BlackBerry AppSecure SDK |
library within your app so that threats can be detected and alerts can be
provided.
AppAuthentication Class Reference| Methods to set, change and enter an
application password and manage biometric authentication.
AppIdentity Class Reference| Provides a various app identifiers that can be
used to determine if the user’s session is originating from the same app
instance and device when authenticating with the application server.
ThreatStatus Class Reference| Provides details about security threats related
to the device, app, network, and user.
ContentChecker Class Reference| Detect potentially malicious URLs or IP
addresses to protect users from malicious websites, phishing attempts,
malware, adware, and other web sources that pose a threat to your data.
ContentCheckerRules Class Reference| Configure rules that change how the SDK
detects malicious URLs and IP addresses.
DeviceChecker Class Reference| Perform security checks on the device to
identify potential security risks.
DeviceSecurityRules Class Reference| Control which device security checks are
evaluated when enableSecurity or checkDeviceSecurity are called.
DeviceSoftwareRules Class Reference| Configure a check for a minimum Android
security patch level and OS version. If the device does not meet these
requirements it is considered unsafe.
MalwareScanRules Class Reference| Configure rules that control how the SDK
detects malware on an Android device.
ManageFeatures Class Reference| Retrieve the status of a security feature and
enable or disable features.
ManageRules Class Reference| Configure and manage security rules.
Package com.blackberry.security.file| Store app data in the BlackBerry secure
file system.
PasswordUtility Class Reference| Check the strength of passwords.
Item| Description
---|---
Preferences Class Reference| Manage shared preferences in the BlackBerry
secure data store.
DataCollectionRules Class Reference| Enable anonymous data collection to help
BlackBerry improve the features of the BlackBerry AppSecure SDK.
Diagnostics Class
Reference > void uploadLogs (LogsUploadFinishedListener listener)
| Send recent logs to BlackBerry support.
Troubleshooting IDP configuration issues
| Problem | Possible cause | Possible solution |
|---|
After you initialize the BlackBerry AppSecure SDK with
enableSecurity, the app does not run.
| The BlackBerry App Client ID is missing from AndroidManifest.xml or from the info.plist of the Xcode project.| See:
• Add the BlackBerry App Client ID to your Android app
• Add the BlackBerry App Client ID to your iOS app
After calling provideToken, the following are returned:
• ErrorDomain: AppConfig
• ErrorType: ErrorTypeTokenInvalidClientID
| The BlackBerry App Client ID is incorrect, possibly because the value was
not copied correctly or the client has been deleted.| See Register the
identity provider for your app.
After calling provideToken, the following are returned:
• ErrorDomain: IDPConfig
• ErrorType: ErrorTypeNoBearerPolicyForClient
| The discovery URL for your identity provider in my Account does not
match the issuer (iss) in your JWT Bearer token.
| Update the discovery URL to match the issuer of the IDP.
See Register the identity provider for your app.
After calling provideToken, the following are returned:
• ErrorDomain: IDPConfig
• ErrorType: ErrorTypeAzpClaimMismatch
| The Authorized Client IDs configured for your IDP in my Account do not match with the Audience (aud) or Authorized Party (azp) fields in your JWT Bearer token.| Update the Authorized Client ID.
See Register the identity provider for your app.
I don’t have an identity provider
If you don’t have an identity provider, you can create one using Firebase. The
BlackBerry AppSecure SDK sample app ‘Pyrite Financial’ integrates Firebase as
the identity provider and is available for Android and iOS.
You can use the Project ID from the Firebase project to determine the
discovery URL and Authorized Client ID. See Information about compliant IDPs.
Before you begin: Register the app with BlackBerry
- Create a Firebase project and register your application.
- For Android, see https://firebase.google.com/docs/android/setup.
- For iOS, see https://firebase.google.com/docs/ios/setup.
- Determine the Google authentication mechanism that you want to integrate with. For example, you can easily use password authentication (Email/Password) as the sign-in method and add a test user. The Pyrite Financial sample application demonstrates password authentication.
- To configure your Firebase IDP with BlackBerry, you need to retrieve the Project ID from the Firebase console.
a) On the left menu, beside Project Overview, click the gear icon to view the Project Settings.
b) Copy the Project ID value.
After you finish: Register the identity provider for your app
Legal notice
©2022 BlackBerry Limited. Trademarks, including but not limited to BLACKBERRY, BBM, BES, EMBLEM Design, ATHOC, CYLANCE and SECUSMART are the trademarks or registered trademarks of BlackBerry Limited, its subsidiaries and/or affiliates, used under license, and the exclusive rights to such trademarks are expressly reserved. All other trademarks are the property of their respective owners.
This documentation including all documentation incorporated by reference herein such as documentation provided or made available on the BlackBerry website provided or made accessible “AS IS” and “AS AVAILABLE” and without condition, endorsement, guarantee, representation, or warranty of any kind by BlackBerry Limited and its affiliated companies (“BlackBerry”) and BlackBerry assumes no responsibility for any typographical, technical, or other inaccuracies, errors, or omissions in this documentation. In order to protect BlackBerry proprietary and confidential information and/or trade secrets, this documentation may describe some aspects of BlackBerry technology in generalized terms. BlackBerry reserves the right to periodically change information that is contained in this documentation; however, BlackBerry makes no commitment to provide any such changes, updates, enhancements, or other additions to this documentation to you in a timely manner or at all.
This documentation might contain references to third-party sources of information, hardware or software, products or services including components and content such as content protected by copyright and/or third-party websites (collectively the “Third Party Products and Services”). BlackBerry does not control, and is not responsible for, any Third Party Products and Services including, without limitation the content, accuracy, copyright compliance, compatibility, performance, trustworthiness, legality, decency, links, or any other aspect of Third Party Products and Services. The inclusion of a reference to Third Party Products and Services in this documentation does not imply endorsement by BlackBerry of the Third Party Products and Services or the third party in any way.
EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOUR
JURISDICTION, ALL CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS, OR
WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY
CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS OR WARRANTIES OF
DURABILITY, FITNESS FOR A PARTICULAR PURPOSE OR USE, MERCHANTABILITY,
MERCHANTABLE QUALITY, NON-INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, OR
ARISING FROM A STATUTE OR CUSTOM OR A COURSE OF DEALING OR USAGE OF TRADE, OR
RELATED TO THE DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCE OF
ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES
REFERENCED HEREIN, ARE HEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THAT
VARY BY STATE OR PROVINCE. SOME JURISDICTIONS MAY
NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND CONDITIONS. TO
THE EXTENT PERMITTED BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO
THE DOCUMENTATION TO THE EXTENT THEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT
CAN BE LIMITED, ARE HEREBY LIMITED TO NINETY (90) DAYS FROM THE DATE YOU FIRST
ACQUIRED THE DOCUMENTATION OR THE ITEM THAT IS THE SUBJECT OF THE CLAIM.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO
EVENT SHALL BLACKBERRY BE LIABLE FOR ANY TYPE OF DAMAGES RELATED TO THIS
DOCUMENTATION OR ITS USE,OR PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE,
HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED HEREIN
INCLUDING WITHOUT LIMITATION ANY OF THE FOLLOWING DAMAGES: DIRECT,
CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR
AGGRAVATED DAMAGES, DAMAGES FOR LOSS OF PROFITS OR REVENUES, FAILURE TO
REALIZE ANY EXPECTED SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS
INFORMATION, LOSS OF BUSINESS OPPORTUNITY, OR CORRUPTION OR LOSS OF DATA,
FAILURES TO TRANSMIT OR RECEIVE ANY DATA, PROBLEMS ASSOCIATED WITH ANY
APPLICATIONS USED IN CONJUNCTION WITH BLACKBERRY PRODUCTS OR SERVICES,
DOWNTIME COSTS, LOSS OF THE USE OF BLACKBERRY PRODUCTS OR SERVICES OR ANY
PORTION THEREOF OR OF ANY AIRTIME SERVICES, COST OF SUBSTITUTE GOODS, COSTS OF
COVER, FACILITIES OR SERVICES, COST OF CAPITAL, OR OTHER SIMILAR PECUNIARY
LOSSES, WHETHER OR NOT SUCH DAMAGES WERE FORESEEN OR UNFORESEEN, AND EVEN IF
BLACKBERRY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION,
BLACKBERRY SHALL 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 SUCCESSORS, ASSIGNS, AGENTS, SUPPLIERS (INCLUDING AIRTIME SERVICE
PROVIDERS), AUTHORIZED BLACKBERRY DISTRIBUTORS (ALSO INCLUDING AIRTIME SERVICE
PROVIDERS) AND THEIR RESPECTIVE DIRECTORS, EMPLOYEES, AND INDEPENDENT
CONTRACTORS.
IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALL
ANY DIRECTOR, EMPLOYEE, AGENT, DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR
OF BLACKBERRY OR ANY AFFILIATES OF BLACKBERRY HAVE ANY LIABILITY ARISING FROM
OR RELATED TO THE DOCUMENTATION.
Prior to subscribing for, installing, or using any Third Party Products and
Services, it is your responsibility to ensure that your airtime service
provider has agreed to support all of their features. Some airtime service
providers might not offer Internet browsing functionality with a subscription
to the BlackBerry® Internet Service. Check with your service provider for
availability, roaming arrangements, service plans and features. Installation
or use of Third Party Products and Services with BlackBerry’s products and
services may require one or more patent, trademark, copyright, or other
licenses in order to avoid infringement or violation of third party rights.
You 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 Party Products and Services shall be governed by and subject to you
agreeing to the terms of separate licenses and other agreements applicable
thereto with third parties, except to the extent expressly covered by a
license or other agreement with BlackBerry.
The terms of use of any BlackBerry product or service are set out in a
separate license or other agreement with 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 associated with this software is available at http://worldwide.blackberry.com/legal/thirdpartysoftware.jsp.
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
Published in Canada
References
- BlackBerry
- JSON Web Tokens - jwt.io
- OpenID Foundation website
- AB/Connect Working Group - OpenID Foundation
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>