Skip to content

Modifies Materia OboNode server-side code to work with the upcoming Materia release.#2139

Draft
FrenjaminBanklin wants to merge 7 commits intomasterfrom
dev/materia-lti1p3-patch
Draft

Modifies Materia OboNode server-side code to work with the upcoming Materia release.#2139
FrenjaminBanklin wants to merge 7 commits intomasterfrom
dev/materia-lti1p3-patch

Conversation

@FrenjaminBanklin
Copy link
Copy Markdown
Contributor

@FrenjaminBanklin FrenjaminBanklin commented Dec 17, 2025

Materia's upcoming release removes support for LTI 1.1 in favor of LTI 1.3, requiring changes on the Obojobo end to have it act as a basic LTI 1.3 platform.

This update also pins a more recent commit of the upstream ims-lti repository to add newly required headers to outcomes requests sent to an LMS upon completing a module assessment.

This requires a few additional environment variables:

  • MATERIA_LTI_VERSION: Either 1.1 or 1.3.
  • OBO_LTI_CLIENTID: This should be an alphanumeric string value determined by the platform (Obojobo) that needs to be matched in a corresponding LTI registration in any relevant tools. It can be an arbitrary alphanumeric string.
  • OBO_LTI_UUID: This is a UUID value that is generated by the Materia LTI registration.
  • OBO_JWT_KEY: This is an alphanumeric string value.
  • OBO_PRIVATE_RSA_KEY: This is an RSA key generated by a command like openssl genrsa -out private.pem 2048. Ideally condensed to a single string with newline characters and bookends preserved.
  • OBO_LTI_DEPLOYMENTID: This is a UUID value that is generated by the Materia LTI registration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant