From eeac744361258f98a6f72c96f593066923a3e529 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Mon, 15 Sep 2025 08:11:03 -0700 Subject: [PATCH] Fix broken link --- .../rancher-security/rancher-security-best-practices.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/reference-guides/rancher-security/rancher-security-best-practices.md b/docs/reference-guides/rancher-security/rancher-security-best-practices.md index 5b67aede622..9ffb4ca0978 100644 --- a/docs/reference-guides/rancher-security/rancher-security-best-practices.md +++ b/docs/reference-guides/rancher-security/rancher-security-best-practices.md @@ -44,8 +44,11 @@ Examples of potential baseline policies include: Without these controls at the identity provider layer, there is a risk of inconsistent or insecure username practices, which can complicate access audits and lead to privilege escalation attempts. -> [!IMPORTANT] -> Rancher currently enforces only a [minimum password length](../../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/manage-users-and-groups#minimum-password-length.md) +:::note Important + +Rancher currently enforces only a [minimum password length](../../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/manage-users-and-groups.md#minimum-password-length). + +::: **Recommendation:** We strongly advice that customers: