From 02f808a998419a93e60ad48a85978bcb4f2aaaaa Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Fri, 10 May 2024 13:03:57 -0700 Subject: [PATCH] Updating after review and syncing versions. Signed-off-by: Sunil Singh --- docs/api/api-tokens.md | 2 +- docs/api/quickstart.md | 2 +- versioned_docs/version-2.8/api/api-tokens.md | 4 +--- versioned_docs/version-2.8/api/quickstart.md | 2 +- 4 files changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/api/api-tokens.md b/docs/api/api-tokens.md index 6552eca4156..fa5c797ab3d 100644 --- a/docs/api/api-tokens.md +++ b/docs/api/api-tokens.md @@ -49,7 +49,7 @@ Set the `kubeconfig-generate-token` setting to `false`. This setting instructs R ## Token Hashing -You can [enable token hashing](../how-to-guides/advanced-user-guides/enable-experimental-features/enable-experimental-features.md), where tokens undergo a one-way hash using the SHA256 algorithm. This is a non-reversible process: once enabled, this feature cannot be disabled. It is advisable to take backups before enabling and/or evaluating in a test environment first. +You can [enable token hashing](../how-to-guides/advanced-user-guides/enable-experimental-features/enable-experimental-features.md), where tokens undergo a one-way hash using the SHA256 algorithm. This is a non-reversible process: once enabled, this feature cannot be disabled. You should first evaluate this setting in a test environment, and/or take backups before enabling. This feature affects all tokens which include, but are not limited to, the following: diff --git a/docs/api/quickstart.md b/docs/api/quickstart.md index 2b215857a39..5bb3057183e 100644 --- a/docs/api/quickstart.md +++ b/docs/api/quickstart.md @@ -129,7 +129,7 @@ To ensure that your tools can recognize Rancher's CA certificates, most setups r If your Rancher instance is proxied by another service, you must extract the certificate that the service is using, and add it to the kubeconfig file, as demonstrated in step 5. ::: -4. The following commands convert `rancher.crt` to base64 output, trim all new-lines, and update the cluster in the kubeconfig with the certificate, then finishing by removing the `rancher.crt` file: +4. The following commands convert `rancher.crt` to base64 output, trim all new-lines, and update the cluster in the kubeconfig with the certificate, then finish by removing the `rancher.crt` file: ```bash export KUBECONFIG=$PATH_TO_RANCHER_KUBECONFIG diff --git a/versioned_docs/version-2.8/api/api-tokens.md b/versioned_docs/version-2.8/api/api-tokens.md index 75aa6307fee..ae51e67aa93 100644 --- a/versioned_docs/version-2.8/api/api-tokens.md +++ b/versioned_docs/version-2.8/api/api-tokens.md @@ -49,9 +49,7 @@ Set the `kubeconfig-generate-token` setting to `false`. This setting instructs R ## Token Hashing -Users can enable token hashing, where tokens undergo a one-way hash using the SHA256 algorithm. This is a non-reversible process: once enabled, this feature cannot be disabled. It is advisable to take backups before enabling and/or evaluating in a test environment first. - -To enable token hashing, refer to [this section](../how-to-guides/advanced-user-guides/enable-experimental-features/enable-experimental-features.md). +You can [enable token hashing](../how-to-guides/advanced-user-guides/enable-experimental-features/enable-experimental-features.md), where tokens undergo a one-way hash using the SHA256 algorithm. This is a non-reversible process: once enabled, this feature cannot be disabled. You should first evaluate this setting in a test environment, and/or take backups before enabling. This feature affects all tokens which include, but are not limited to, the following: diff --git a/versioned_docs/version-2.8/api/quickstart.md b/versioned_docs/version-2.8/api/quickstart.md index 2b215857a39..5bb3057183e 100644 --- a/versioned_docs/version-2.8/api/quickstart.md +++ b/versioned_docs/version-2.8/api/quickstart.md @@ -129,7 +129,7 @@ To ensure that your tools can recognize Rancher's CA certificates, most setups r If your Rancher instance is proxied by another service, you must extract the certificate that the service is using, and add it to the kubeconfig file, as demonstrated in step 5. ::: -4. The following commands convert `rancher.crt` to base64 output, trim all new-lines, and update the cluster in the kubeconfig with the certificate, then finishing by removing the `rancher.crt` file: +4. The following commands convert `rancher.crt` to base64 output, trim all new-lines, and update the cluster in the kubeconfig with the certificate, then finish by removing the `rancher.crt` file: ```bash export KUBECONFIG=$PATH_TO_RANCHER_KUBECONFIG