Store LTI1.3 assignment ID explicitly in the DB #6616
Merged
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.
For:
To talk to the Name and Roles LTI API we use the service URL sent in LTI1.3 courses.
However to filter that by assignment we need to use the LTI1.3 assignment ID on that same course URL.
The ID is sent in all launches but if present, we prefer the LTI1.1 (for backwards compatibility).
With this PR we now store explicitly the LTI1.3 ID to later be use the call the LTI API.
Testing
Nothing changes
The LTI1.3 is stored in the DB