From 15d0986125e4ec6c1208d269df46767785372492 Mon Sep 17 00:00:00 2001 From: Rhuan Barreto Date: Fri, 23 Oct 2026 19:33:03 +0200 Subject: [PATCH 1/4] docs: state that beta ag_beta_ plugin tokens are not accepted Signed-off-by: Rhuan Barreto --- docs/public/llms-full.txt | 2 +- docs/src/content/docs/nb/reference/cli/login.mdx | 2 +- docs/src/content/docs/pt-br/reference/cli/login.mdx | 2 +- docs/src/content/docs/reference/cli/login.mdx | 2 +- src/helpers/sentry.ts | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/public/llms-full.txt b/docs/public/llms-full.txt index 0c1af587..5643b19e 100644 --- a/docs/public/llms-full.txt +++ b/docs/public/llms-full.txt @@ -4730,7 +4730,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Access tokens are short-lived. The CLI keeps a refresh token alongside them and renews the access token automatically, so signing in once is normally enough. If the refresh token itself expires or is revoked, the CLI reports that the session has expired, and `archgate login` re-establishes it. A token issued before this flow existed keeps working only until you sign in to the platform; from then on the platform session alone decides. +Access tokens are short-lived. The CLI keeps a refresh token alongside them and renews the access token automatically, so signing in once is normally enough. If the refresh token itself expires or is revoked, the CLI reports that the session has expired, and `archgate login` re-establishes it. Plugin tokens from the beta sign-up (`ag_beta_…`) are not accepted by `plugins.archgate.dev`; run `archgate login` to replace one with a platform session. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/nb/reference/cli/login.mdx b/docs/src/content/docs/nb/reference/cli/login.mdx index 8128cc02..27274c5c 100644 --- a/docs/src/content/docs/nb/reference/cli/login.mdx +++ b/docs/src/content/docs/nb/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starter en OAuth 2.0 Device Authorization Grant (RFC 8628) mot Archgate-plattfor Ingen av delene er påkrevd. I CI, over SSH eller på en ren Linux-maskin uten skjermserver (WSL når Windows-skrivebordet) hopper CLI-en over begge og skriver dem bare ut. Når autorisasjonen er fullført, gir CLI-en tokenene til git via `git credential approve`, så hvor de havner avhenger av hvilken credential-helper du har konfigurert. En helper som bruker operativsystemets legitimasjonsbehandler (macOS Keychain, Windows Credential Manager, Linux libsecret) holder dem krypterte; gits innebygde `store`-helper skriver dem til `~/.git-credentials` i klartekst. Sjekk din med `git config --global credential.helper`. -Tilgangstokener er kortlivede. CLI-en beholder et refresh-token ved siden av dem og fornyer tilgangstokenet automatisk, så det holder normalt å logge inn én gang. Hvis selve refresh-tokenet utløper eller blir tilbakekalt, melder CLI-en at økten er utløpt, og `archgate login` gjenoppretter den. Et token utstedt før denne flyten fantes virker bare til du logger inn på plattformen; fra da av er det plattformøkten alene som gjelder. +Tilgangstokener er kortlivede. CLI-en beholder et refresh-token ved siden av dem og fornyer tilgangstokenet automatisk, så det holder normalt å logge inn én gang. Hvis selve refresh-tokenet utløper eller blir tilbakekalt, melder CLI-en at økten er utløpt, og `archgate login` gjenoppretter den. Plugin-tokener fra beta-registreringen (`ag_beta_…`) godtas ikke av `plugins.archgate.dev`; kjør `archgate login` for å erstatte et slikt token med en plattformøkt. Innlogging registrerer også `archgate credential` som en git credential helper for `plugins.archgate.dev`, som er det som lar `git clone` av et plugin-repositorium autentisere uten å spørre. Se [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/pt-br/reference/cli/login.mdx b/docs/src/content/docs/pt-br/reference/cli/login.mdx index 932a5384..427e40a1 100644 --- a/docs/src/content/docs/pt-br/reference/cli/login.mdx +++ b/docs/src/content/docs/pt-br/reference/cli/login.mdx @@ -13,7 +13,7 @@ Inicia um OAuth 2.0 Device Authorization Grant (RFC 8628) na plataforma Archgate Nenhuma das duas etapas é obrigatória. Em CI, via SSH ou em uma máquina Linux nativa sem servidor gráfico (o WSL alcança a área de trabalho do Windows), a CLI pula ambas e apenas os exibe. Após a autorização, a CLI entrega os tokens ao git via `git credential approve`, então onde eles ficam depende do credential helper que você tem configurado. Um helper apoiado no gerenciador de credenciais do sistema operacional (macOS Keychain, Windows Credential Manager, libsecret no Linux) os mantém criptografados; o helper `store` embutido do git os grava em `~/.git-credentials` em texto puro. Verifique o seu com `git config --global credential.helper`. -Os tokens de acesso têm vida curta. A CLI mantém um refresh token junto deles e renova o token de acesso automaticamente, então normalmente basta entrar uma vez. Se o próprio refresh token expirar ou for revogado, a CLI informa que a sessão expirou, e o `archgate login` a restabelece. Um token emitido antes deste fluxo existir continua funcionando apenas até você entrar na plataforma; a partir daí, somente a sessão da plataforma decide. +Os tokens de acesso têm vida curta. A CLI mantém um refresh token junto deles e renova o token de acesso automaticamente, então normalmente basta entrar uma vez. Se o próprio refresh token expirar ou for revogado, a CLI informa que a sessão expirou, e o `archgate login` a restabelece. Tokens de plugin do cadastro beta (`ag_beta_…`) não são aceitos por `plugins.archgate.dev`; execute `archgate login` para substituí-los por uma sessão da plataforma. Entrar também registra `archgate credential` como um credential helper do git para `plugins.archgate.dev`, que é o que permite ao `git clone` de um repositório de plugin autenticar sem solicitar credenciais. Veja [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/reference/cli/login.mdx b/docs/src/content/docs/reference/cli/login.mdx index 181a3526..95e56f05 100644 --- a/docs/src/content/docs/reference/cli/login.mdx +++ b/docs/src/content/docs/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Access tokens are short-lived. The CLI keeps a refresh token alongside them and renews the access token automatically, so signing in once is normally enough. If the refresh token itself expires or is revoked, the CLI reports that the session has expired, and `archgate login` re-establishes it. A token issued before this flow existed keeps working only until you sign in to the platform; from then on the platform session alone decides. +Access tokens are short-lived. The CLI keeps a refresh token alongside them and renews the access token automatically, so signing in once is normally enough. If the refresh token itself expires or is revoked, the CLI reports that the session has expired, and `archgate login` re-establishes it. Plugin tokens from the beta sign-up (`ag_beta_…`) are not accepted by `plugins.archgate.dev`; run `archgate login` to replace one with a platform session. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/). diff --git a/src/helpers/sentry.ts b/src/helpers/sentry.ts index ea9a9f89..a3e87466 100644 --- a/src/helpers/sentry.ts +++ b/src/helpers/sentry.ts @@ -30,7 +30,7 @@ const SENTRY_DSN = * Sentry tunnel — routes envelopes through our own domain instead of * hitting ingest.de.sentry.io directly. Better reputation with corporate * proxies and ad-blockers, matching the PostHog proxy at n.archgate.dev. - * The tunnel server lives in services/sentry-tunnel/ and runs on Railway. + * The tunnel server is services/sentry-tunnel/ in archgate/services. */ const SENTRY_TUNNEL = "https://s.archgate.dev/tunnel"; From 3bd1efb214b662b1aac980b433cf02150498f995 Mon Sep 17 00:00:00 2001 From: Rhuan Barreto Date: Fri, 23 Oct 2026 22:34:24 +0200 Subject: [PATCH 2/4] docs(login): describe sessions as users see them The login reference says a session stays current on its own and that archgate login signs you in again if it expires, without access and refresh token mechanics or beta-token history. Same change in pt-BR and nb. Signed-off-by: Rhuan Barreto --- docs/public/llms-full.txt | 2 +- docs/src/content/docs/nb/reference/cli/login.mdx | 2 +- docs/src/content/docs/pt-br/reference/cli/login.mdx | 2 +- docs/src/content/docs/reference/cli/login.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/public/llms-full.txt b/docs/public/llms-full.txt index 5643b19e..6d14ec04 100644 --- a/docs/public/llms-full.txt +++ b/docs/public/llms-full.txt @@ -4730,7 +4730,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Access tokens are short-lived. The CLI keeps a refresh token alongside them and renews the access token automatically, so signing in once is normally enough. If the refresh token itself expires or is revoked, the CLI reports that the session has expired, and `archgate login` re-establishes it. Plugin tokens from the beta sign-up (`ag_beta_…`) are not accepted by `plugins.archgate.dev`; run `archgate login` to replace one with a platform session. +Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login` signs you in again. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/nb/reference/cli/login.mdx b/docs/src/content/docs/nb/reference/cli/login.mdx index 27274c5c..d7e230d9 100644 --- a/docs/src/content/docs/nb/reference/cli/login.mdx +++ b/docs/src/content/docs/nb/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starter en OAuth 2.0 Device Authorization Grant (RFC 8628) mot Archgate-plattfor Ingen av delene er påkrevd. I CI, over SSH eller på en ren Linux-maskin uten skjermserver (WSL når Windows-skrivebordet) hopper CLI-en over begge og skriver dem bare ut. Når autorisasjonen er fullført, gir CLI-en tokenene til git via `git credential approve`, så hvor de havner avhenger av hvilken credential-helper du har konfigurert. En helper som bruker operativsystemets legitimasjonsbehandler (macOS Keychain, Windows Credential Manager, Linux libsecret) holder dem krypterte; gits innebygde `store`-helper skriver dem til `~/.git-credentials` i klartekst. Sjekk din med `git config --global credential.helper`. -Tilgangstokener er kortlivede. CLI-en beholder et refresh-token ved siden av dem og fornyer tilgangstokenet automatisk, så det holder normalt å logge inn én gang. Hvis selve refresh-tokenet utløper eller blir tilbakekalt, melder CLI-en at økten er utløpt, og `archgate login` gjenoppretter den. Plugin-tokener fra beta-registreringen (`ag_beta_…`) godtas ikke av `plugins.archgate.dev`; kjør `archgate login` for å erstatte et slikt token med en plattformøkt. +Det holder normalt å logge inn én gang: CLI-en holder økten din oppdatert av seg selv. Hvis økten utløper eller blir tilbakekalt, sier CLI-en fra, og `archgate login` logger deg inn igjen. Innlogging registrerer også `archgate credential` som en git credential helper for `plugins.archgate.dev`, som er det som lar `git clone` av et plugin-repositorium autentisere uten å spørre. Se [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/pt-br/reference/cli/login.mdx b/docs/src/content/docs/pt-br/reference/cli/login.mdx index 427e40a1..05938084 100644 --- a/docs/src/content/docs/pt-br/reference/cli/login.mdx +++ b/docs/src/content/docs/pt-br/reference/cli/login.mdx @@ -13,7 +13,7 @@ Inicia um OAuth 2.0 Device Authorization Grant (RFC 8628) na plataforma Archgate Nenhuma das duas etapas é obrigatória. Em CI, via SSH ou em uma máquina Linux nativa sem servidor gráfico (o WSL alcança a área de trabalho do Windows), a CLI pula ambas e apenas os exibe. Após a autorização, a CLI entrega os tokens ao git via `git credential approve`, então onde eles ficam depende do credential helper que você tem configurado. Um helper apoiado no gerenciador de credenciais do sistema operacional (macOS Keychain, Windows Credential Manager, libsecret no Linux) os mantém criptografados; o helper `store` embutido do git os grava em `~/.git-credentials` em texto puro. Verifique o seu com `git config --global credential.helper`. -Os tokens de acesso têm vida curta. A CLI mantém um refresh token junto deles e renova o token de acesso automaticamente, então normalmente basta entrar uma vez. Se o próprio refresh token expirar ou for revogado, a CLI informa que a sessão expirou, e o `archgate login` a restabelece. Tokens de plugin do cadastro beta (`ag_beta_…`) não são aceitos por `plugins.archgate.dev`; execute `archgate login` para substituí-los por uma sessão da plataforma. +Normalmente basta entrar uma vez: a CLI mantém sua sessão atualizada sozinha. Se a sessão expirar ou for revogada, a CLI avisa, e o `archgate login` faz seu login novamente. Entrar também registra `archgate credential` como um credential helper do git para `plugins.archgate.dev`, que é o que permite ao `git clone` de um repositório de plugin autenticar sem solicitar credenciais. Veja [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/reference/cli/login.mdx b/docs/src/content/docs/reference/cli/login.mdx index 95e56f05..abfe8bd3 100644 --- a/docs/src/content/docs/reference/cli/login.mdx +++ b/docs/src/content/docs/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Access tokens are short-lived. The CLI keeps a refresh token alongside them and renews the access token automatically, so signing in once is normally enough. If the refresh token itself expires or is revoked, the CLI reports that the session has expired, and `archgate login` re-establishes it. Plugin tokens from the beta sign-up (`ag_beta_…`) are not accepted by `plugins.archgate.dev`; run `archgate login` to replace one with a platform session. +Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login` signs you in again. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/). From a27a0f4741031ca0a08be6b2d76b3917105b638b Mon Sep 17 00:00:00 2001 From: Rhuan Barreto Date: Fri, 23 Oct 2026 22:39:14 +0200 Subject: [PATCH 3/4] docs(login): point an expired session at archgate login refresh archgate login stops at "Already logged in" while any credential is stored; archgate login refresh always signs in again and replaces it. Signed-off-by: Rhuan Barreto --- docs/public/llms-full.txt | 2 +- docs/src/content/docs/nb/reference/cli/login.mdx | 2 +- docs/src/content/docs/pt-br/reference/cli/login.mdx | 2 +- docs/src/content/docs/reference/cli/login.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/public/llms-full.txt b/docs/public/llms-full.txt index 6d14ec04..6aca56b3 100644 --- a/docs/public/llms-full.txt +++ b/docs/public/llms-full.txt @@ -4730,7 +4730,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login` signs you in again. +Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login refresh` signs you in again. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/nb/reference/cli/login.mdx b/docs/src/content/docs/nb/reference/cli/login.mdx index d7e230d9..5495516a 100644 --- a/docs/src/content/docs/nb/reference/cli/login.mdx +++ b/docs/src/content/docs/nb/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starter en OAuth 2.0 Device Authorization Grant (RFC 8628) mot Archgate-plattfor Ingen av delene er påkrevd. I CI, over SSH eller på en ren Linux-maskin uten skjermserver (WSL når Windows-skrivebordet) hopper CLI-en over begge og skriver dem bare ut. Når autorisasjonen er fullført, gir CLI-en tokenene til git via `git credential approve`, så hvor de havner avhenger av hvilken credential-helper du har konfigurert. En helper som bruker operativsystemets legitimasjonsbehandler (macOS Keychain, Windows Credential Manager, Linux libsecret) holder dem krypterte; gits innebygde `store`-helper skriver dem til `~/.git-credentials` i klartekst. Sjekk din med `git config --global credential.helper`. -Det holder normalt å logge inn én gang: CLI-en holder økten din oppdatert av seg selv. Hvis økten utløper eller blir tilbakekalt, sier CLI-en fra, og `archgate login` logger deg inn igjen. +Det holder normalt å logge inn én gang: CLI-en holder økten din oppdatert av seg selv. Hvis økten utløper eller blir tilbakekalt, sier CLI-en fra, og `archgate login refresh` logger deg inn igjen. Innlogging registrerer også `archgate credential` som en git credential helper for `plugins.archgate.dev`, som er det som lar `git clone` av et plugin-repositorium autentisere uten å spørre. Se [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/pt-br/reference/cli/login.mdx b/docs/src/content/docs/pt-br/reference/cli/login.mdx index 05938084..411f143a 100644 --- a/docs/src/content/docs/pt-br/reference/cli/login.mdx +++ b/docs/src/content/docs/pt-br/reference/cli/login.mdx @@ -13,7 +13,7 @@ Inicia um OAuth 2.0 Device Authorization Grant (RFC 8628) na plataforma Archgate Nenhuma das duas etapas é obrigatória. Em CI, via SSH ou em uma máquina Linux nativa sem servidor gráfico (o WSL alcança a área de trabalho do Windows), a CLI pula ambas e apenas os exibe. Após a autorização, a CLI entrega os tokens ao git via `git credential approve`, então onde eles ficam depende do credential helper que você tem configurado. Um helper apoiado no gerenciador de credenciais do sistema operacional (macOS Keychain, Windows Credential Manager, libsecret no Linux) os mantém criptografados; o helper `store` embutido do git os grava em `~/.git-credentials` em texto puro. Verifique o seu com `git config --global credential.helper`. -Normalmente basta entrar uma vez: a CLI mantém sua sessão atualizada sozinha. Se a sessão expirar ou for revogada, a CLI avisa, e o `archgate login` faz seu login novamente. +Normalmente basta entrar uma vez: a CLI mantém sua sessão atualizada sozinha. Se a sessão expirar ou for revogada, a CLI avisa, e o `archgate login refresh` faz seu login novamente. Entrar também registra `archgate credential` como um credential helper do git para `plugins.archgate.dev`, que é o que permite ao `git clone` de um repositório de plugin autenticar sem solicitar credenciais. Veja [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/reference/cli/login.mdx b/docs/src/content/docs/reference/cli/login.mdx index abfe8bd3..63b4c20d 100644 --- a/docs/src/content/docs/reference/cli/login.mdx +++ b/docs/src/content/docs/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login` signs you in again. +Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login refresh` signs you in again. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/). From 5ca8166114a8a94483a672e3b5824f7952fbb51a Mon Sep 17 00:00:00 2001 From: Rhuan Barreto Date: Fri, 23 Oct 2026 22:48:24 +0200 Subject: [PATCH 4/4] docs(login): an expired session reads as signed out The CLI does not report an expired or revoked session on interactive commands; it treats the user as signed out, and archgate login signs them in again. Signed-off-by: Rhuan Barreto --- docs/public/llms-full.txt | 2 +- docs/src/content/docs/nb/reference/cli/login.mdx | 2 +- docs/src/content/docs/pt-br/reference/cli/login.mdx | 2 +- docs/src/content/docs/reference/cli/login.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/public/llms-full.txt b/docs/public/llms-full.txt index 6aca56b3..c33cdad1 100644 --- a/docs/public/llms-full.txt +++ b/docs/public/llms-full.txt @@ -4730,7 +4730,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login refresh` signs you in again. +Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI treats you as signed out, and `archgate login` signs you in again. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/nb/reference/cli/login.mdx b/docs/src/content/docs/nb/reference/cli/login.mdx index 5495516a..627a782e 100644 --- a/docs/src/content/docs/nb/reference/cli/login.mdx +++ b/docs/src/content/docs/nb/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starter en OAuth 2.0 Device Authorization Grant (RFC 8628) mot Archgate-plattfor Ingen av delene er påkrevd. I CI, over SSH eller på en ren Linux-maskin uten skjermserver (WSL når Windows-skrivebordet) hopper CLI-en over begge og skriver dem bare ut. Når autorisasjonen er fullført, gir CLI-en tokenene til git via `git credential approve`, så hvor de havner avhenger av hvilken credential-helper du har konfigurert. En helper som bruker operativsystemets legitimasjonsbehandler (macOS Keychain, Windows Credential Manager, Linux libsecret) holder dem krypterte; gits innebygde `store`-helper skriver dem til `~/.git-credentials` i klartekst. Sjekk din med `git config --global credential.helper`. -Det holder normalt å logge inn én gang: CLI-en holder økten din oppdatert av seg selv. Hvis økten utløper eller blir tilbakekalt, sier CLI-en fra, og `archgate login refresh` logger deg inn igjen. +Det holder normalt å logge inn én gang: CLI-en holder økten din oppdatert av seg selv. Hvis økten utløper eller blir tilbakekalt, behandler CLI-en deg som utlogget, og `archgate login` logger deg inn igjen. Innlogging registrerer også `archgate credential` som en git credential helper for `plugins.archgate.dev`, som er det som lar `git clone` av et plugin-repositorium autentisere uten å spørre. Se [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/pt-br/reference/cli/login.mdx b/docs/src/content/docs/pt-br/reference/cli/login.mdx index 411f143a..0d2f2bcf 100644 --- a/docs/src/content/docs/pt-br/reference/cli/login.mdx +++ b/docs/src/content/docs/pt-br/reference/cli/login.mdx @@ -13,7 +13,7 @@ Inicia um OAuth 2.0 Device Authorization Grant (RFC 8628) na plataforma Archgate Nenhuma das duas etapas é obrigatória. Em CI, via SSH ou em uma máquina Linux nativa sem servidor gráfico (o WSL alcança a área de trabalho do Windows), a CLI pula ambas e apenas os exibe. Após a autorização, a CLI entrega os tokens ao git via `git credential approve`, então onde eles ficam depende do credential helper que você tem configurado. Um helper apoiado no gerenciador de credenciais do sistema operacional (macOS Keychain, Windows Credential Manager, libsecret no Linux) os mantém criptografados; o helper `store` embutido do git os grava em `~/.git-credentials` em texto puro. Verifique o seu com `git config --global credential.helper`. -Normalmente basta entrar uma vez: a CLI mantém sua sessão atualizada sozinha. Se a sessão expirar ou for revogada, a CLI avisa, e o `archgate login refresh` faz seu login novamente. +Normalmente basta entrar uma vez: a CLI mantém sua sessão atualizada sozinha. Se a sessão expirar ou for revogada, a CLI considera você desconectado, e o `archgate login` faz seu login novamente. Entrar também registra `archgate credential` como um credential helper do git para `plugins.archgate.dev`, que é o que permite ao `git clone` de um repositório de plugin autenticar sem solicitar credenciais. Veja [`archgate credential`](/reference/cli/credential/). diff --git a/docs/src/content/docs/reference/cli/login.mdx b/docs/src/content/docs/reference/cli/login.mdx index 63b4c20d..81439cd6 100644 --- a/docs/src/content/docs/reference/cli/login.mdx +++ b/docs/src/content/docs/reference/cli/login.mdx @@ -13,7 +13,7 @@ Starts an OAuth 2.0 Device Authorization Grant (RFC 8628) against the Archgate p Neither step is required. In CI, over SSH, or on a native Linux host with no display server (WSL reaches the Windows desktop) the CLI skips both and just prints them. Once authorized, the CLI hands the resulting tokens to git via `git credential approve`, so where they end up depends on the credential helper you have configured. A helper backed by your OS credential manager (macOS Keychain, Windows Credential Manager, Linux libsecret) keeps them encrypted; git's built-in `store` helper writes them to `~/.git-credentials` in plain text. Check yours with `git config --global credential.helper`. -Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI tells you, and `archgate login refresh` signs you in again. +Signing in once is normally enough: the CLI keeps your session current on its own. If the session expires or is revoked, the CLI treats you as signed out, and `archgate login` signs you in again. Signing in also registers `archgate credential` as a git credential helper for `plugins.archgate.dev`, which is what lets `git clone` of a plugin repository authenticate without prompting. See [`archgate credential`](/reference/cli/credential/).