chore: Remove edx-token-utils dependency #36077
Open
+265
−35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rijuma
force-pushed
the
rijuma/remove-edx-token-utils-dep
branch
12 times, most recently
from
48ab9fa to
ef07615
Compare
rijuma
force-pushed
the
rijuma/remove-edx-token-utils-dep
branch
from
ef07615 to
0a0d662
Compare
rijuma
force-pushed
the
rijuma/remove-edx-token-utils-dep
branch
from
0a0d662 to
fe88592
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
There's been a request to remove
edx-token-utilsdependency from the repository by Axim on issue #36009. The platform only uses one function from this repository, and since this repository is outdated one of the suggestions was to remove the dependency and fold the necessary parts intoedx-platformitself.This update moves the functionality for packing/unpacking and signing JWT tokens. We only use the unpacking on
edx-platformbut I thought it was a good idea to have both implementations just in case.This would have no noticeable impact user wise.
Supporting information
Testing instructions
Deadline
None.