Original Publication Date: 10/31/2018
In November 2015, Apple posted the release of the iOS Edge Client version 2.0.6. Users should download this new version from the app store.
|468712||Edge Client in web logon mode now auto-populates and submits credentials if the server policy allows credentials caching and the user decides to cache them. Auto-submission of credentials or authentication is possible if the APM server policy allows cached credentials and is already cached at runtime. Auto-population of user name is possible if the policy allows only user names.|
|476958||If a fully qualified host is specified in the proxy bypass list, users navigating to the host using the short form make use of the proxy in iOS 7, but this bypasses the proxy on iOS 8. iOS 8 takes into account the DNS suffix for proxy bypass.|
|512960||When users trigger a VPN-on-Demand connection using Safari, it returns the following error message, Safari cannot open the page because the server cannot be found. This occurs even when users successfully establish the VPN tunnel and the VPN icon displays on the status bar. This works as designed. To work around this issue, refresh the page after establishing the VPN connection.|
|518576||After users trigger VPN-on-Demand, Safari displays the following error message, Safari could not open the page because the server stopped responding. Users fail to reach the internal resource until they refresh the web page. This only occurs when users try to reach a domain that ends in ".local."|
|552214||Previously, on iOS 9, the VPN tunnel might not establish a connection if users try to establish a connection immediately after disconnecting the VPN. This issue is resolved.|
|553707||Previously, on iOS 9, users could configure the network access resource to automatically launch an application after connecting to Edge Client. Sometimes, the application fails to reach internal resources through the VPN. This was due to a timing issue, when the application might prematurely launch before the VPN configuration finishes establishing a connection. This issue is resolved.|
|542760||Previously, Edge Client might crash when users attempt to send a log report. This issue is resolved.|
|516674||Previously, if users configured split tunneling in the network access resource, the "LAN address space" field was marked "required," while the "DNS Address Space" could be left blank. When "DNS Address Space" was left blank, Edge Client failed to pass DNS traffic through the VPN tunnel.
Now, to resolve internal addresses with the DNS servers specified in the network access resource, if users select the Use split tunneling for traffic option, they must specify either a DNS suffix or DNS Address Space pattern to use the VPN DNS servers. If the "DNS Suffix" and the "DNS Address Space" fields are both left blank, then Edge Client does not use the VPN DNS servers and sends all DNS traffic to public DNS servers.
The documentation for this feature was modified to provide further clarification.
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.