Inheriting permissions from LTI platform context #2868
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
github-actions
bot
added
language
emmachughes
force-pushed
the
content-contexts
branch
from
3e4addb to
01d2516
Compare
emmachughes
force-pushed
the
content-contexts
branch
2 times, most recently
from
0ee76eb to
9adefe8
Compare
emmachughes
force-pushed
the
content-contexts
branch
from
4469de5 to
aac4640
Compare
chrieinv
approved these changes
Jan 9, 2025
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.
Adds contextual permissions checking.
LTI platforms can have a context assigned to them with either the Reader, Editor, or Owner role. When Edlib is launched as an LTI tool, permissions are granted based on the platform's contexts.
Upon creating content during an LTI launch, each context is assigned to the content. The content must be assigned the relevant context for inherited permissions to be granted.
Existing content is not modified.
Finally, role checks for users are properly implemented now.