KB44267 - Known Issues for iOS 13 and iPadOS 13
KB43813 - Certificate authentication fails with error "Missing or Invalid Certificate" or other applications that rely on certificate authentication may fail after upgrading to the Pulse Mobile 7.0.0 for iOS
SA44101 - 2019-04: Out-of-Cycle Advisory: Multiple vulnerabilities resolved in Pulse Connect Secure / Pulse Policy Secure 9.0RX
KB43862 - Certificate authentication fails for unmanaged devices (no MDM/EMM profile) with error "Missing or Invalid Certificate" after upgrading to Pulse Mobile for iOS 7.0.0
KB44266 - After upgrading to iOS 13, end user is unable to connect to the Pulse Connect Secure (PCS) with the error message of "Server is not responding"
KB43870 - Create VPN profile for Network Extension for Pulse Mobile for iOS 7.0.0
KB44113 - Pulse iOS client : Unable to connect using Pulse Secure Mobile client for iOS 18.104.22.168829 & above
SA40312 - September 22 2016 OpenSSL Security Advisory
KB43871 - How to repush iOS profiles using MobileIron where iOS apps that authenticate with certificates stop working after upgrading to Pulse mobile for iOS 7.0
KB40512 - HOB JWT Administration Guide for Java RDP Applet parameter values
What would you like to know?
< Back to search results
KB44268 - Unable to import certificates using shared extension from Native Email (iOS 13) to Pulse Mobile Client
Last Modified Date
9/19/2019 1:51 PM
This article describes an issue where the end user is unable to import certificates using shared extension from Native Email (iOS 13) to Pulse Mobile Client
Problem or Goal
This issue occurs due to a bug in iOS 13.
We are working with Apple on this issue, we will update the KB once we have further updates.
Use the another email client (i.e. Gmail app) and share the certificate to the Pulse Mobile Client.
Was this article helpful?
Please tell us how we can make this article more useful.