@Mick_Ball I reviewed your post, and double checked everything. Thank you for the replies. I found that the agent itself works when I install to (Local Computer)-Personal. This appears to work for the global protect agent flawlessly. It's a bit misleading to me though, as when I try to browse directly to the portal (which I was originally trying to do) I get a warning that says "Valid client certificate is required" (and an auth failure, if typing in known good credentials)- however, the Global protect agent itself works perfectly. This must be because I'm launching a web browser as a current user of the computer, and the GP agent has access to a different store? This is where my confusion was all along. How could I be getting a warning "Valid client certificate required" - and denied authentication, when web-browsing to the portal, if I wasn't missing the certificate? Well, the GP agent says otherwise. If this is the case, how are people using the portal to allow machines that may not have the agent (someone inside the org, but offsite), to web browse to the portal, download the agent and install it? I'm guessing using a publicly signed CA certificate may solve this issue? Or maybe they are just requiring the certificate authentication on their gateways and NOT the portal?
... View more