Restricting Xerte embed via "Other"

In Cardiff University, we used to restrict embedded Xerte objects via our VLE using the "Other" option in Access. Previously, staff could use " learningcentral.cf.ac.uk/ " as the main URL for these restrictions. However, we recently discovered that this method no longer works, especially when these Xerte objects are embedded in the new Ultra Courses environment. After conducting several tests, we found that the following combination of URLs seems to work: alt-5fd150846bae0.blackboard.com/ and xerte.cardiff.ac.uk/tsugi/lti/oidc_launch . However, we're not entirely certain about this.

Could someone please provide more insights regarding this issue and whether we can have a more definitive answer to provide to our staff?

Hi Nan
The "Other" option detects the 'referrer' value being passed back from the launch environment so if you have allowed values set in Xerte that previously worked but now the value being sent from Ultra is different then you need to change the values in Xerte to match. From memory I previously shared a test LO with Jin to use to detect and verify the referrer being sent.
However your message is also somewhat confusing as you refer to an LTI launch URL too. If you are using LTI then you really don't need to use the 'Other' option because the LO will only work via the LTI link and wherever that is set in BB/Ultra. If someone tried to view the LO outside of that environment it simply won't work.
HTH
Ron

BTW I corrected a few typos after sending my reply but also you may need to verify that your LTI 1.3/Advantage integration is still working as it should if the envrionment has changed.
HTH
Ron

Thanks Ron for the prompt reply. I will carry out some more testings and get back to you on my findings.