feat(auth-backend): validate catalog user existence on refresh token usage
Add `experimentalRefreshToken.validateCatalogUserExistence` config option that checks whether the user's catalog entity still exists before issuing a new access token during refresh. If the user has been removed from the catalog (e.g. offboarded), the refresh is rejected and the session is revoked. Transient catalog errors reject the refresh but preserve the session for retry. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: MT Lewis <mtlewis@users.noreply.github.com>
This commit is contained in:
@@ -0,0 +1,5 @@
|
||||
---
|
||||
'@backstage/plugin-auth-backend': patch
|
||||
---
|
||||
|
||||
Added a new `auth.experimentalRefreshToken.validateCatalogUserExistence` config option. When enabled, refresh token usage will verify that the user's catalog entity still exists before issuing a new access token. If the user has been removed from the catalog, the refresh is rejected and the session is revoked. Transient catalog errors reject the refresh but preserve the session for retry.
|
||||
Reference in New Issue
Block a user