From 3b181c9278e1030760609837a7eceb79242ed730 Mon Sep 17 00:00:00 2001 From: Alexandre Dutra Date: Wed, 12 Jun 2024 08:44:58 +0200 Subject: [PATCH] changelog --- CHANGELOG.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index edc3ec0ea0d..c8bcfd26085 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -41,10 +41,13 @@ as necessary. Empty sections will not end in the release notes. specified explicitly in the JDBC URL. - `nessie.version.store.persist.jdbc.catalog` - `nessie.version.store.persist.jdbc.schema` -- Support for token exchange in the Nessie client is deprecated and will be removed in a future - release. The token exchange flow was being used to exchange a refresh token for an access token, - but this is not its recommended usage. Instead, the client will now fall back to the configured - initial grant type, if a refresh token is not provided by the authorization server. +- Support for token exchange in the Nessie client, in its current form, is now deprecated. The token + exchange flow was being used to exchange a refresh token for an access token, but this is not its + recommended usage. From now on, if a refresh token is provided by the authorization server, the + Nessie client will use the `refresh_token` grant type to obtain a new access token; if a refresh + token is not provided, the client will use the configured initial grant type to fetch a new access + token. _This change should thus be transparent to all users._ The `token_exchange` flow will be + redesigned in a future release to support more advanced use cases. ### Fixes