LTI configurations pipeline EDLY-6642 #4
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
mfarhan943
requested review from
muhammadali286,
taimoor-ahmed-1 and
muhammadali124
taimoor-ahmed-1
approved these changes
Apr 25, 2024
mfarhan943
force-pushed
the
farhan/EDLY-6642
branch
from
3a86b71 to
1b49052
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.
Descriptions:
We are implementing a solution that allows users to avoid re-entering values, such as URLs and keys, in LTI configurations. But, each XBlock will have its unique ClientID, Keyset URL, and Access Token URL to be used with the customer's tool.
Jira
https://edlyio.atlassian.net/browse/EDLY-6642