add-lti-launch

You add LTI 1.3 launch support to a Phoenix application by wiring login and launch routes, configuring HTTPS, and setting up session handling to integrate securely with LMS platforms. This involves starting Ltix.JWT.KeySet.EtsCache in your supervision tree.

LTI launch often fails in a cross-origin iframe because standard session cookies are blocked. You must specifically secure cross-origin iframe sessions using custom pipeline configurations to ensure the LMS platform can interact with your Phoenix app without losing session state.

Yes, you need separate pipelines for LTI launch and post-launch interactions. The launch flow pipeline omits CSRF protection to allow the initial LMS redirect, while the post-launch pipeline applies standard CSRF protection to secure subsequent app interactions.

The OIDC login-to-launch flow in Elixir validates the LMS platform identity request, establishes a secure session, and processes the LTI 1.3 launch payload. It requires starting the JWT KeySet cache and wiring dedicated Phoenix routes to complete the end-to-end flow.

Prerequisites for testing an end-to-end LTI 1.3 launch include configuring HTTPS, starting the Ltix.JWT.KeySet.EtsCache in your supervision tree, and wiring the lti_launch and lti pipelines. You also need an LMS platform configured to target your Phoenix application endpoints.