- 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 BlackBerry UEM
- Setting up a PAC file to manage a proxy infrastructure
- Configure RSA SecurID soft token authentication
- Kerberos authentication support
- Managing certificates
- 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
- Using BlackBerry Analytics to collect app data
- Troubleshooting
- Feature support
- Browser support for HTML5 and CSS3
- BlackBerry Docs
- BlackBerry Access 3.17
- BlackBerry Access Administration Guide
- Managing BlackBerry Access
- Security features
- HTTP basic authentication
HTTP basic authentication
HTTP basic authentication implementation is the simplest technique for enforcing
access controls to web resources because it doesn’t require cookies, session identifiers, or
login pages. Instead, HTTP basic authentication uses static, standard HTTP headers, which means
that no handshakes have to be done in anticipation.
However, the basic authentication mechanism provides no confidentiality
protection for the transmitted credentials. They are merely encoded with BASE64 in transit, but
not encrypted or hashed. Basic authentication should therefore only be used over HTTPS.