Skip to content

[lti1.3] add launch messages expiration - #1171

Open
anthonygego wants to merge 2 commits into
mainfrom
lti_launch_expire
Open

anthonygego wants to merge 2 commits into
mainfrom
lti_launch_expire

Conversation

@anthonygego

@anthonygego anthonygego commented Sep 11, 2026

Copy link
Copy Markdown
Member

This PR adds support for expiring LTI1.3 launch messages from the database storage. These documents are not expected to live longer than the LTI session.

  • It adds the expirable index on the mongo collection
  • It adds the expiration date given by lti1p3 lib through the LaunchDataStorage interface.
  • It provides a migration for the collection, making documents expire the next day (the default from lti1p3)
  • Since launch messages should be available during the whole LTI session lifetime for AGS service to send scores, it disable LTI session lifetime extension. It only lives the time set in config file.
  • It sets the launch message expiration time to the flask session expiration time.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@anthonygego

Copy link
Copy Markdown
Member Author

@nrybowski Pushed commit to disable LTI sessions expiration extension and put the same expiration time to sessions and launch message, so that the launch messages will expire with the session.

This branch has not been deployed

No deployments
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.

2 participants