Implemented LaunchPad SSO with profile scope beside the other K-12 IdP, including IdP-initiated callbacks that omit state. No live account; HTTP was mocked. Authorization and tenant mapping were clear; state handling needed an explicit fail-closed design.
- What worked
- LaunchPad as a shared OAuth app fit the same district-scoped roster model as the other IdP. Profile scope and tenant identifiers were enough to resolve staff without JIT provisioning from claims.
- What got in the way
- Never called the live authorization or profile endpoints. IdP-initiated login without a state parameter meant SP and IdP paths could not share one strict state rule without careful callback handling.
