From f7cacfa771753fb63299808fb33ad70d52b55dc2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Corentin=20N=C3=A9au?= Date: Thu, 25 Sep 2025 11:50:31 +0200 Subject: [PATCH] Clarify requirements on token-based auth (#334) Github and BitBucket are special cases, now supported. --- docs/gitrepo-add.md | 3 +++ docs/troubleshooting.md | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/gitrepo-add.md b/docs/gitrepo-add.md index f0af670e3..c7c5974a1 100644 --- a/docs/gitrepo-add.md +++ b/docs/gitrepo-add.md @@ -158,6 +158,9 @@ Just like with SSH, reference the secret in your GitRepo resource via `clientSec branch: main clientSecretName: basic-auth-secret +:::info +When using BitBucket and access tokens, the username must be `x-token-auth`. +::: ### Using Custom CA Bundles diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 32b3e9f58..dd653e9f9 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -165,7 +165,7 @@ done ; wait When testing Fleet with private git repositories, you will notice that HTTP secrets are no longer supported in Github. To work around this issue, follow these steps: 1. Create a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) in Github. -1. In Rancher, create an HTTP [secret](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets) with your Github username. +1. In Rancher, create an HTTP [secret](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets) with your Github personal access token. Your username is optional. 1. Use your token as the secret. ### Fleet fails with bad response code: 403