Known issues in BlackBerry Access Secure Enterprise Browser
|
When you update the allowed domains in a BlackBerry Dynamics connectivity profile, BlackBerry Access Secure Enterprise Browser doesn't apply the changes until the user restarts the app. A domain that you configure to deny access might still be accessible to users until they restart the app. (BBDA-707) Workaround: Instruct users to restart BlackBerry Access Secure Enterprise Browser after you update the connectivity profile. |
|
When you disable "Trusted Certificate Authorities" in the BlackBerry Dynamics profile and you don't assign a certificate authority to the user in BlackBerry UEM, BlackBerry Access Secure Enterprise Browser still trusts certificate authorities from the Windows certificate store. Users don't receive an insecure connection warning for sites that the Windows certificate store trusts as legitimate. (BBDA-698) |
|
When you view a user certificate that is installed in BlackBerry Access Secure Enterprise Browser, the Device column in the UEM management console displays "WP_unknown Windows Desktop (Windows Desktop)" instead of the Windows device name. (BBDA-636) |
|
In the BlackBerry Access Secure Enterprise Browser app configuration, on the Extensions tab, if you select "Enable installation of extensions" and configure an extension with "installation_mode" set to "force_installed" in the "Advanced Extension Management" field, the extension doesn't installed automatically. (BBDA-559) Workaround: Instruct users to manually install the extension. |
When a device user tries to remove BlackBerry Access from the Windows Settings, the uninstaller displays an unknown publisher instead of BlackBerry Limited. The correct publisher information displays in the installer. (BBDA-579) |
When users change the zoom level in document view mode, the file view mode does not display the file as expected. (BBDA-573) Workaround: Refresh the page. |
When proxy connectivity settings are configured, resources in Microsoft Outlook or Microsoft Teams fail to load or load with significant delays. (BBDA-62) Workaround: Verify that the resources load over the Internet and do not go through a proxy server. |