Repository navigation
@hanzo/ui 8.32.0: SignInPanel, the one-click sign-in every Hanzo site shares - #313
Merged
Merged
Conversation
… shares A site's front page drew its own sign-in, and its Google and GitHub buttons handed the browser to hanzo.ai/login without the provider, so the person pressed Google a second time there. @hanzo/ui/auth now has the one way every Hanzo site leaves to sign in: - handoff(request, way): from the site's own authorize request (its client, callback, state and PKCE challenge; the verifier stays on the site), a provider goes straight to IAM's authorize ON hanzo.ai with `provider`, which sends the browser to Google or GitHub at once and takes the provider's return on hanzo.ai, so the session lands there. An email goes to hanzo.ai/login with login_hint, a new account to /signup, another account to the chooser. - SignInPanel: the headline, one line, Continue with Google and GitHub, an email box, Create account and the terms, drawn from @hanzo/ui components and free of any framework, so a Next export and a Vite app draw it alike. No credential is typed on the site.
This was referenced Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Pressing Continue with Google or GitHub on hanzo.bot or hanzo.app landed on hanzo.ai/login without the provider, so people pressed Google a second time there. hanzo.team draws its own copy of the panel.
What (
@hanzo/ui/auth)handoff(request, way, signin?): from the site's own authorize request (getSigninUrl; PKCE verifier stays on the site):https://hanzo.ai/v1/iam/oauth/authorize?…&provider=…. IAM redirects to Google or GitHub at once (checked live) and takes the provider's return on hanzo.ai, so the session lands there.hanzo.ai/loginwithlogin_hint; a new account to/signup; another account to the chooser (prompt=select_account).SignInPanel: headline, one line, Continue with Google and GitHub, an email box, Create account and the terms line. Built from@hanzo/uicomponents with no framework code, so the Next.js export (hanzo-inc/app) and the Vite app (hanzo.team) draw it alike. No credential is typed on the site.Testing
vitest run src/auth/signin-panel.test.tsx: 6 passed, including everyhandoffaddress and a press on Google that leaves straight for the provider.tsc: no errors in the new files (checked locally against older borrowed dependencies, so the full run is CI's).Next
lib/auth/signin.tsuseLeave) goes throughhandoff, so hanzo.app and hanzo.bot are one click.SignInPanel.