feature-request: add dotnet/C# support #1287

New Issue

GiteaMirror · 2026-03-13T08:31:24-05:00

GiteaMirror commented

2026-03-13 08:31:24 -05:00

Originally created by @biegehydra on GitHub (May 31, 2025).

I'd like there to be some better auth nuget packages that add support for better auth. Let's use this issue to see how much the community wants it. React to this issue if you are interested

With enough traction, I will start a repo and begin working on this

Originally created by @biegehydra on GitHub (May 31, 2025). I'd like there to be some better auth nuget packages that add support for better auth. Let's use this issue to see how much the community wants it. React to this issue if you are interested With enough traction, I will start a repo and begin working on this

GiteaMirror closed this issue

2026-03-13 08:31:24 -05:00

GiteaMirror commented

2026-03-13 08:31:24 -05:00

@yigsvnsla commented on GitHub (Jun 1, 2025):

You can easily use the open-api implementation that already comes in the core plugins.

@yigsvnsla commented on GitHub (Jun 1, 2025): You can easily use the open-api implementation that already comes in the core plugins.

GiteaMirror commented

2026-03-13 08:31:25 -05:00

@biegehydra commented on GitHub (Jun 1, 2025):

I'd have to look into it but there's a lot more that goes into it. A good package would have a middleware, repository service, authentication/authorization service, endpoint/controller attributes, etc

@biegehydra commented on GitHub (Jun 1, 2025): I'd have to look into it but there's a lot more that goes into it. A good package would have a middleware, repository service, authentication/authorization service, endpoint/controller attributes, etc

GiteaMirror commented

2026-03-13 08:31:25 -05:00

@ChristPetitjean commented on GitHub (Jun 2, 2025):

Hello, i was wondering if I was alone with this exact requirement.

I was thinking of a nuxt frontend with a dotnet backend to be able to scale only the backend if needed but keep the front with some ssr capabilities.

So, yes, I follow you 😜

@ChristPetitjean commented on GitHub (Jun 2, 2025): Hello, i was wondering if I was alone with this exact requirement. I was thinking of a nuxt frontend with a dotnet backend to be able to scale only the backend if needed but keep the front with some ssr capabilities. So, yes, I follow you 😜

GiteaMirror commented

2026-03-13 08:31:25 -05:00

@ChristPetitjean commented on GitHub (Jun 3, 2025):

I'd have to look into it but there's a lot more that goes into it. A good package would have a middleware, repository service, authentication/authorization service, endpoint/controller attributes, etc

For better compatibilty with dotnet, you should not provide endpoints.
"Endpoint / controller / AWS Lambda / Azure function, etc.", are all possible solutions and choosing one will prevent other (of course)
So maybe just a set of handful services that everyone if free to map to their prefered/mandatory stack with some guidance.

Something like :

Service:

public interface IBetterAuthService 
{
    SignInResult HandleSignIn(SignInInput input);
}

Usage:

Call IBetterAuthService service from your prefered stack.
You have to map:

for signin:
- route: /auth/signin
- verb: POST
- service: IBetterAuthService
- method to call: HandleSignIn
for singup:
- route: /auth/signup
- verb: POST
- service: IBetterAuthService
- method to call: HandleSignUp

Some naive examples below.

Minimal API:

app.MapPost("/auth/signin", [FromBody] SignInInput input, [FromService] BetterService betterService) => 
    betterService.HandleSignIn(signInInput)?.ToResult() ?? Results.Problem("Something gone wrong !");

Controller:

[ApiController]
[Route("[controller]")]
public class AuthController : ControllerBase
{
    private readonly IBetterAuthService _betterAuthService;
    private AuthController(IBetterAuthService betterAuthService)
    {
        _betterAuthService = betterAuthService;
    }

    [HttpPost]
    public IActionResult SignIn(SignInInput signInInput)
    {
        var result = _betterAuthService.HandleSignIn(signInInput);
        if (result == null)
        {
            return Results.Problem("Something gone wrong !");
        }
        return Ok(result);
    }
}

Azure function

