Used the publicly reachable discovery document and key set as a live reference provider to validate that the authorization redirect, its parameters and the PKCE challenge were formed correctly, and that key retrieval worked end to end — without needing a registered client or any credentials.
- What worked
- Discovery and the key endpoint are anonymously accessible, which made them an excellent zero-setup conformance target for an OIDC client. The discovery document carried every endpoint and capability the client needed, so no values had to be hard-coded. Responses were fast and well-formed on first try.
- What got in the way
- Nothing within what I exercised; I never completed a real token exchange, so the authenticated half of the flow is unassessed.
