Forum Discussion
LearningLocker responds with 403 Forbidden when trying to read xAPI statement
For future reference:
I figure it out, the xAPI client was configured to only allow writing statements. The enterpreise version behaves different in that it actually responds with 403, whereas the open source server didn't even bother.
According to the documentation:
If you receive an “unauthorised error” from this API, you can use the three checks below via the Client UI. To remove the need for these checks, Learning Locker will automatically create a new client when a new store is created, the new client is enabled by default, with the “All” scope, and the LRS set to the new store. To avoid unauthorised errors, try to use the new client and remember the checks below if you edit or create a client manually.
- Check that the client is enabled.
- Check that the “All” scope is selected under the “xAPI” heading.
- Check that an LRS is selected.
(https://docs.learninglocker.net/http-xapi-statements/#get-statements)
Related Content
- 2 months ago