Files
zooqueen 231838cbee dataroom: sign in with Hanzo takes the OIDC callback
hanzo.id is an OIDC provider and returns an id_token. The provider declared
idToken: false, so next-auth used the plain-OAuth2 callback and openid-client
threw on a token response it could not account for:

  id_token detected in the response, you must use client.callback()
  instead of client.oauthCallback()

A signing-in user saw only /api/auth/signin?error=OAuthCallback and a red
"Try signing in with a different account." — which points at the account, and
the account was never the problem.

What made this easy to call working: the sign-in HANDOFF is healthy. The button
reaches hanzo.id with the right client_id and an allowlisted redirect_uri, and
a real login page renders. Only the trip back was broken, and nothing before
the callback shows it. Verifying a login means completing one.

profile() reads sub/name/email/picture/owner, all of which the id_token
carries, so the mapping is unchanged; userinfo stays declared for the claims
the token does not hold.
2026-08-14 17:44:20 -07:00
..
2025-01-17 16:08:09 +01:00
2024-10-10 16:26:35 +05:30
2025-03-24 19:42:30 +04:00