implement-storage-adapter

The four required Ltix.StorageAdapter callbacks are get_registration/2, get_deployment/2, store_nonce/2, and validate_nonce/2. They manage LTI 1.3 registrations, deployments, and nonces, returning protocol-driven shapes like LTix.Registration and LTix.Deployment to coordinate your schema with the library.

Nonce validation should be handled atomically within the store_nonce/2 and validate_nonce/2 callbacks to prevent race conditions. The implementation requires an Ecto schema for the Nonce model and careful lifecycle handling to ensure secure LTI 1.3 tool launches.

Yes, you need Ecto schemas for LTI registrations and deployments when using Ltix. You must build a storage context, such as Ltix.Lti, and define corresponding schemas that satisfy the LTix.Registration and LTix.Deployment protocol implementations required by the adapter callbacks.

The best way to configure a storage adapter for LTI 1.3 is to enable it in your Elixir config files by pointing the Ltix configuration to your custom adapter module. This involves defining the required schemas, implementing the four callbacks, and wiring the storage context to the application's configuration.

Yes, you can upsert LTI deployments automatically through the storage adapter. The implementation provides strategies for upsert versus manual deployment creation, allowing you to choose how the get_deployment/2 callback manages deployment records based on your specific application needs.