End-user issue #1
(cert auth failures within Pulse Mobile 7.0.0) occurs in deployments where there is no MDM/EMM profile on the iOS device (unmanaged end-user devices).
The root cause for this issue is that Pulse Mobile for iOS 7.0.0 leverages a new framework (Network Extension framework
) and there were no options within iOS that Pulse Secure could leverage to migrate the certificate to the new location as required by the new framework. This issue is not specific to Pulse Secure and impacts any vendor that migrates to the new framework, which is a requirement for iOS 12. More details on this topic are available at KB43801 - FAQ on NetworkExtension API Framework being used in Pulse iOS Client 7.0.0
End-User Issue #2
(i.e. Failures in other applications after upgrading to Pulse Secure Mobile client 7.0.0) occurs in deployments where the iOS device is managed using a MDM/EMM type product such as Mobile Iron, AirWatch, Pulse workspace, etc.
The root cause for this issue is that when Pulse Mobile for iOS 7.0.0 is installed, the underlying iOS components performs migration of certificates to the new locations. However, Pulse Secure have found that after Apple iOS performs this migration the client certificates are available for the Pulse Secure app to use, but they are no longer available to other applications that were previously using the certificate along with the Pulse Secure Mobile VPN app. This issue has been reported to Apple and Pulse Secure is working with Apple to find a resolution for this issue that manifests after upgrading the Pulse Secure App.