github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #1426] Feature Request / Question: External API Login in Next.js #8747

New Issue
Closed
opened 2026-04-13 03:56:31 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-13 03:56:31 -05:00
Owner
Copy Link

Originally created by @dev-SR on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1426

I'm using Next.js with a .NET API for authentication and want to integrate Better-Auth to handle sign-in via my external .NET API. Specifically, I need guidance on:

  1. Using Better-Auth Credentials to authenticate users against a external API (.NET in my case).
  2. Storing and managing the access token from the external API in cookies (or session storage) securely.
  3. Ensuring the token is available for authenticated requests in both client-side and server-side Next.js components.

With NextAuth.js, this is typically implemented:

import NextAuth from "next-auth";
import CredentialsProvider from "next-auth/providers/credentials";

export const authOptions = {
  providers: [
    CredentialsProvider({
      name: "Credentials",
      credentials: {
        username: { label: "Username", type: "text", placeholder: "john_doe" },
        password: { label: "Password", type: "password" },
      },
      async authorize(credentials, req) {
        const res = await fetch("http://127.0.0.1:4000/auth/login/", {
          method: "POST",
          headers: { "Content-Type": "application/json" },
          body: JSON.stringify({
            username: credentials.username,
            password: credentials.password,
          }),
        });

        const user = await res.json();

        if (!res.ok) {
          throw new Error(user.message || "Login failed");
        }

        return user;
      },
    }),
  ],
  callbacks: {
    async jwt({ token, user }) {
      if (user) {
        token.accessToken = user.token; // Store .NET API token in JWT
      }
      return token;
    },
    async session({ session, token }) {
      session.accessToken = token.accessToken;
      return session;
    },
  },
  secret: process.env.NEXTAUTH_SECRET,
  pages: {
    signIn: "/login",
  },
};

export default NextAuth(authOptions);

Thanks! 😊

