Invalid token. Please reinitiate login. about ltijs

[jeffmiko]

I installed Moodle 3.7 on a clean virtual machine following the Ubuntu instructions and it is working now. I followed the steps in your Medium article. So it was definitely something to do with my docker setup or environment. I wonder if it had to do with DNS since I was running both Moodle and VSCode in docker containers. That's why I was trying to use IP addresses initially. Thanks for your help.

[Cvmcosta]

Hello, your configuration looks correct at first glance.

i've been seeing some problems regarding the usage of ltijs with Bitnami Moodle, apparently their configuration causes some issues. I'm installing their Moodle Stack and trying to figure out what is wrong. It seems Bitnami's moodle is not receiving either the nonce or the lti_message_hint parameters correctly, i'll try to see what i can do to fix the issue and let you know.

In the meantime, do you have any other moodle instance you can try it with?

[Cvmcosta]

Just to confirm, you are using this docker container, right?

[jeffmiko]

Yes that is the correct docker. I installed a clean Canvas in a virtual machine but I could not get the tool to work on that either. So I wanted to try Moodle so I used the easy docker container. I am going to install a moodle instance from scratch on virtual machine and test it

[Cvmcosta]

Got it, i think i found the error, or at least what triggers it, Moodle throws this error when the platform domain does not match the endpoint's domain.

I repeated your exact code (only changed database configuration and platform urls) and tested against the same Bitnami Container. When using http://localhost as the platform url and http://localhost/mod/lti/auth.php as the authentication url everything worked fine, but when i changed the authentication url to http://192.168.0.12/mod/lti/auth.php i got the same error:

provider:main No LTIK found +0ms
provider:main Request body:  [Object: null prototype] { error: 'invalid_request', state: 'd40b78ada4a75671' }

And when i changed the main platform url to http://192.168.0.12 to match the endpoint's domain everything started working again.

[Cvmcosta]

I see, i'm glad it worked out!