From ab606b6e510970f1daaf6d1c4dbd8de8fc4ff89f Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Thu, 31 Jul 2025 10:55:37 -0700 Subject: [PATCH] Updating broken link in /docs configure-oidc-provider.md page. Signed-off-by: Sunil Singh --- .../advanced-user-guides/configure-oidc-provider.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/advanced-user-guides/configure-oidc-provider.md b/docs/how-to-guides/advanced-user-guides/configure-oidc-provider.md index f96a4fb92aa..9f85fd52168 100644 --- a/docs/how-to-guides/advanced-user-guides/configure-oidc-provider.md +++ b/docs/how-to-guides/advanced-user-guides/configure-oidc-provider.md @@ -7,7 +7,7 @@ title: Configure Rancher as an OIDC provider Rancher can function as a standard OpenID Connect (OIDC) provider, allowing external applications to use Rancher for authentication. -This can be used for enabling single sign-on (SSO) across Rancher Prime components. For example, see the [documentation](https://documentation.suse.com/cloudnative/suse-observability/next/en/setup/security/authentication/oidc.html) for configuring the OIDC provider for SUSE Observability. +This can be used for enabling single sign-on (SSO) across Rancher Prime components. For example, see the [documentation](https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/oidc.html) for configuring the OIDC provider for SUSE Observability. The OIDC provider can be enabled with the `oidc-provider` feature flag. When this flag is on the following endpoints are available: