Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerScale OneFS 9.8.0.0 Web Administration Guide

Kerberos authentication

Kerberos is a network authentication provider that negotiates encryption tickets for securing a connection. OneFS supports Microsoft Kerberos and MIT Kerberos authentication providers on a cluster. If you configure an Active Directory provider, support for Microsoft Kerberos authentication is provided automatically. MIT Kerberos works independently of Active Directory.

For MIT Kerberos authentication, you define an administrative domain, also called a realm. Within this realm, an authentication server has the authority to authenticate a user, host, or service; the server can resolve to either IPv4 or IPv6 addresses. You can optionally define a Kerberos domain to allow additional domain extensions to be associated with a realm.

The authentication server in a Kerberos environment is called the Key Distribution Center (KDC) and distributes encrypted tickets. When a user authenticates with an MIT Kerberos provider within a realm, a cryptographic ticket-granting ticket (TGT) is created. The TGT enables user access to a service principal name (SPN).

Each MIT Kerberos provider is associated with a groupnet. The groupnet is a top-level networking container that manages hostname resolution against DNS nameservers. It contains subnets and IP address pools. The groupnet specifies which networking properties the Kerberos provider uses when it communicates with external servers. The groupnet associated with the Kerberos provider cannot be changed. Instead, delete the Kerberos provider and create it again with the new groupnet association.

You can add an MIT Kerberos provider to an access zone as an authentication method for clients connecting through the access zone. An access zone may include at most one MIT Kerberos provider. The access zone and the Kerberos provider must reference the same groupnet. You can discontinue authentication through an MIT Kerberos provider by removing the provider from associated access zones.

NOTE:Do not use the NULL account with Kerberos authentication. Using the NULL account for Kerberos authentication can cause issues.

Session ticket lifetimes

The duration of connections that are authenticated using Kerberos is based on the Kerberos ticket lifetime settings. These settings are controlled on the Kerberos Distribution Center (KDC). For information about configuring maximum lifetimes, see the appropriate provider documentation as shown in the following table.

SMB only checks ticket validity during initial authentication. As a result, SMB connections may remain valid and in use after Kerberos tickets expire. For information about immediately closing active SMB sessions, contact Dell Technologies Support.

Table 1. Provider TypesThe following table displays the specifications for each provider type.
Provider type Documentation for configuring maximum lifetimes
Microsoft Kerberos with Active Directory Domain Services See the following Microsoft documentation:
MIT Kerberos See the MIT Kerberos documentation for configuring the kdc.conf file. The max_life setting in kdc.conf controls the lifetime duration.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\