-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Conversation
ce8d0d7
to
e7593c9
Compare
Since we're not doing refresh tokens any more, we should start killing off the dead code paths. /tokenrefresh itself is a bit of a thornier subject, since there might be apps out there using it, but we can at least not generate refresh tokens on new logins.
e7593c9
to
5c4edc8
Compare
We might as well treat all refresh_tokens as invalid. Just return a 403 from /tokenrefresh, so that we don't have a load of dead, untestable code hanging around. Still TODO: removing the table from the schema.
@@ -386,8 +386,8 @@ def _create_registration_details(self, user_id, params): | |||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The doc-string still refers to refresh_token
s
We might want to remove the refresh_tokens database table at somepoint, but fitting that into the schema upgrade process might be subtle given that there are background updates run against that table. So lets leave that for another PR so that it can be reviewed properly. |
Other than the stale docstring LGTM. |
yeah, I came to exactly the same conclusion. |
Remove refresh_token reference
Refresh tokens are dead, so let's stop trying to generate new ones.