Feb 10 11:23:55 ip-10-0-0-82 [service_variant=lms][oauthlib.oauth1.rfc5849.endpoints.signature_only][env:sandbox] INFO [ip-10-0-0-82 2621] [user None] [signature_only.py:81] - [Failure] request verification failed. Feb 10 11:23:55 ip-10-0-0-82 [service_variant=lms][oauthlib.oauth1.rfc5849.endpoints.signature_only][env:sandbox] INFO [ip-10-0-0-82 2621] [user None] [signature_only.py:82] - Valid client: True Feb 10 11:23:55 ip-10-0-0-82 [service_variant=lms][oauthlib.oauth1.rfc5849.endpoints.signature_only][env:sandbox] INFO [ip-10-0-0-82 2621] [user None] [signature_only.py:83] - Valid signature: False
The same course configuration with ironwood works perfectly while testing with http://ltiapps.net/test/tc.php. I am wondering if something changed with LTI between Ironwood and Juniper.
Because I couldn’t find anything, I decided to install a new single server instance of ironwood.master. Just to check something.
I was surprised to discover that LTI wasn’t working either on that instance.
Did any of the libraries installed for oauth or LTI under /edx/app/edxapp/venvs/edxapp changed versions recently? I am comparing my test system and production system where LTI works under ironwood and there does not seem to be any change. Did I miss something obvious?
@nedbat is this something that will carry on to Juniper and should we expect it to “break” our LTI components used by courses accessing our Open edX instance through LTI? We have a few courses where our internal Moodle systems are accessing LTI exercises in our Open edX site and expecting a grade to be returned to Moodle. This would be a serious game changer for courses who have developped ressources in Open edX and want to leverage them in Moodle. We have a few courses like that here at Université de Montréal and École Polytechnique de Montréal that reach out to https://cours.edulib.org to access a few LTI components.