feat: Allow optionally passing PII in course LTI tab [BD-38] [BB-3899] [TNL-8104] - #26982
Conversation
|
Thanks for the pull request, @xitij2000! I've created BLENDED-792 to keep track of it in Jira. When this pull request is ready, tag your edX technical lead. |
11433cd to
bfdaba8
Compare
There was a problem hiding this comment.
Are ask_to_send_username and ask_to_send_email two new fields we're adding to LtiConfiguration? I'm wondering if we want these to be phrased more as authorizations or allowances. can_send_username or something like that, perhaps? I'm not sure if there's precedent for a naming scheme for this elsewhere in the codebase.
There was a problem hiding this comment.
@davidjoy These are the terms used by the current LTI XBLock. I was going for familiarity here, but since they have different UIs perhaps it isn't that important. I will change this to what you suggested.
There was a problem hiding this comment.
Yeah, I'm not a huge fan of the ask_to_ prefix; I initially thought this would prompt the user for consent.
That said, it may be even worse to refer to the variable by multiple different names.
Given the original key has existed in the xblock for >5 years now, I think I'd be begrudgingly inclined to leave it as-is 🤷
There was a problem hiding this comment.
@stvstnfrd The field name is internal to the XBlock, and the display name is "Request user's username" the XBlock does actually ask for permission before sending this data.
Perhaps we can use more accurate terminology internally while using familiar names in the UI?
There was a problem hiding this comment.
What's the current stance on naming these variables?
There was a problem hiding this comment.
The current internal naming is to be consistent with the current XBlock field names. This might not be the best idea since these are used differently here.
Perhaps the names should drop the ask and just be send_username and send_email.
There was a problem hiding this comment.
sure, that would clean up a little.
There was a problem hiding this comment.
Yeah, I'm not a huge fan of the ask_to_ prefix; I initially thought this would prompt the user for consent.
That said, it may be even worse to refer to the variable by multiple different names.
Given the original key has existed in the xblock for >5 years now, I think I'd be begrudgingly inclined to leave it as-is 🤷
8337f57 to
59ded7b
Compare
|
What is the next step on this PR? |
|
jenkins run quality |
|
@marcotuts While this was being worked on I created an ADR to decide how to handle the flag situation since it wasn't straightforward. Since that ADR was approved, I will have a task this sprint to implement the suggestions from the ADR, and use the flag the way it's described in the ADR |
|
📣 💥 Heads-up: You must either rebase onto master or merge master into your branch to avoid breaking the build. We recently removed diff-quality and introduced lint-amnesty. This means that the automated quality check that has run on your branch doesn't work the same way it will on master. If you have introduced any quality failures, they might pass on the PR but then break the build on master. This branch has been detected to not have commit 2e33565 as an ancestor. Here's how to see for yourself: If you have any questions, please reach out to the Architecture team (either #edx-shared-architecture on Open edX Slack or #architecture on edX internal). |
awaisdar001
left a comment
There was a problem hiding this comment.
Just a few nits -- otherwise this PR looks good to me.
There was a problem hiding this comment.
What's the current stance on naming these variables?
33379b9 to
dad2973
Compare
awaisdar001
left a comment
There was a problem hiding this comment.
@xitij2000 This PR seems outdated or blocked on some other PR.
The reason I say that is because there is no model "CourseAllowPIISharingInLTIFlag" in specified import location (edx:master). at the moment.
Thoughts?
|
@awaisdar001 Yes, it is currently blocked on this PR: openedx/xblock-lti-consumer#172 That needs to be updated to add the new changelog, bump up the version to 3 etc. Then this PR needs to be updated to use new new flag, remove the prefixes etc. I don't have time in the current sprint, but will look into next sprint starting next tuesday. |
1b41608 to
26bbacc
Compare
|
jenkins run all |
AhtishamShahid
left a comment
There was a problem hiding this comment.
There is lti-consumer-xblock dependency at this line. https://github.com/edx/edx-platform/blob/36319bda486394f049f006898c5a920a09211c33/requirements/edx/base.in#L112
And changes in .txt files for dependency seem to be pointing towards the branch, normally we use tags for that.
This is a temporary change. Currenly the version of xblock-lti-consumer this needs hasn't been merged or tagged yet: openedx/xblock-lti-consumer#172 So while that PR is still unmerged, and the release is untagged, this PR needs to use the branch name. Once a release is tagged, I'll run make upgrade and commit that. |
saadyousafarbi
left a comment
There was a problem hiding this comment.
Have added some comments!
If this is ready, can we have a sandbox for this so we can test the functionality thoroughly before moving forward!
Thank you!
There was a problem hiding this comment.
are there any other fields other than pii_share_username and pii_share_email starting with pii_ for this check?
There was a problem hiding this comment.
Nope, but the idea is that if there are any in the future, this will cover it.
31272d2 to
9d2a087
Compare
ae6113b to
3708721
Compare
awaisdar001
left a comment
There was a problem hiding this comment.
Looks good, but updatexblock-lti-consumer requirement before merging.
3708721 to
d989432
Compare
I've manually updated the dependency. |
|
jenkins run all |
|
@xitij2000 the checks are failing here. Can you take a look? |
Thats because pypi is not updated to 3.0.0 :( |
|
@xitij2000 please share the sandbox for this PR once the build pipelines are fixed and test pass! Thank you. |
d989432 to
68321a0
Compare
|
jenkins run all |
|
Your PR has finished running tests. There were no failures. |
|
@xitij2000 is this PR ready to merge? Should I merge it? |
|
@asadazam93 Yes. It's good to go for my side. |
|
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production. |
|
EdX Release Notice: This PR has been deployed to the production environment. |
Adds the ability to pass PII to an LTI provider in the LTI course tab if the LtiConfiguration associated with that tab is configured to allow that.
Jira task: https://openedx.atlassian.net/browse/TNL-8104
Dependencies: None
Sandbox URL:
Merge deadline: "None"
Testing instructions:
LtiConfigurationfor this provider set thelti_configto:{"ask_to_send_username":true,"ask_to_send_email":true}Reviewers