cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
agschmid
Community Contributor

Environment variables stopped working

Jump to solution

We have been using environment variables for our LTI tools for years. Recently, around the beginning of November, the environment variables stopped working, so after the weekly refresh, the tools on beta are pointing to production.

Since we haven't updated the xml on production for these tools, it doesn't make sense that the environment variables just stopped working on beta. Has anyone else experienced this? Did something change that I missed?

Labels (2)
0 Kudos
1 Solution

Accepted Solutions
agschmid
Community Contributor

I submitted a ticket to Instructure and they were able to reproduce the problem. Their engineers are working on fixing this.

View solution in original post

0 Kudos
3 Replies
agschmid
Community Contributor

I submitted a ticket to Instructure and they were able to reproduce the problem. Their engineers are working on fixing this.

View solution in original post

0 Kudos
matthew_buckett
Community Contributor

Is this back working again?

As I understand it this is the use of the properties beta_launch_url and test_launch_url that allow a LTI 1.1 tool to be launched to a different URL when the launch is made from test/beta.

agschmid
Community Contributor

Yes, this is working again. There was a bug and support was able to reproduce it and put in a fix.

The beta_launch_url, beta_domain, test_launch_url  and test_domain are added to the production xml so when the beta/test servers refresh, they receive the beta/test launch urls. It has been working great for a number of years with just a few glitches (like the one reported here) once in a while.