Celebrate Excellence in Education: Nominate Outstanding Educators by April 15!
Found this content helpful? Log in or sign up to leave a like!
Is there a way to specify prefer_sis_email when using LTI 1.3?
Hi @office9,
I found this question while doing a community cleanup. I believe I have a possible answer for you. I tested various things, and what finally seemed to work (judging by looking at the LTI config via the API) was to add the following placement to your LTI 1.3 JSON:
I hope this late response may still help, but I also want to stress that I couldn't find any official documentation on this, so take please take this as an unofficial option.
-Chris
Thank you.
Was hoping to configure an inherited developer key to use this, but that doesn't seem possible at this time. Doesn't seem to be any workarounds for that case, right?
Hi @tue59036,
With an inherited developer key, you'd need to use the external tools API to modify the deployment of the tool. If you do go this route, you'd need to pay attention to the config, as if someone modifies the inherited key in the future, it may overwrite your change to the deployment, and you'd need to re-apply the config with the API at that point.
I do have a python script written to help make changes like this easier if you're interested.
-Chris
We (mostly @phanley) tried setting tool_configuration[prefer_sis_email], with the external tools API - but it didn't seem to have any effect on the inherited LTI 1.3 developer key. Canvas still passes along the user's "default email".
Worked fine on the LTI 1.1 app I tried.
To participate in the Instructure Community, you need to sign up or log in:
Sign In