[External Tools] Support environment variables for LTI 1.3

[agschmid]

For LTI 1.1 there was support for environment variables (https://canvas.instructure.com/doc/api/file.tools_xml.html#test_env_settings) so when beta/test refreshed, our LTI tools would point to beta/test on the beta/test servers instead of production. We've used the environment variables for years.

We're in the process of switching to LTI 1.3 and were told that there is no support for environment variables, according to Instructure "it doesn't seem like we've seen much need for this from our end users so far until now."

I know we are not the only ones using the environment variables and hope that Instructure will decide to support environment variables for LTI 1.3.

[KristinL]

Hi @agschmid -

Thanks for sharing this Idea with the Community!

You should be able to launch LTI 1.3 in your Beta and Test environments. This isn't only available to LTI 1.1. I also understand that sometimes LTIs have their own support and resources and Canvas Support can help connect you to those teams.

Here's a related lesson for reference: How do I configure an LTI key for an account? 

One of our L1 Support Agents said that if you try to test your LTI 1.3 in Beta and you run into issues, you can open a case with support and they'll either assist you or connect you to a person who can.

[agschmid]

Hi @KristinL ,

That's surprising since I contacted support first and asked. It was sent to "one of the engineers" who stated that environment variables are not available for LTI 1.3. Environment variables cannot be tested in beta. Are you possibly referring to "custom" variables?

This is an example of the LTI 1.1 environment variables, (the XML gets added to production):

      <lticm:options name="environments">
        <lticm:property name="launch_url">http://test.example.com/content</lticm:property>
        <lticm:property name="domain">test.example.com</lticm:property>
        <lticm:property name="test_launch_url">http://test.example.com/content</lticm:property>
        <lticm:property name="test_domain">test.example.com</lticm:property>
        <lticm:property name="beta_launch_url">http://beta.example.com/content</lticm:property>
        <lticm:property name="beta_domain">beta.example.com</lticm:property>
      </lticm:options>

[agschmid]

Could this idea please be reopened? Here is the reply I received from L2 support :

My name is Taylor with our L2 Support team.  I understand you are looking for information regarding whether custom environment launch URLs are supported with LTI 1.3 tools.

After speaking to our engineers about this, we learned that this is unfortunately not supported with LTI 1.3 tools at this time.

I'm not sure what specifics updates will be made on our end as LTI 1.3 becomes more widely adopted, but at this time, the Community Ideas space will likely be your best option, as it doesn't seem like we've seen much need for this from our end users so far until now.  If you like, you can suggest these variables be supported with LTI 1.3 tools using this page:
https://community.canvaslms.com/t5/forums/postpage/board-id/ideas/search-before-post-mode/true

Let us know if there are any additional questions regarding this.  Thanks and have a great day!

[KristinL]

Hi @agschmid -

Thank you for sharing about your process! I'll follow up and make sure everything is connected from the Support and Community Team side of things, but this Idea is Open for Conversation.

[agschmid]

Thank you @KristinL 

[ismail_orabi]

We would also greatly benefit from this feature, otherwise it's a very tedious process to update LTI 1.3 configs after a refresh.

[agschmid]

I have a temporary solution for updating the beta/stage servers until Instructure comes up with a solution:

https://community.canvaslms.com/t5/Canvas-Developers-Group/Temporary-Solution-for-Updating-LTI-1-3-o...

[ColinMurtaugh]

We are also interested in this.