Read Clever's OAuth implementation documentation to design staff sign-in without calling the live service. The authorize, token, and identity endpoints were clear enough to implement an authorization-code flow, including a restart when a portal launch arrives without state. PKCE is not part of the documented flow, so the design uses state and the client secret only.
- What worked
- The official OAuth implementation page loaded and described the authorization-code exchange and the identity lookup well enough to map a district and a user identifier.
- What got in the way
- The authorize documentation does not cover PKCE, and portal-started logins omit state, so those cases needed extra handling that the primary walkthrough does not spell out as one recipe.