public class SigninEndpoint(
    ILogger<SigninEndpoint> logger,
    IBetterAuthService betterAuthService)
{
    [Function("signin")]
    public async Task<IActionResult> Run(
        [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "auth/signin")]
        HttpRequest req,
        SignInInput input,
        CancellationToken cancellationToken)
    {
        var result = betterAuthService.HandleSignIn(signInInput);
        if (result == null)
        {
            return Results.Problem("Something gone wrong !");
        }
        return Ok(result);
    }
}

@ChristPetitjean commented on GitHub (Jun 3, 2025): > I'd have to look into it but there's a lot more that goes into it. A good package would have a middleware, repository service, authentication/authorization service, endpoint/controller attributes, etc For better compatibilty with dotnet, you should not provide endpoints. "Endpoint / controller / AWS Lambda / Azure function, etc.", are all possible solutions and choosing one will prevent other (of course) So maybe just a set of handful services that everyone if free to map to their prefered/mandatory stack with some guidance. Something like : ## Service: ```csharp public interface IBetterAuthService { SignInResult HandleSignIn(SignInInput input); } ``` # Usage: Call `IBetterAuthService` service from your prefered stack. You have to map: - for signin: - route: /auth/signin - verb: POST - service: IBetterAuthService - method to call: HandleSignIn - for singup: - route: /auth/signup - verb: POST - service: IBetterAuthService - method to call: HandleSignUp Some naive examples below. ## Minimal API: ```csharp app.MapPost("/auth/signin", [FromBody] SignInInput input, [FromService] BetterService betterService) => betterService.HandleSignIn(signInInput)?.ToResult() ?? Results.Problem("Something gone wrong !"); ``` ## Controller: ```csharp [ApiController] [Route("[controller]")] public class AuthController : ControllerBase { private readonly IBetterAuthService _betterAuthService; private AuthController(IBetterAuthService betterAuthService) { _betterAuthService = betterAuthService; } [HttpPost] public IActionResult SignIn(SignInInput signInInput) { var result = _betterAuthService.HandleSignIn(signInInput); if (result == null) { return Results.Problem("Something gone wrong !"); } return Ok(result); } } ``` ## Azure function ```csharp public class SigninEndpoint( ILogger<SigninEndpoint> logger, IBetterAuthService betterAuthService) { [Function("signin")] public async Task<IActionResult> Run( [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "auth/signin")] HttpRequest req, SignInInput input, CancellationToken cancellationToken) { var result = betterAuthService.HandleSignIn(signInInput); if (result == null) { return Results.Problem("Something gone wrong !"); } return Ok(result); } } ```

GiteaMirror commented

2026-03-13 08:31:25 -05:00

@yigsvnsla commented on GitHub (Jun 3, 2025):

I'd like there to be some better auth nuget packages that add support for better auth. Let's use this issue to see how much the community wants it. React to this issue if you are interested

With enough traction, I will start a repo and begin working on this

I don't know what your experience is like as a dev, but just google a little and investigate how the open API standard works and you'll realize that you don't need to write almost any code since you could delegate everything to a service layer or directly within the services you already have, call the fetch client.

https://learn.microsoft.com/en-us/openapi/kiota/install?tabs=bash

https://stackoverflow.com/questions/73877723/how-to-generate-openapi-client-sdk-project-in-net-core

@yigsvnsla commented on GitHub (Jun 3, 2025): > I'd like there to be some better auth nuget packages that add support for better auth. Let's use this issue to see how much the community wants it. React to this issue if you are interested > > With enough traction, I will start a repo and begin working on this I don't know what your experience is like as a dev, but just google a little and investigate how the open API standard works and you'll realize that you don't need to write almost any code since you could delegate everything to a service layer or directly within the services you already have, call the fetch client. https://learn.microsoft.com/en-us/openapi/kiota/install?tabs=bash https://stackoverflow.com/questions/73877723/how-to-generate-openapi-client-sdk-project-in-net-core

GiteaMirror commented

2026-03-13 08:31:26 -05:00

@biegehydra commented on GitHub (Jun 3, 2025):

@yigsvnsla Quite experienced. I'm very familiar with OpenApi specs. The goal is not for my asp.net to be a client, its for it to be the server... I don't want to have a separate js backend. I want my asp.net backend to be able to hook into the better-auth framework and be able to issue tokens, manage sessions, authenticate, authorize, etc. All by only interacting with the database that follows the better-auth specs.

I'm sure I could create an authentication service that acts as a proxy to a javascript backend but that has many downsides:

Requires extra application
Extra rounded-trip (increased delay)
Lacks actual asp.net integration (as mentioned before, authorization attributes, services, identity integration)
Makes transactions & consistency more difficult
Monorepos are easier to manage and track issues/logs

It seems like you are not familiar with asp.net because it should be pretty clear why a nuget package would be quite useful. All I want to do to use better auth is this:

dotnet add package BetterAuth

builder.Services.AddBetterAuth();

app.UseBetterAuth();

[Authorize(AuthenticationSchemes = "BetterAuth")] 
public class MyController
{
    // Protected by better-auth
    [HttpGet("/api/my-endpoint")]
    public string MyEndpoint() => "Success";
}

Also, being able to inject an authentication/authorization service directly into my blazor components would be a godsend.

Your solution would require about 100x more work on my end.

@biegehydra commented on GitHub (Jun 3, 2025): @yigsvnsla Quite experienced. I'm very familiar with OpenApi specs. The goal is not for my asp.net to be a client, its for it to be the server... I don't want to have a separate js backend. I want my asp.net backend to be able to hook into the better-auth framework and be able to issue tokens, manage sessions, authenticate, authorize, etc. All by only interacting with the database that follows the better-auth specs. I'm sure I could create an authentication service that acts as a proxy to a javascript backend but that has many downsides: - Requires extra application - Extra rounded-trip (increased delay) - Lacks actual asp.net integration (as mentioned before, authorization attributes, services, identity integration) - Makes transactions & consistency more difficult - Monorepos are easier to manage and track issues/logs It seems like you are not familiar with asp.net because it should be pretty clear why a nuget package would be quite useful. All I want to do to use better auth is this: ```bash dotnet add package BetterAuth ``` ```cs builder.Services.AddBetterAuth(); app.UseBetterAuth(); [Authorize(AuthenticationSchemes = "BetterAuth")] public class MyController { // Protected by better-auth [HttpGet("/api/my-endpoint")] public string MyEndpoint() => "Success"; } ``` Also, being able to inject an authentication/authorization service directly into my blazor components would be a godsend. Your solution would require about 100x more work on my end.

GiteaMirror commented

2026-03-13 08:31:26 -05:00

@yigsvnsla commented on GitHub (Jun 3, 2025):

@yigsvnslaTengo bastante experiencia. Estoy muy familiarizado con las especificaciones de OpenAPI. El objetivo no es que mi ASP.NET sea un cliente, sino el servidor. No quiero tener un backend de JavaScript independiente. Quiero que mi backend de ASP.NET cumpla con las especificaciones/marco de Better-Auth y pueda emitir tokens, gestionar sesiones, autenticar, autorizar, etc. Todo ello interactuando únicamente con la base de datos que cumple con dichas especificaciones.

Estoy seguro de que podría crear un servicio de autenticación que actúe como proxy de un backend de JavaScript, pero eso tiene muchas desventajas:

Requiere aplicación adicional

Viaje de ida y vuelta adicional (mayor retraso)

Carece de integración real con asp.net (como se mencionó anteriormente, atributos de autorización, servicios, integración de identidad)

Dificulta las transacciones y la consistencia

Los monorepositorios son más fáciles de administrar y rastrear problemas/registros.

Parece que no estás familiarizado con ASP.NET, ya que debería estar bastante claro por qué un paquete NuGet sería tan útil. Lo único que quiero hacer para usar una mejor autenticación es esto:

dotnet add package BetterAuth
builder.Services.AddBetterAuth();

app.UseBetterAuth();

[Authorize(AuthenticationSchemes = "BetterAuth")]
public class MyController
{
// Protected by better-auth
[HttpGet("/api/my-endpoint")]
public string MyEndpoint() => "Success";
}
Su solución requeriría aproximadamente 100 veces más trabajo de mi parte.

I understand your point, but keep in mind that better-auth is a project in development. Underneath, better-auth uses better-fetch, which is basically a wrapper for "fetch" on the client side, and on the server side, things are getting more complex.

That said, I feel like better-auth is still in the development phase, and I don't think they'll be willing to create an SDK for other languages unless the community itself pushes for it with its own implementations.

