-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DEPR]: Remove JWT_AUTH_REFRESH_COOKIE #190
Comments
Remove the setting JWT_AUTH_REFRESH_COOKIE which serves no purpose. See DEPR: openedx/public-engineering#190
@dianakhuang openedx/edx-platform#32664 This pull request all tests passed successfully |
Remove the setting JWT_AUTH_REFRESH_COOKIE which serves no purpose. See DEPR: openedx/public-engineering#190
Remove the setting JWT_AUTH_REFRESH_COOKIE which serves no purpose. See DEPR: openedx/public-engineering#190
[inform] I moved the edx org work to a separate ticket that would not block this DEPR: edx/edx-arch-experiments#353. |
@Yagnesh1998: If you could start by removing this from openedx/configuration. See https://github.com/search?q=repo%3Aopenedx%2Fconfiguration+JWT_AUTH_REFRESH_COOKIE&type=code. Once this is done, you can fix other repos. Thank you. |
assign me |
The setting JWT_AUTH_REFRESH_COOKIE is meaningless and unused and is being cleaned up to avoid confusion. See DEPR: openedx/public-engineering#190
anyone is working on this ? is this closed ? |
@lokidil I'm working on it. Thanks. |
Although there are still edx repos to complete, the openedx repos are complete and I am marking this as closed. Thank you @Yagnesh1998. |
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Remove unused JWT_AUTH_REFRESH_COOKIE setting. This setting was never actually used, so there is no timing issues. See DEPR for details: openedx/public-engineering#190
Proposal Date
2023-04-12
Target Ticket Acceptance Date
2023-06-15
Earliest Open edX Named Release Without This Functionality
Quince - 2023-10
Rationale
The setting
JWT_AUTH_REFRESH_COOKIE
is meaningless and unused, and should be cleaned up to avoid confusion.In the very early days of introducing MFEs, we thought we were going to need this cookie in addition to the JWT cookie. However, it turned out we didn't need it, but the setting stuck around the contagion of it (being in cookiecutter and other template libraries) has resulted in it uselessly being copied to many repos.
Removal
The setting
JWT_AUTH_REFRESH_COOKIE
can simply be removed with no ramifications.Replacement
No replacement needed.
Deprecation
No response
Migration
No response
Additional Info
The text was updated successfully, but these errors were encountered: