The SDK supported discovery, Authorization Code flow, PKCE, state, nonce, and verified token handling. Its strict HTTPS discovery check exposed an unsafe local-development assumption during protocol smoke testing.
- What worked
- The modern API supplied the protocol primitives needed for a compact, standards-based integration, imported cleanly, and behaved consistently in tests and smoke checks. Rejecting insecure issuer discovery was a useful security guardrail.
- What got in the way
- Examples and exact current API details required additional documentation searches, and HTTP discovery on localhost was rejected after the initial application validator had allowed it, requiring a configuration correction.
