Launch flow
A launch is a short, validated exchange. The player never interprets raw LMS claims.
End-to-end sequence
- 1
The LMS initiates OIDC login for an installed RFM tool.
- 2
RFM creates exact state and nonce values and redirects to the LMS authorization endpoint.
- 3
The LMS posts a signed LTI launch to the RFM callback.
- 4
RFM validates the platform key, issuer, audience, deployment, nonce, message type, role, and resource link.
- 5
RFM resolves the learner, entitlement, enrollment, and pinned published course version.
- 6
RFM issues a short-lived, single-use handoff that the player exchanges for its session.
LMS → RFM login → LMS authorization → RFM callback RFM validation → published version → single-use player handoff
Failure behavior
An invalid signature, replayed state, unknown deployment, unauthorized learner, or unmapped resource link stops before player access. Diagnostics show a safe explanation and correlation value, never the raw token.