Skip to content

Commit fc50ff1

Browse files
JordiNeiln2ygk
andauthored
documentation seems to be outdated regarding rotate_refresh_token setting known bug (#1250)
Co-authored-by: Alan Crosswell <[email protected]>
1 parent 62f9261 commit fc50ff1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/settings.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ this value if you wrote your own implementation (subclass of
177177
ROTATE_REFRESH_TOKEN
178178
~~~~~~~~~~~~~~~~~~~~
179179
When is set to `True` (default) a new refresh token is issued to the client when the client refreshes an access token.
180-
Known bugs: `False` currently has a side effect of immediately revoking both access and refresh token on refreshing.
180+
If `False`, it will reuse the same refresh token and only update the access token with a new token value.
181181
See also: validator's rotate_refresh_token method can be overridden to make this variable
182182
(could be usable with expiring refresh tokens, in particular, so that they are rotated
183183
when close to expiration, theoretically).

0 commit comments

Comments
 (0)