🔒️(api) securing API with LTI token #29
Merged
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
wilbrdt
force-pushed
the
api/security
branch
2 times, most recently
from
40481b8 to
e3acd4e
Compare
lunika
approved these changes
Jun 5, 2024
`warren:api-core-0.3.0` and `warren:app-0.3.0` are released. Upgrading base images to these last revision.
API was unsecure and anyone could make request to it from a browser. Securing it with a LTI token verification on each endpoint, and to get the `course_id`, the `roles` of the user and its `user_id`.
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.
Purpose
API was unsecure and anyone could make request to it from a browser.
Proposal
Securing it with a LTI token verification on each endpoint.