Roll the refresh_token #1224

New Issue

MrUnknownDE · 2026-04-06T01:41:31+02:00

MrUnknownDE commented

2026-04-06 01:41:31 +02:00

Originally created by @Timshel on 2/18/2024

Hey,

We recently discussed the refresh_token in the SSO PR and during this discussion it occurred to me that the long lived refresh_token could be rolled as is done by some SSO client.

This is handled / expected by the Bitwarden clients since the response _refresh_login contain the potentially updated refresh_token.

*Originally created by @Timshel on 2/18/2024* Hey, We recently discussed the `refresh_token` in the SSO PR and during this discussion it occurred to me that the long lived `refresh_token` could be rolled as is done by some SSO client. This is handled / expected by the Bitwarden clients since the response `_refresh_login` contain the potentially updated [refresh_token](https://github.com/dani-garcia/vaultwarden/blob/bb2412d0339e1da5dee99fc566a2b2aab5d2808c/src/api/identity.rs#L122).

MrUnknownDE closed this issue

2026-04-06 01:41:31 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1224