From efa233d5f833f1b32f5204d24574ede0c196cc73 Mon Sep 17 00:00:00 2001 From: Jack Green Date: Thu, 28 May 2026 14:37:36 +0100 Subject: [PATCH] Fix OIDC documentation link in `jfrog-platform-configuration.md` --- .../get-started/configurations/jfrog-platform-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jfrog-applications/jfrog-cli/get-started/configurations/jfrog-platform-configuration.md b/jfrog-applications/jfrog-cli/get-started/configurations/jfrog-platform-configuration.md index c9bb3c65..6490837a 100644 --- a/jfrog-applications/jfrog-cli/get-started/configurations/jfrog-platform-configuration.md +++ b/jfrog-applications/jfrog-cli/get-started/configurations/jfrog-platform-configuration.md @@ -217,7 +217,7 @@ The `exchange-oidc-token` (alias: `eot`) command is used to exchange an OIDC tok Before executing the command, ensure that an OIDC integration has been set up on the platform. For more details, -refer to the [JFrog OIDC Integration](https://jfrog.com/help/r/jfrog-platform-administration-documentation/openid-connect-integration) documentation. +refer to the [JFrog OIDC Integration](https://docs.jfrog.com/administration/docs/openid-connect-integration) documentation. OIDC tokens are short-lived and ⚠️**do not support refresh**⚠️. OIDC access tokens are not renewable. They are intended for one-time use during CI pipelines and do not have an automatic refresh mechanism like other tokens. Consequently, the authentication will only be valid for the duration of the pipeline or until the token expires.