Skip to content

Sign in with email and a passkey

PortalCLIBeginner~15 min

Signing in with an email link now ends with a passkey. You open the link in your inbox, then confirm with your fingerprint, face or device PIN, and only then are you signed in. You do this step yourself, in your browser. An agent cannot do it for you, because a passkey answers only to the person who holds it. If you sign in with GitHub, Google or Apple instead, nothing changes.

This applies on servers where passkey registration is switched on. Hadron's hosted server is one of them; you can check yours at /capabilities, which lists passkey-registration when it is on. Why the step exists is in Why email sign-in needs a passkey.

If you already have a passkey

  1. Ask for the email link as usual, from the portal's sign-in page or from hadron auth login, and open it in the same browser.
  2. The link takes you to a Hadron page titled Confirm it's you. Click Use passkey and approve with your fingerprint, face or device PIN.
  3. You land where you were going: the portal, or the terminal that started hadron auth login, which stores its key only now.

You have 10 minutes from opening the link to finish the passkey step. The email link itself expires a short while after it is sent; the email says how long.

If this is your first passkey

Your first passkey is any passkey you add while your account has no unrevoked passkey: your very first, or a replacement after you removed them all. An account with no passkey cannot finish an email sign-in yet, so the page says Add a passkey to finish signing in. Opening the first link does not sign you in and does not add anything. You have 30 minutes for the whole detour.

  1. Click Add a passkey.
  2. Confirm who you are again. Hadron emails you a second link, and you must open it in the same browser; the first link does not count. The confirmation it gives lasts 10 minutes, so add the passkey promptly.
  3. Name the passkey (for example "Work laptop") and click Add my first passkey.
  4. Click Continue signing in, then Use passkey. Your new passkey signs you in right away.

Your first passkey has a cooling-off window of at least 72 hours (a server may set it longer; the page you see states its length). It signs you in immediately, but anything it signs (a signed node or an approved grant) stays pending until the window ends. Hadron emails you whenever a passkey is added. For a first passkey, that email contains a Remove this passkey link that works without signing in and only until the window ends. A passkey you add later, vouched for by one you already hold, has no cooling-off window and no cancel link; the email tells you to remove it from your account's passkey page if it was not you. A passkey still inside its cooling-off window cannot vouch for another one, so wait until the window ends before adding a second. (Removing every passkey and starting again is the recovery path below.)

If you start from the CLI

hadron auth login opens your browser and waits. Do the steps above in the browser. The CLI never touches the passkey; it receives a key only after you finish. The browser is the one on the machine where you ran the command. It waits 15 minutes for the whole sign-in. On a headless host, the passkey step needs a browser on another machine, and the callback workaround in Install the hadron CLI still applies. Adding a first passkey can take longer than that. If it times out, nothing was stored: finish in the browser, then run hadron auth login again.

If you lose every passkey

Sign in with GitHub, Google or Apple, if you have linked one to your account. From the account's passkey page, remove the lost passkeys and add a new one. The new passkey signs you in right away, and its signatures stay pending for the cooling-off window (72 hours or more). If you have no linked provider account, contact Hadron support.

If you remove a passkey you did not add

The Remove this passkey link in the email sent when a first passkey is added (a later passkey's email has none) revokes that passkey, ends every sign-in it completed, and ends the keys those sign-ins created, including keys created from them afterwards. It also cancels anything that passkey signed. Your other sessions and keys keep working. After that, the CLI answers with an ordinary invalid-credential error; run hadron auth login again.

What stays the same

  • GitHub, Google and Apple sign-ins have no extra step.
  • Keys and tokens you already hold keep working, and minting a new one asks for no extra factor.
  • A magic link on its own never removes a passkey.

Not decided

These are open questions, not behaviour: what support may do for someone who has lost every passkey and has no linked provider account, any exception for demo accounts, and whether the steps for adding a first passkey will change. The steps above are what the server does today, not a promise that they stay. Nothing here promises a bypass.

If something goes wrong

At the passkey step, a flow that is expired, used, or opened in a different browser shows one fixed page, This sign-in link can't be used, and Hadron does not say which of those it was. An email link that has itself expired or been used before you reach that step can instead answer with a plain "Invalid or expired token" error. Either way, go back to the sign-in page and ask for a new link.