Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Stop generating refresh_tokens #1654

Merged
merged 5 commits into from
Dec 1, 2016
Merged

Stop generating refresh_tokens #1654

merged 5 commits into from
Dec 1, 2016

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Nov 25, 2016

Refresh tokens are dead, so let's stop trying to generate new ones.

@richvdh richvdh force-pushed the rav/no_more_refresh_tokens branch 3 times, most recently from ce8d0d7 to e7593c9 Compare November 28, 2016 09:59
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.
@richvdh richvdh force-pushed the rav/no_more_refresh_tokens branch from e7593c9 to 5c4edc8 Compare November 28, 2016 10:13
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):
"""
Copy link
Contributor

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_tokens

@NegativeMjark
Copy link
Contributor

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.

@NegativeMjark
Copy link
Contributor

NegativeMjark commented Dec 1, 2016

Other than the stale docstring LGTM.

@richvdh
Copy link
Member Author

richvdh commented Dec 1, 2016

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.

yeah, I came to exactly the same conclusion.

Remove refresh_token reference
@richvdh richvdh merged commit 4712000 into develop Dec 1, 2016
@richvdh richvdh deleted the rav/no_more_refresh_tokens branch December 1, 2016 11:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants