Red Flag ManiaIntegrations
⌘ K
Public documentationManage integrations
Integration docsIntegration home ↗
LTI 1.3Available first

Other LTI 1.3 platforms

A standards-compliant platform can use the generic registration path without a provider-specific RFM implementation.

Platform requirements

The platform must support LTI 1.3 OIDC login initiation and signed resource-link launch messages.

  • Stable HTTPS issuer and public JWKS endpoint.
  • Client and deployment identifiers.
  • Authorization endpoint for OIDC login.
  • LtiResourceLinkRequest with required LTI 1.3 claims.
  • A stable learner subject within the registration.

Manual registration

Enter RFM’s public values in the platform, then attach the platform’s issuer, client ID, deployment ID, authorization endpoint, and JWKS URL to the RFM institution.