Originally created by @dev-SR on GitHub (Feb 12, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1426 I'm using **Next.js** with a **.NET API** for authentication and want to integrate **Better-Auth** to handle sign-in via my external .NET API. Specifically, I need guidance on: 1. Using **Better-Auth Credentials** to authenticate users against a **external API (.NET in my case)**. 2. Storing and managing the **access token from the external API** in **cookies** (or session storage) securely. 3. Ensuring the token is available for authenticated requests in both **client-side** and **server-side** Next.js components. With **NextAuth.js**, this is typically implemented: ```ts import NextAuth from "next-auth"; import CredentialsProvider from "next-auth/providers/credentials"; export const authOptions = { providers: [ CredentialsProvider({ name: "Credentials", credentials: { username: { label: "Username", type: "text", placeholder: "john_doe" }, password: { label: "Password", type: "password" }, }, async authorize(credentials, req) { const res = await fetch("http://127.0.0.1:4000/auth/login/", { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ username: credentials.username, password: credentials.password, }), }); const user = await res.json(); if (!res.ok) { throw new Error(user.message || "Login failed"); } return user; }, }), ], callbacks: { async jwt({ token, user }) { if (user) { token.accessToken = user.token; // Store .NET API token in JWT } return token; }, async session({ session, token }) { session.accessToken = token.accessToken; return session; }, }, secret: process.env.NEXTAUTH_SECRET, pages: { signIn: "/login", }, }; export default NextAuth(authOptions); ``` Thanks! 😊
GiteaMirror added the locked label 2026-04-13 03:56:31 -05:00
GiteaMirror commented 2026-04-13 03:56:33 -05:00
Author
Owner
Copy Link

@margaretjoanmiller commented on GitHub (Feb 13, 2025):

I'm in the exact same boat so I'd love to see what folks say about this

<!-- gh-comment-id:2657911633 --> @margaretjoanmiller commented on GitHub (Feb 13, 2025): I'm in the exact same boat so I'd love to see what folks say about this
GiteaMirror commented 2026-04-13 03:56:34 -05:00
Author
Owner
Copy Link

@jslno commented on GitHub (Feb 14, 2025):

you could just write your own plugin with a sign-up / sign-in endpoint. This allows passing more credentials than just username and password

<!-- gh-comment-id:2659752454 --> @jslno commented on GitHub (Feb 14, 2025): you could just write your own plugin with a sign-up / sign-in endpoint. This allows passing more credentials than just username and password
GiteaMirror commented 2026-04-13 03:56:35 -05:00
Author
Owner
Copy Link

@strangemodern commented on GitHub (Feb 21, 2025):

Subscribed. I'm doing something similar with a Nest API, but keep running into errors when implementing plugin after hooks.

<!-- gh-comment-id:2673299354 --> @strangemodern commented on GitHub (Feb 21, 2025): Subscribed. I'm doing something similar with a Nest API, but keep running into errors when implementing plugin after hooks.
GiteaMirror commented 2026-04-13 03:56:36 -05:00
Author
Owner
Copy Link

@itisvincent commented on GitHub (Mar 7, 2025):

you could just write your own plugin with a sign-up / sign-in endpoint. This allows passing more credentials than just username and password

is there any document to guide us to do that? thanks

<!-- gh-comment-id:2705516478 --> @itisvincent commented on GitHub (Mar 7, 2025): > you could just write your own plugin with a sign-up / sign-in endpoint. This allows passing more credentials than just username and password is there any document to guide us to do that? thanks
GiteaMirror commented 2026-04-13 03:56:38 -05:00
Author
Owner
Copy Link

@jslno commented on GitHub (Mar 7, 2025):

is there any document to guide us to do that? thanks

https://www.better-auth.com/docs/guides/your-first-plugin
https://www.better-auth.com/docs/concepts/plugins#creating-a-plugin

https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/api/routes/sign-in.ts
https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/api/routes/sign-up.ts

<!-- gh-comment-id:2705881066 --> @jslno commented on GitHub (Mar 7, 2025): > is there any document to guide us to do that? thanks https://www.better-auth.com/docs/guides/your-first-plugin https://www.better-auth.com/docs/concepts/plugins#creating-a-plugin https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/api/routes/sign-in.ts https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/api/routes/sign-up.ts
GiteaMirror commented 2026-04-13 03:56:41 -05:00
Author
Owner
Copy Link

@whitemyrat commented on GitHub (Mar 8, 2025):

Has anyone had success with an external API?

<!-- gh-comment-id:2708529779 --> @whitemyrat commented on GitHub (Mar 8, 2025): Has anyone had success with an external API?
GiteaMirror commented 2026-04-13 03:56:42 -05:00
Author
Owner
Copy Link

@christianwebdev200 commented on GitHub (Apr 16, 2025):

Joining the boat here, I hope they will support external API or include an adapter for NestJs and Laravel. I want to escape the Next-Auth nightmare haha!

<!-- gh-comment-id:2808075863 --> @christianwebdev200 commented on GitHub (Apr 16, 2025): Joining the boat here, I hope they will support external API or include an adapter for NestJs and Laravel. I want to escape the Next-Auth nightmare haha!
GiteaMirror commented 2026-04-13 03:56:42 -05:00
Author
Owner
Copy Link

@lagroms commented on GitHub (May 30, 2025):

I'm in the same situation, I'd like to use my external API as well. Anything that won't make me use auth.js 🤢

<!-- gh-comment-id:2921295351 --> @lagroms commented on GitHub (May 30, 2025): I'm in the same situation, I'd like to use my external API as well. Anything that won't make me use auth.js 🤢
GiteaMirror commented 2026-04-13 03:56:44 -05:00
Author
Owner
Copy Link

@MuhammadM1998 commented on GitHub (Jun 25, 2025):

This would be great!

<!-- gh-comment-id:3006129977 --> @MuhammadM1998 commented on GitHub (Jun 25, 2025): This would be great!
GiteaMirror commented 2026-04-13 03:56:45 -05:00
Author
Owner
Copy Link

@frectonz commented on GitHub (Aug 11, 2025):

To integrate this into better auth the authentication server would need to conform to some kind of standard like OIDC, which Better Auth supports. If the server doesn't conform to a standard then it doesn't make sense to add this to the core of better auth, so i recommend creating a separate plugin.

<!-- gh-comment-id:3176803699 --> @frectonz commented on GitHub (Aug 11, 2025): To integrate this into better auth the authentication server would need to conform to some kind of standard like OIDC, which Better Auth supports. If the server doesn't conform to a standard then it doesn't make sense to add this to the core of better auth, so i recommend creating a separate plugin.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#8747
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?