This website uses Cookies. By clicking Accept, you agree to the storing of cookies on your device to enhance your community and translation experience. Read our Privacy Policy.
Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Who rated this post

tcleghorn
L1 Bithead

‎07-23-2020 05:30 PM

This is by design.  If you allow a user to connect using Credential OR Client Cert, we'd need a username from the client cert.

 

A workaround is to set the User Name in the Certificate Profile to using the Subject Alt Name of the Certificate.  When you generate the Machine Certificate for the Pre-Logon, do NOT put anything in the Subject Alt Name field.  This should allow both Machine Cert users (without Cookies) and non-Machine Cert users.

 

Best practice would be to set-up 2 Portals and 2 Gateways.  One with the CertProfile (for your domain trusted machines) and one without (for your contractors).

(1)
Who rated this post
LEGAL NOTICES
RESOURCES
Khoros awards 2022
Copyright 2007 - 2024 - Palo Alto Networks