Bumps the dev Compose Liquor Cabinet image to 2.0.0-rc.2 and sets RS_HASHED_ACCESS_TOKENS=true, so it looks up remoteStorage authorizations by the SHA256 digest of the presented bearer token. That matches how Akkounts has stored authorizations in Redis since the token hashing change, where the plaintext is no longer available after issuance.
Without the flag, the dev setup kept Liquor Cabinet on a plaintext lookup, so a freshly issued authorization (stored only under its digest key) could not be found and requests failed with 401. Verified locally: a token whose digest is present in Redis is authorized, while a wrong token still returns 401. Liquor Cabinet 2.0.0-rc.2 still falls back to the plaintext key, so authorizations created before hashing keep working.
Bumps the dev Compose Liquor Cabinet image to 2.0.0-rc.2 and sets RS_HASHED_ACCESS_TOKENS=true, so it looks up remoteStorage authorizations by the SHA256 digest of the presented bearer token. That matches how Akkounts has stored authorizations in Redis since the token hashing change, where the plaintext is no longer available after issuance.
Without the flag, the dev setup kept Liquor Cabinet on a plaintext lookup, so a freshly issued authorization (stored only under its digest key) could not be found and requests failed with 401. Verified locally: a token whose digest is present in Redis is authorized, while a wrong token still returns 401. Liquor Cabinet 2.0.0-rc.2 still falls back to the plaintext key, so authorizations created before hashing keep working.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bumps the dev Compose Liquor Cabinet image to 2.0.0-rc.2 and sets RS_HASHED_ACCESS_TOKENS=true, so it looks up remoteStorage authorizations by the SHA256 digest of the presented bearer token. That matches how Akkounts has stored authorizations in Redis since the token hashing change, where the plaintext is no longer available after issuance.
Without the flag, the dev setup kept Liquor Cabinet on a plaintext lookup, so a freshly issued authorization (stored only under its digest key) could not be found and requests failed with 401. Verified locally: a token whose digest is present in Redis is authorized, while a wrong token still returns 401. Liquor Cabinet 2.0.0-rc.2 still falls back to the plaintext key, so authorizations created before hashing keep working.