Configure Kerberos Single Sign-On
Palo Alto Networks firewalls and Panorama support Kerberos V5 single sign-on (SSO) to authenticate administrators to the web interface and end users to Captive Portal. With Kerberos SSO enabled, the user needs to log in only for initial access to your network (such as logging in to Microsoft Windows). After this initial login, the user can access any browser-based service in the network (such as the firewall web interface) without having to log in again until the SSO session expires.
- Create a Kerberos keytab.The keytab is a file that contains the principal name and password of the firewall, and is required for the SSO process. When you configure Kerberos in your Authentication Profile and Sequence, the firewall first checks for a Kerberos SSO hostname. If you provide a hostname, the firewall searches the keytabs for a service principal name that matches the hostname and uses only that keytab for decryption. If you do not provide a hostname, the firewall tries each keytab in the authentication sequence until it is able to successfully authenticate using Kerberos.If the Kerberos SSO hostname is included in the request sent to the firewall, then the hostname must match the service principal name of the keytab; otherwise, the Kerberos authentication request is not sent.
- Log in to the Active Directory server and open a command prompt.
- Enter the following command to register the service principal name (SPN) for GlobalProtect or Captive Portal, where<portal_fqdn>and<service_account_username>are variables.setspn -s HTTP/<portal_fqdn><service_account_username>
- Create Kerberos account for the firewall. Refer to your Kerberos documentation for the steps.
- Log in to the KDC and open a command prompt.
- Enter the following command, where<portal_fqdn>,<kerberos_realm>,<netbios_name>,<service_account_username>,<password>,<filename>, and<algorithm>are variables.The<kerberos_realm>value must be in all uppercase characters (for example, enterAD1.EXAMPLE.COM, notad1.example.com).ktpass /princ HTTP<portal_fqdn>@<kerberos_realm>/mapuser<netbios_name>\<service_account_username>/pass<password>/out<filename>.keytab /ptype KRB5_NT_PRINCIPAL /crypto<algorithm>If the firewall is in FIPS/CC mode, the algorithm must beaes128-cts-hmac-sha1-96oraes256-cts-hmac-sha1-96. Otherwise, you can also usedes3-cbc-sha1 or arcfour-hmac. To use an Advanced Encryption Standard (AES) algorithm, the functional level of the KDC must be Windows Server 2008 or later and you must enable AES encryption for the firewall account.The algorithm in the keytab must match the algorithm in the service ticket that the TGS issues to clients. Your Kerberos administrator determines which algorithms the service tickets use.
- Configure an Authentication Profile and Sequence to define Kerberos settings and other authentication options that are common to a set of users.
- Enter theKerberos Realm(usually the DNS domain of the users, except that the realm is uppercase).
- ImporttheKerberos Keytabthat you created for the firewall.
- Assign the authentication profile to the firewall application that requires authentication.
- Administrative access to the web interface—Configure a Firewall Administrator Account and assign the authentication profile you configured.
- End user access to services and applications—Assign the authentication profile you configured to an authentication enforcement object. When configuring the object, set theAuthentication Methodtobrowser-challenge. Assign the object to Authentication policy rules. For the full procedure to configure authentication for end users, see Configure Authentication Policy.
Recommended For You
Recommended videos not found.