Zum Inhalt springen
  • Blog
  • Cookie Policy (EU)
  • Datenschutzerklärung
  • EBF Docs
  • Onboarder Source and Target
  • Test
  • EBF product documentation

    Find help using and administering EBF applications

    EBF Onboarder

    • Release Notes
    • 01. Introduction
    • 02. Registration
    • 03. Preparation of the migration
    • 04. Migration project setup
    • 05. Communication
    • 06. Transformation Tool
    • 07. Enrollment Wizard
    • 08. Enrollment Advice
    • 09. Migration launch
    • 10. Migration monitoring
    • 11. Migration project management
    • 12. EBF Onboarder Status website
    • 13. Platforms
    • 14. Contact
    • Target System Jamf Pro / School
    • Target System MaaS360
    • Target System Microsoft Intune
    • Target System Omnissa Workspace ONE
    • Target System Ivanti EPMM and Neurons
    • Source System baramundi Management Suite (bMS)
    • Source System Jamf Pro
    • Source System MaaS360
    • Source System Microsoft Intune
    • Source System Omnissa Workspace ONE
    • Source System Ivanti EPMM Neurons / MobileIron Core and Cloud and Ivanti EPM (Landesk)
    • Source System BlackBerry UEM Cloud
    • Source System Blackberry UEM v12
    View Categories
    • Home
    • EBF Docs
    • EBF Onboarder

    Source System BlackBerry UEM Cloud

    4 min read

    01. Introduction

    There is a general documentation available for the EBF Onboarder, where you can find information about its prerequisites and the whole migration project. It describes how you can setup a migration project, how you can setup invitation emails and reminders which guide your users through the migration. It also tells you how to initiate the migration process and how to track the migration status.

    This documentation complements the general EBF Onboarder documentation and provides more detailed information about the prerequisites for the source system BlackBerry UEM Cloud.

    ATTENTION: This documentation does not replace any BlackBerry documentation. It is only describing prerequisites for the EBF Onboarder. Please consult the BlackBerry documentation and support if necessary.

    02. Prerequisites for the source system BlackBerry UEM Cloud

    If your source system is BlackBerry UEM Cloud, it is recommended that you login to your BlackBerry UEM Cloud console to make the changes which are described in the following chapters.

    02.1. Create a client app

    To communicate with your BlackBerry UEM Cloud tenant a client app needs to be created in your BlackBerry account. App values will be used by the EBF Onboarder to setup and run the migration.

    NOTE: Do not use an existing client app. To be able to have a better control about the client apps, each topic should get its own client app.

    Follow these steps to create the client app:

    1. Login to your account: https://myaccount.blackberry.com/myaccount.html.
    2. Go to ‘myAccount’ >> ‚BlackBerry Support Community‘ >> ‚My Organization‘ >> ‚Overview‘.
    3. Click on ‘Applications’ >> ‘Add Application’.
    4. Enter a name and select ‘BlackBerry Platform APIs’.
    5. Click on ‘Template’ >> ‘Add Template’.
    6. Enter the following details:
      • Redirect URLs: Enter your FQDN. Example: https://p1234.cp1.uem.blackberry.com.
      • Type: Select ‘web’.
      • Grant Type: Select ‘client_credentails’.
      • Response Types: Select ‘none’.
      • Token Endpoint Auth Method: Select ‘client_secret_basic’.
      • API Scopes: Select ‘Mobile Device Management’.
    7. Click on ‘Register’.
    8. Click on ‘Client’ >> ‘Add Client’.
      • Enter a name.
      • Select your source system’s tenant SRP number (move it from the Available container to the Selected container).
      • Leave ‘Post Logout Redirect URLs’ empty.
      • Set ‚Id Token Signed Response Alg‘ to ES256.
    9. Click on ‘Register’.
    10. You can review the required details for your EBF Onboarder setup under ‘Applications’ >> ’Application Name’ >> ‘BlackBerry Platform APIs’ >> ‘Client’.
    11. Assign the app to an admin in your source UEM Cloud who has permission to ‘View users, devices’ and ‘Manage devices’, ‘Delete only work data, Delete all device data, Delete device’. This can be found under ‘Settings’ >> ‘Administrators’ >> ‘Web service clients’.
      Add the apps also in OpenID Connect-Apps under Settings > BlackBerry Enterprise identity > Services to the OpenID Connect-Apps.

    03. Source system selection for the source system BlackBerry UEM Cloud

    When you setup a migration project with the EBF Onboarder, you will be asked to define the source system (please read the general documentation to learn more about this).

    Select BlackBerry UEM Cloud as target system. The EBF Onboarder will display a set of values which are required to connect to your BlackBerry UEM Cloud system: Host, BlackBerry Tenant Id, BlackBerry Client Id, BlackBerry Client Secret, BlackBerry eId.

    Please check the table below to find the parameters:

    ParameterLocation
    BlackBerry UEM ClientBlackBerry myAccount >> ‚BlackBerry Support Community‘ >> ‚My Organization‘ >> ‚Overview‘ >> ‘Applications’ >> Open your client app
    Host‘BLACKBERRY PLATFORM APIS’ >> ‘CLIENT’: Redirect URL, without https://
    BlackBerry Tenant Id‘BLACKBERRY PLATFORM APIS’ >> ‘CLIENT >> Tenants:
    A tenant within ‘Selected’ can be used (S only + number, not SRP).
    BlackBerry Client Id‘BLACKBERRY PLATFORM APIS’ >> ‘CLIENT’: Client Id
    BlackBerry Client Secret‘BLACKBERRY PLATFORM APIS’ >> ‘CLIENT’: Client Secret
    BlackBerry eIdhttps://idp.blackberry.com

    04. Device selection for the source system BlackBerry UEM Cloud

    When you setup a migration project with the EBF Onboarder, you will be asked to select the devices you want to migrate (please read the general documentation to learn more about this).

    A filter for the devices needs to be already existing or needs to be created in the source system before you setup the migration project. For the first tests you can use a test filter. For the real migration it is recommended to create filters like wave1, wave 2 etc. and to create single migration sets to have control over each wave.

     

    Was this article useful?

    Still stuck? How can we help?

    How can we help?

    Updated on 11. Dezember 2024
    Source System Ivanti EPMM Neurons / MobileIron Core and Cloud and Ivanti EPM (Landesk)Source System Blackberry UEM v12
    Table of Contents
    • 01. Introduction
    • 02. Prerequisites for the source system BlackBerry UEM Cloud
      • 02.1. Create a client app
    • 03. Source system selection for the source system BlackBerry UEM Cloud
    • 04. Device selection for the source system BlackBerry UEM Cloud
    Linkedin-in Phone
    Workplace Management
    • UEM Solutions
    • Migrations
    • Services
    Modern Work Tools
    • Sync Contacts
    • Hybrid Data Management
    • Secure Mobile Printing
    • eSIM Management
    • App Management
    IT Security
    • IAM
    • Modern Threat Defense
    • Cyber Risk Management
    • Secure Development
    • Zero Trust
    • Security Check
    AI Solutions
    • AI Consulting
    • AI Development
    Company
    • About Us
    • References
    • Partners
    • Sustainability
    • Careers
    • Trends
    © 2026 EBF-EDV Beratung Föllmer GmbH
    • Privacy Policy
    • GTC
    • EULA
    • Imprint
    Manage Consent
    To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Immer aktiv
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    • Optionen verwalten
    • Dienste verwalten
    • Verwalten von {vendor_count}-Lieferanten
    • Lese mehr über diese Zwecke
    View preferences
    • {title}
    • {title}
    • {title}
    EBF Status Check