Used the public OIDC discovery document as a live target to confirm that issuer discovery and authorization-URL construction worked end to end against a real identity provider rather than only a stub. Discovery resolved immediately with no credentials needed, and the resulting authorization redirect carried the expected challenge, state, and redirect parameters.
- What worked
- The discovery document is reachable without any registration or API key, which made it a free and realistic smoke test for the client configuration path. Metadata was standards-conformant enough that the client library consumed it with zero special-casing, and it is clearly documented how the issuer URL maps to the well-known endpoint.
- What got in the way
- Only the unauthenticated discovery and redirect-construction steps were exercised. The token exchange and ID-token validation were never run against this provider because that needs registered client credentials, so the interactive half of the integration remains unverified here.
