I have implemented global protect with pre-logon (device certificate) followed by user logon using SAML (Azure AD as SAML IDP)
When global protect client initiate the user authentication below windows security pop up asking to confirm the certificate.
After confirming the certificate it connects fine and every time user reboot same pop up box comes up, if I replace the SAML auth with LDAP auth, I don't get any pops for certificate and everything works fine.
I have client certificate profile (internal Root and Intermediate CA) attached to client profile in each scenario ( LDAP auth vs SAML)
Also note that pre-logon works fine on each scenario and I can see before login to the machine globalprotect shows connected.
Has anyone come across this or similar issue?
I'm not sure if this applies in your case, but I saw something similar when a user had two client certificates which matched the certificate profile. We solved it by deleting one of the unneeded certificates.
I have seen this similar behaviour in our setup.
We also have GP pre logon with machine cert and then SAML Azure authentication.
That cert pop message is for the certificate to sign SAML messages to IDP and we select that in Authentication profile.
Do you have more than 1 certs issued by your Intermediate Certs.?
either way you need to have SSL/TLS profile cert trusted by either your Internal PKI or external certificate authority.
It needs same CA cert signed by the above one which your PC also trusts.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!