![]() ![]() This involves removing the assignment (or deployment for hybrid MDM) and then re-assigning (re-deploying) the certificate again to the same groups. For issues where the authentication certificate is shared between Pulse Secure and different apps, and the other apps lose access to the certificate, you will need to re-deploy the certificate. When users update to Pulse Secure 7.0.0 for iOS or Check Point Capsule Connect versions 1.600 for iOS, the updated VPN client may not read the authentication certificate and will instead report that the certificate is not found on the device - even if the certificate already exists.Īlso, if you are using the same authentication certificate for Pulse Secure as for other apps, those apps may lose access to the certificate when Pulse Secure is updated to version 7.0.0. This impacts both Intune on Azure and hybrid mobile device management (MDM) tenants. ![]() This impacts you if you are deploying Pulse Secure or Check Point Capsule Connect VPN profiles for iOS that use certificate-based authentication. These issues impact Intune in addition to other Enterprise Mobility Management providers.Ībout this that includes some workarounds and is working with Apple to resolve the issues as soon as possible. Specifically, both VPN clients may report that the certificate is missing from the device, even when the certificate has been properly delivered. There are issues with certificate-based authentication when using the Pulse Secure VPN client for iOS, version 7.0 and Check Point Capsule Connect version 1.600 for iOS. First published on TechNet on Sep 15, 2018 ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |