Auth: Expose the per-request Better Auth instance to server routes

Abierto
  • ¿Algo no está bien?
#661 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, authentication

Línea de trabajo

Start with the void/auth exports getUser, getSession and requireAuth, and with runVoidAuthMiddleware, which stores the per-request Better Auth instance under the Hono context key __voidAuth. The issue asks for a supported accessor such as getAuth(c) plus a decision on whether /.well-known/ OAuth discovery paths should be forwarded. Done means the maintainers have chosen an approach and a route can get the instance without the private key.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

I'd like a supported way to get the Better Auth instance that Void creates for the
current request, so that server routes can pass it to Better Auth plugin helpers.

Today void/auth exports getUser(), getSession() and requireAuth(), which cover
user and session checks, but it doesn't export the instance itself.

The only way I've found to reach the instance is to read the internal Hono context key "__voidAuth",
which isn't documented and could change in any release.

Use case

My app is an MCP server that uses Better Auth's OAuth provider, with the jwt() and
mcp() plugins from @better-auth/mcp. Several pieces of that setup need the
Better Auth instance as an argument, so I can't write them with the current
void/auth exports:

  1. The MCP route wraps its handler with requireMcpAuth(auth, handler, options) from
    @better-auth/mcp, which checks the OAuth access token on each request.
  2. MCP clients fetch OAuth discovery documents at the site root, e.g.
    /.well-known/oauth-protected-resource/mcp and
    /.well-known/oauth-authorization-server/api/auth. Void only forwards
    /api/auth/* to Better Auth, so I added a route under routes/.well-known/ that
    passes these requests to auth.handler(request).
  3. My sign-in and consent page loaders use auth.$context to count users through
    the database adapter, because the app allows only one account.

Current workaround

I read the instance from the Hono context in one helper function, and every route
calls that helper:

import type { Context } from "hono";
import type { betterAuth } from "better-auth";

type AuthInstance = ReturnType<typeof betterAuth>;

export function getAuthInstance(c: Context): AuthInstance {
  const auth = c.get("__voidAuth") as AuthInstance | undefined;
  if (!auth) {
    throw new Error('Void did not provide a Better Auth instance at "__voidAuth".');
  }
  return auth;
}

The workaround depends on runVoidAuthMiddleware, which calls
c.set("__voidAuth", auth) in Void's Better Auth runtime code. I checked that the key
is the same in 1.2.1 and 1.4.0. If the key is renamed, my MCP endpoint, the discovery
documents and the sign-in page all stop working, and the type cast means nothing
catches it at build time.

Proposal

I'd like void/auth to export a function that returns the current request's
instance, with the same request handling as requireAuth(c). For example:

import { getAuth } from "void/auth";

export const POST = defineHandler(async (c) => {
  const auth = getAuth(c);
  return requireMcpAuth(auth, handleMcpRequest, { resource })(c.req.raw);
});

I'd also like the return type to include the plugins from auth.ts, the same way
AuthUser and AuthSession now include plugin fields in 1.4.0, so that the
endpoints plugins add under auth.api type check without a cast.

If Void prefers not to expose the instance, I could instead use built-in support for
the two OAuth needs above. That would mean forwarding the /.well-known/ OAuth
discovery paths to Better Auth when the mcp() or oauthProvider() plugin is
enabled, and adding a documented way to protect a route with an OAuth access token.

Environment

  • void 1.4.0, @void/svelte 1.4.0
  • better-auth 1.7.12, @better-auth/mcp 1.7.12
  • Native Cloudflare deploy (Workers and D1)

Disclaimers

Written by Claude Opus 5, reviewed and edited by Humans.

Lenguaje dominante
TypeScript
Estrellas
627
Forks
66
Merge medio
14 h 17 min
PR fusionados (30 d)
200

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de voidzero-dev/void

Todos los issues de voidzero-dev/void

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.