From afac7abd6f7ee614cd1bbe7413d196f7c149387e Mon Sep 17 00:00:00 2001 From: Brett Smith Date: Thu, 24 Aug 2023 15:11:32 -0400 Subject: [PATCH] 20750: Fix documentation link typo Arvados-DCO-1.1-Signed-off-by: Brett Smith --- doc/admin/upgrading.html.textile.liquid | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/admin/upgrading.html.textile.liquid b/doc/admin/upgrading.html.textile.liquid index 7c521a24ba..5aec1cbb6d 100644 --- a/doc/admin/upgrading.html.textile.liquid +++ b/doc/admin/upgrading.html.textile.liquid @@ -50,7 +50,7 @@ The defaults for all of these options match the previous behavior of @arvados-lo h3. API clients can always retrieve their current token, regardless of scopes -We have introduced a small exception to the previous behavior of "Arvados API token scopes":{{ site.baseurl }}:/admin/scoped-tokens.html in this release. A valid token is now always allowed to issue a request to "@GET /arvados/v1/api_client_authorizations/current@":{{ site.baseurl }}/api/methods/api_client_authorizations.html#current regardless of its scopes. This allows clients to reliably determine whether a request failed because a token is invalid, or because the token is not permitted to perform a particular request. The API server itself needs to be able to do this to validate tokens issued by other clusters in a federation. +We have introduced a small exception to the previous behavior of "Arvados API token scopes":{{ site.baseurl }}/admin/scoped-tokens.html in this release. A valid token is now always allowed to issue a request to "@GET /arvados/v1/api_client_authorizations/current@":{{ site.baseurl }}/api/methods/api_client_authorizations.html#current regardless of its scopes. This allows clients to reliably determine whether a request failed because a token is invalid, or because the token is not permitted to perform a particular request. The API server itself needs to be able to do this to validate tokens issued by other clusters in a federation. h3. UseAWSS3v2Driver option removed -- 2.30.2