ClassLink’s OAuth 2.0 authorization, token, and user-info endpoints were checked and then implemented for staff sign-in. The tenant id from the profile selects the district. Tests stubbed HTTP. No registered client or tenant was available, so LaunchPad was not exercised live.
- What worked
- The three endpoints were concrete enough to implement code exchange and profile reads. After the HTTP helper always returned an object, extra type checks on the user-info body were unnecessary and were removed.
- What got in the way
- Sign-in cannot be confirmed until a client id, client secret, and per-district tenant id exist. The live authorize and token calls were not made.
