- What is BlackBerry Access?
- Getting started with BlackBerry Access
- Managing BlackBerry Access
- Making BlackBerry Access available to users
- Configuring BlackBerry Access app settings
- Configuring the BlackBerry Dynamics Launcher
- Whitelist the BlackBerry UEM App Catalog in the BlackBerry Dynamics Connectivity profile
- Configure single sign-on for BlackBerry Access in Good Control
- Configure single sign-on for BlackBerry Access in BlackBerry UEM
- Setting up a PAC file to manage a proxy infrastructure
- Configure RSA SecurID soft token authentication
- Kerberos authentication support
- Managing certificates
- Verify that BlackBerry Access can use certificates in BlackBerry UEM
- Verify that BlackBerry Access can use certificates in Good Control
- Upload certificates for users in BlackBerry UEM
- Upload certificates for users in Good Control
- Delete certificates for users in BlackBerry UEM
- Delete certificates for users in Good Control
- Security features
- Video support
- Configuring allowed Internet domains
- Changing communications protocols
- Configure access to WebRTC-based destinations
- Allow users to open custom URL schemes
- Allow users to securely edit files within an app in BlackBerry Access on Windows or macOS
- Identifying BlackBerry Access in user agent
- Good Control cloud deployments and intranet servers
- Using BlackBerry Analytics to collect app data
- Configure a compliance rule for Windows antivirus detection in Good Control
- Configure support for FQDN resolution in Good Control
- Troubleshooting
- Feature support
- Browser support for HTML5 and CSS3
NTLMv2 authentication
NTLMv2 is a challenge-response authentication protocol and a cryptographically
strengthened replacement for NTLMv1.
Kerberos
, which is
the preferred authentication protocol for Windows
and Microsoft Active
Directory
domains, is used when a server belongs to a Windows Server
domain or if a trust relationship with a Windows Server
domain is established in some other way, such as Linux
to Microsoft Active
Directory
authentication.NTLMv2 sends two 16-byte responses to an 8-byte server challenge. The two
responses are:
- The HMAC-MD5 hash of the server challenge, which is a randomly generated client challenge
- An HMAC-MD5 hash of the user's password and other identifying information
Active
Directory
,
and continues to hash in the username and domain name, using HMAC-MD5.