On the other hand, you don't really need to modify much to use better-auth. I prefer to have it separate rather than within my API. Just keep in mind that one day I want to switch from better-auth to another authentication provider (Keycloak, Zitadel, Clerk, my own custom authentication API). I'll need to decouple a few things, which would take time and complexity.

That's my opinion, hehe. I'm just reflecting on the topic.

@yigsvnsla commented on GitHub (Jun 3, 2025): > [@yigsvnsla](https://github.com/yigsvnsla)Tengo bastante experiencia. Estoy muy familiarizado con las especificaciones de OpenAPI. El objetivo no es que mi ASP.NET sea un cliente, sino el servidor. No quiero tener un backend de JavaScript independiente. Quiero que mi backend de ASP.NET cumpla con las especificaciones/marco de Better-Auth y pueda emitir tokens, gestionar sesiones, autenticar, autorizar, etc. Todo ello interactuando únicamente con la base de datos que cumple con dichas especificaciones. > > Estoy seguro de que podría crear un servicio de autenticación que actúe como proxy de un backend de JavaScript, pero eso tiene muchas desventajas: > > * Requiere aplicación adicional > * Viaje de ida y vuelta adicional (mayor retraso) > * Carece de integración real con asp.net (como se mencionó anteriormente, atributos de autorización, servicios, integración de identidad) > * Dificulta las transacciones y la consistencia > * Los monorepositorios son más fáciles de administrar y rastrear problemas/registros. > > Parece que no estás familiarizado con ASP.NET, ya que debería estar bastante claro por qué un paquete NuGet sería tan útil. Lo único que quiero hacer para usar una mejor autenticación es esto: > > dotnet add package BetterAuth > builder.Services.AddBetterAuth(); > > app.UseBetterAuth(); > > [Authorize(AuthenticationSchemes = "BetterAuth")] > public class MyController > { > // Protected by better-auth > [HttpGet("/api/my-endpoint")] > public string MyEndpoint() => "Success"; > } > Su solución requeriría aproximadamente 100 veces más trabajo de mi parte. I understand your point, but keep in mind that better-auth is a project in development. Underneath, better-auth uses better-fetch, which is basically a wrapper for "fetch" on the client side, and on the server side, things are getting more complex. That said, I feel like better-auth is still in the development phase, and I don't think they'll be willing to create an SDK for other languages unless the community itself pushes for it with its own implementations. On the other hand, you don't really need to modify much to use better-auth. I prefer to have it separate rather than within my API. Just keep in mind that one day I want to switch from better-auth to another authentication provider (Keycloak, Zitadel, Clerk, my own custom authentication API). I'll need to decouple a few things, which would take time and complexity. That's my opinion, hehe. I'm just reflecting on the topic.

GiteaMirror referenced this issue

2026-04-13 03:50:23 -05:00

[GH-ISSUE #1287] I would like to use google authentication using subdomains, but my subdomains are dynamic. #8678

GiteaMirror referenced this issue

2026-04-15 15:24:53 -05:00

[GH-ISSUE #1287] I would like to use google authentication using subdomains, but my subdomains are dynamic. #17309

GiteaMirror referenced this issue

2026-04-17 16:23:07 -05:00

[GH-ISSUE #1287] I would like to use google authentication using subdomains, but my subdomains are dynamic. #26001

Sign in to join this conversation.

Branches Tags

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-227a091249

dependabot/github_actions/github-actions-98f3470200

2026-05-13/ci/stabilize-docker-startup

dependabot/npm_and_yarn/samlify-2.13.0

changeset-release/main

main

2026-05-22/chore/adopt-agents-md

2026-05-22/refactor/string-case-utils

2026-05-14/fix/passkey-verify-error-and-claim

changeset-release/next

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-07/fix/admin-set-password-upsert

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-provider-backchannel-logout-next

feat/oauth-idp-initiated-bounce

refactor/sign-in-challenges

2026-04-21/fix/oauth-rfc-input-validation

fix/release-notes-new-packages

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

2026-04-12/security/dynamic-baseurl-proxy-trust-default

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

claude/slack-update-stripe-docs-consistency-8Sc0w

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-24/fix/update-user-info-on-link

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#1287