GlobalProtect 5.0 for iOS 12 and User Certificates

[MarkRosenecker]

I have several customers (and my homelab) that leverage user certificates issued from Active Directory Certificate Authorities as a second authentication factor.  Since upgrading to the new 5.0 client for iOS, the client errors out on connection to the portal, indicating that the required certificate cannot be found.  If I attempt to connect to the same portal via the 4.1 client, it works flawlessly.  Upgrading to iOS12 prevents me from using the 4.1 client, and I fear that many of my customers' users will upgrade their own devices to iOS12, not knowing the problems this may cause.

Is anyone else having problems with user certificates and the new 5.0 client?

Thanks!

Mark Rosenecker

[gwesson · Accepted solution]

This is expected, because of the way Apple changed the way certificates are handled in iOS 12 compared with 11 and older.

The new features guide talks about it under the "Authentication

https://www.paloaltonetworks.com/documentation/50/globalprotect/globalprotect-app-new-features/new-f...

The location of the certificates in iOS 11 is different than iOS 12, so you'll need to re-import the certs. The steps are different for admins who manage their devices with an MDM versus unmanaged devices.

[gwesson · Accepted solution]

This is expected, because of the way Apple changed the way certificates are handled in iOS 12 compared with 11 and older.

The new features guide talks about it under the "Authentication

https://www.paloaltonetworks.com/documentation/50/globalprotect/globalprotect-app-new-features/new-f...

The location of the certificates in iOS 11 is different than iOS 12, so you'll need to re-import the certs. The steps are different for admins who manage their devices with an MDM versus unmanaged devices.

[sarao]

For MDM based client certificate deployments, please refer to the following link for more details:

https://www.paloaltonetworks.com/documentation/50/globalprotect/globalprotect-app-new-features/new-f...

These changes were pre-announced in July 2018 on live articles and also as part of GP App 5.0 Beta program.

[MarkRosenecker]

Thank you, gwesson!  That was a very helpful post!  I will re-import my certs and check again.

I had only become aware of the new client when the old client had an "update".  When run on iOS 11, it exhibited the same problem (which makes sense, if it's looking in a non-existant location for the certs).  I chalked it up to a .0 bug.

[MarkRosenecker]

Sarao,

I appreciate your reply, but there are a few things:

1) I'm not using an MDM, so that portion is not applicable to me (or my customers).

2) I never saw any pre-announcement about GP 5.0, and I'm a platinum partner, a CNSE (before it was called PCNSE) since 2012, and multiple-PSE certified engineer.  I was also at SKO a few weeks ago as well, and I didn't hear a thing about it.  Granted, I don't spend my days whiling away on Live Communities...

3) I obviously wasn't part of the beta program (otherwise I'd have found this problem long ago and resolved it).

Perhaps I was reading too much into your reply (it is 10pm, and I've been up since 3am), but there was a condescending tone to it that I did not appreciate.  If I am wrong, I am sorry for my misinterpretation.  If I am right, please exhibit more tact in the future, when addressing other professionals.

Thank you!

[icartwright]

Hello all,

Can someone detail the steps they took to "reimport" the certificates for an unmanaged iOS device? I reimported the certs I use for Global Protect and I still can't authenticate to my Gateway. I used the same steps to import the certs that I've always used: email the certs to myself; import in this order: CA, Intermediate, Client; trust the CA under Settings>General>About>Certificate Trust Settings. I still get the same error I was getting before:

GlobalProtect gateway user authentication failed. Login from: xxx.xxx.xxx.xxx, Source region: US, User name: , Client OS version: Apple iOS 12.0, Reason: client cert not present, Auth type: profile.

BTW: I use two-factor auth in the form of local username/password and a shared client certificate.

Thanks.

[MickBall]

Hi @icartwright, yeah, me too....

i have upgraded to ios 12 and gp 5 and removed all certs and re emailed and installed.

GP is stating no client certificate found but when i browse to my portal via safari it accepts the cert.

please update if you manage to resolve.

thanks.

[gwesson]

Yep, emailing them won't work anymore. Apple removed the ability for VPN applications to access certs that are emailed as a standalone file (.p12, for example). The portal works from Safari because it's not initiating a VPN tunnel, so it can access the keystore.

You can deploy them using Apple Configurator in a .mobileconfig file, which CAN be emailed to be installed.

It's a pain, but it's universal with all VPN apps in iOS 12 (not just GlobalProtect).

[MickBall]

@gwesson, hi.

many thanks for your reply and information, 

not really a pain as all our ipads are sent profiles via the cofigurator.

i was just playing with mine and i usually test cert auth by email.

i can of course still do this via safari but will now ensure that when our ipads are upgraded to V5 a new profile will follow.

once again, many thanks for your time and prompt reply.

[MarkRosenecker]

So, that essentially means that I (and my customers) need to have a Mac or an MDM system, in order to distribute certificates.  That totally, utterly sucks.

#HackintoshTime

Thanks again, gwesson!  You've been an immeasurable help!

---

@gwesson wrote:

Yep, emailing them won't work anymore. Apple removed the ability for VPN applications to access certs that are emailed as a standalone file (.p12, for example). The portal works from Safari because it's not initiating a VPN tunnel, so it can access the keystore.

You can deploy them using Apple Configurator in a .mobileconfig file, which CAN be emailed to be installed.

It's a pain, but it's universal with all VPN apps in iOS 12 (not just GlobalProtect).

---