From a596ea5c6a588d62453e8297dfb70cc9bf58ae5e Mon Sep 17 00:00:00 2001 From: "Michael G. Khmelnitsky, Ph.D" Date: Wed, 10 Jan 2024 15:44:23 -0800 Subject: [PATCH] Update kerberos-additional-cluster-configuration.md --- .../kerberos/kerberos-additional-cluster-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_includes/content-reuse/admin-guides/kerberos/kerberos-additional-cluster-configuration.md b/_includes/content-reuse/admin-guides/kerberos/kerberos-additional-cluster-configuration.md index bf9c1d548..267e5452c 100644 --- a/_includes/content-reuse/admin-guides/kerberos/kerberos-additional-cluster-configuration.md +++ b/_includes/content-reuse/admin-guides/kerberos/kerberos-additional-cluster-configuration.md @@ -50,7 +50,7 @@ Qumulo provides configuration for the permitted NFSv4.1 authentication flavors i {{site.data.alerts.note}} @@ -62,4 +62,4 @@ You can use [NFSv4.1 exports](../nfs/nfsv4.1-enabling-using.html) to configure a The user-mapping portion of the export configuration has no effect on Kerberos configuration. Specifying `root` or `any` user mapping for a particular export applies only to `AUTH_SYS` mounts that access this export. -Otherwise, exports and IP address restrictions (that you specify in exports) behave identically for all authentication flavors: `AUTH_SYS`, `AUTH_KRB5`, `AUTH_KRB5P`, and `AUTH_KRB5I`. +Otherwise, exports and IP address restrictions (that you specify in exports) behave identically for all [Kerberos security flavors](../kerberos/kerberos-with-qumulo-core.html#choosing-a-kerberos-security-flavor): `AUTH_SYS`, `AUTH_KRB5`, `AUTH_KRB5P`, and `AUTH_KRB5I`.