Prerequisites for configuring KCD for BlackBerry Dynamics apps

Item

Description

Active Directory port

Port 88 on the Active Directory service must be accessible by all BlackBerry UEM servers.

Kerberos environment

The Kerberos environment must include the following components:
  • Microsoft Active Directory server: The directory service that authenticates and authorizes all users and computers associated with your Windows network.
  • Kerberos Key Distribution Center (KDC): The authentication service on the Active Directory server that supplies session tickets and keys to users and computers in the Active Directory domain.

To use KCD with Microsoft 365 resources, the on-premises Active Directory domain must be integrated with Entra. For more information, see Microsoft Entra Cloud Sync supported topologies and scenarios.

RC4 deprecation

Microsoft is deprecating RC4-based Kerberos ticket issuance and is moving Active Directory environments to AES-only operation. To ensure compatibility with these hardened environments, UEM supports the transition from the current PA-FOR-USER mechanism to the new PA-S4U-X509-USER mechanism for S4U identity assertion.

For more information about this change and the requirements for your KCD configuration, see the following Microsoft resources:

By default, UEM uses the existing PA-FOR-USER mechanism until you change a setting in the management console (Settings > BlackBerry Dynamics > Global properties > Identity assertion mode) to switch to the new PA-S4U-X509-USER mechanism. For more information, see Configure KCD for BlackBerry Dynamics apps.

krb5.conf file

Your UEM environment requires a krb5.conf file with values specific to your KDC. The file must include the following [libdefaults] settings:

[libdefaults]
    forwardable = true

Generate the keytab file using AES encryption by specifying either /crypto AES128-SHA1 or /crypto AES256-SHA1 in the ktpass command. Support for the PA-S4U-X509-USER identity assertion mechanism requires the use of an AES-encrypted keytab file.

ktpass /out outfilename.keytab /mapuser kerberos_account@REALM_IN_ALL_CAPS /princ GCSvc/UEM@REALM_IN_ALL_CAPS /pass kerberos_account_password /ptype KRB5_NT_SRV_HST /crypto AES256-SHA1

The value you specify for /princ must be a unique SPN in the domain that will be associated with the service account when the keytab file is created.

You must specify the location of the krb5.conf file in Settings > BlackBerry Dynamics > Properties (see Configure KCD for BlackBerry Dynamics apps). For more information about constructing a krb5.conf file, see the MIT Kerberos Documentation.

Service Principal Names (SPN)

Create SPNs for all HTTP services, including the BlackBerry Enterprise Mobility Server. You must set an SPN for every target resource you want devices to have access to.

For more information about how to create and modify SPNs, see Register a Service Principal Name for Kerberos Connections.

Multi-realm Kerberos environments

  • A minimum of one UEM Core must be installed in each Kerberos realm. UEM must reside in the same Kerberos realm as the resource because cross-realm resource delegation is not supported.
  • Ensure that single-realm KCD is working before configuring multi-realm KCD.
  • All trusts must be bidirectional, transitive forest trusts.
  • Ensure a maximum of 5 ms latency between the UEM Core instances and the Microsoft SQL Server database.
  • For each UEM Core instance, use a separate service account with its own unique SPN set and generated keytab file (you can reuse the same account and keytab file on other UEM servers in the same realm).