From 7b1f33abd0da9aa37131b4ff7e3e9f169c383c08 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A2u=20Cao?= Date: Wed, 4 Nov 2026 15:35:45 +0400 Subject: [PATCH] Upgrade Liquor Cabinet and enable hashed access tokens Liquor Cabinet 2.0.0-rc.2 can look up remoteStorage authorizations by the SHA256 digest of the presented bearer token, which matches how Akkounts now stores them. Set RS_HASHED_ACCESS_TOKENS=true in the dev Compose setup so the two sides agree; Liquor Cabinet still falls back to the plaintext key for authorizations created before hashing. --- docker-compose.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index 36a7fa7..50eb5dc 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -97,7 +97,7 @@ services: GARAGE_DEFAULT_BUCKET: remotestorage liquor-cabinet: - image: gitea.kosmos.org/5apps/liquor-cabinet:2.0.0-rc.1 + image: gitea.kosmos.org/5apps/liquor-cabinet:2.0.0-rc.2 networks: - external_network - internal_network @@ -108,6 +108,7 @@ services: command: ["bundle", "exec", "rainbows", "-c", "/etc/liquor-cabinet/rainbows.conf.rb", "--listen", "0.0.0.0:4567"] environment: RACK_ENV: staging + RS_HASHED_ACCESS_TOKENS: "true" REDIS_HOST: redis REDIS_PORT: 6379 REDIS_DB: 1 -- 2.50.1