cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
nardell
Community Participant

Is it possible to override lis_* LTI parameters with custom settings

Jump to solution

I am wondering if it is possible to override the provided values for any of the lis_ parameters in the External Apps > Edit App > Custom Fields setting.  For example, I have tried to do the following:

lis_person_contact_email_primary=$Canvas.user.loginId

.. however this does not seem to work in testing. The intent is to ensure that the email attribute a third party tool uses is always the institutional email address (which happens to be the login ID, as EPPN).

THanks for any advice on this,

Mike

Labels (2)
0 Kudos
1 Solution

Accepted Solutions
chriscas
Community Champion

Hi @nardell ,

I don't believe those values can be overridden.  Some LTIs will let you do custom mapping on their end, but if the particular LTI you're working with is hardcoded to look at the lis_person_contact_email_primary field, I think the only thing you can do is block users from changing their default email in Canvas (I made some JS code for this, and it has seemed to do the trick for us but ymmv).  If you do put this JS in place, you'd also need to do a one-time script of some sort to reset the default email back to the right one for any users who might have changed that.

-Chris

View solution in original post

2 Replies
chriscas
Community Champion

Hi @nardell ,

I don't believe those values can be overridden.  Some LTIs will let you do custom mapping on their end, but if the particular LTI you're working with is hardcoded to look at the lis_person_contact_email_primary field, I think the only thing you can do is block users from changing their default email in Canvas (I made some JS code for this, and it has seemed to do the trick for us but ymmv).  If you do put this JS in place, you'd also need to do a one-time script of some sort to reset the default email back to the right one for any users who might have changed that.

-Chris

View solution in original post

nardell
Community Participant

Thanks @chriscas - I appreciate the clarification / confirmation on what I was finding to be the case. I believe that restricting the changes to email addresses may be something we need to consider. Will pursue using custom attributes on the vendor's side before we go down that road. 

Mike