On Android, when running a Blue Cedar-secured app that uses WebView on a pre-Lollipop device (KitKat (4.4–4.4.4) and earlier), not all Secure Web Stack features are available. This is because some underlying WebView Android APIs required by Blue Cedar were not introduced until the later Android OS releases. In this article, we list the Secure Web Stack limitations when run on these older devices.
The following limitations apply when a secured app is run on an Android pre-Lollipop device:
- Automatic PAC file settings are not used. Instead, a separate proxy configuration for Android pre-Lollipop devices must be used on these older Android OS versions.
- Proxy authentication is not supported. If a proxy that requires authentication is specified, when the user loads a web page via a WebView, the user is prompted for authentication.
- Client Certificate authentication is not supported. In a secured app's WebView, if a user attempts to load a URL that requires client-side certificate authentication, the web page may not load correctly and the browser may display "web page not available."
- A static fallback proxy must be configured when setting up Automatic proxy. Otherwise, when the app is run on a pre-Lollipop device and the user launches an Android WebView, it is possible that network access will be limited and some web pages may not load correctly.