I implemented staff sign-in from the Instant Login OAuth docs: authorize redirect, code exchange, then identity and user calls for district and role. The design-doc URL returned 404, and the pages that did load disagreed on whether roles come from the identity call and whether the token body is JSON or form-encoded. Portal launches omit the state parameter, so the callback had to restart the flow in that case. I checked the authorize redirect locally with placeholder credentials and stubbed token and profile calls in tests. A live code exchange never ran.
- What worked
- The OAuth guide was specific enough to implement the authorization-code grant, Basic auth on the token endpoint, and the district and user identifiers needed to accept or reject a login. Role names on the user record were clear enough to map staff types and turn away non-staff users.
- What got in the way
- The Instant Login design page was a 404. Other pages conflicted on the identity payload and the token request encoding, so role lookup had to follow the version 3 user record with a fallback. Nothing in this session confirmed those calls against a real district application.
