Sign players in without running your own auth server.

What you get

• Email codes

  Players sign in with a six-digit code sent to their inbox. There are no passwords to store or reset.

• Discord sign-in

  Connect your Discord application and let players use the account they already have for gaming.

• Guests that upgrade safely

  Players start without an account and add an email or Discord identity later. Their user ID stays the same, and accounts are never merged silently.

• Device sign-in for games

  Show a short code in your game and let the player approve it on a phone or PC. No browser runs inside the game.

• Isolated projects

  Each project is its own tenant with its own issuer, users, applications and sign-in settings. Tokens issued for one project are rejected by another.

• Developer console

  Create projects, register applications, turn on sign-in methods, and manage users, sessions and audit events.

SDKs for where your players are

Three SDKs, each with a runnable example in the repository. The snippets below are taken from those examples.

const auth4 = new Auth4BrowserClient({
  issuer: "https://auth.auth4.dev/t/ten_replace_with_your_tenant",
  clientId: "cli_replace_with_your_browser_client",
  redirectUri: `${window.location.origin}${window.location.pathname}`,
});

export async function handleProtectedRequest(
  request: Request,
  client: Auth4ServerClient,
): Promise<Response> {
  const claims = await authenticateRequest(request, client);
  if (!claims) return unauthorizedResponse();
  return Response.json({ subject: claims.sub, tenant: claims.tenant_id });
}

_client = new Auth4Client(new Auth4ClientOptions
{
    TenantId = tenantId,
    ClientId = clientId,
    AuthOrigin = authOrigin,
    Transport = new UnityWebRequestTransport(),
});