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

getSession({ headers})) fails if JWT is in Bearer even with valid cookie #423

New Issue
Closed
opened 2026-03-13 07:45:17 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 07:45:17 -05:00
Owner
Copy Link

Originally created by @daveycodez on GitHub (Dec 18, 2024).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

Use the JWT plugin and pass the "Bearer JWT" Authorization header.

This will cause getSession to fail, I assume because it doesn't support JWT bearers. I'm using Bearer JWT for my Neon Postgres Proxy API, but I also need to use getSession in that proxy. My current hack is to check cookies for auth-token and omit the authorization header if it is present. However, for my Capacitor app I pass the normal Bearer token (not JWT) for all requests.

IMO the ideal solution would be to authorize JWT's in getSession, but a second best fix would be to attempt to authenticate based on the Authorization Bearer header, and if that fails fallback to the cookie

Current vs. Expected behavior

getSession should still work if there is a valid cookie but an invalid authorization header.

What version of Better Auth are you using?

1.2.2

Provide environment information

Next.js 15 Pages Router
Capacitor

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
import { jwt, bearer } from "better-auth/plugins"
import { NeonHTTPDialect } from "kysely-neon"

export const auth = betterAuth({
    database: {
        dialect: new NeonHTTPDialect({
            connectionString: process.env.DATABASE_URL!,
        }),
        type: "postgres"
    },
    emailAndPassword: { enabled: true },
    plugins: [
        jwt({
            jwks: {
                keyPairConfig: {
                    alg: "ES256"
                }
            }
        }),
        bearer()
    ],
    trustedOrigins: [
        "http://localhost:3000",
    ]
})

Additional context

No response

Originally created by @daveycodez on GitHub (Dec 18, 2024). ### Is this suited for github? - [X] Yes, this is suited for github ### To Reproduce Use the JWT plugin and pass the "Bearer JWT" Authorization header. This will cause getSession to fail, I assume because it doesn't support JWT bearers. I'm using Bearer JWT for my Neon Postgres Proxy API, but I also need to use getSession in that proxy. My current hack is to check cookies for auth-token and omit the authorization header if it is present. However, for my Capacitor app I pass the normal Bearer token (not JWT) for all requests. IMO the ideal solution would be to authorize JWT's in getSession, but a second best fix would be to attempt to authenticate based on the Authorization Bearer header, and if that fails fallback to the cookie ### Current vs. Expected behavior getSession should still work if there is a valid cookie but an invalid authorization header. ### What version of Better Auth are you using? 1.2.2 ### Provide environment information ```bash Next.js 15 Pages Router Capacitor ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" import { jwt, bearer } from "better-auth/plugins" import { NeonHTTPDialect } from "kysely-neon" export const auth = betterAuth({ database: { dialect: new NeonHTTPDialect({ connectionString: process.env.DATABASE_URL!, }), type: "postgres" }, emailAndPassword: { enabled: true }, plugins: [ jwt({ jwks: { keyPairConfig: { alg: "ES256" } } }), bearer() ], trustedOrigins: [ "http://localhost:3000", ] }) ``` ### Additional context _No response_
GiteaMirror added the bug label 2026-03-13 07:45:17 -05:00
GiteaMirror commented 2026-03-13 07:45:18 -05:00
Author
Owner
Copy Link

@daveycodez commented on GitHub (Dec 18, 2024):

This is my hack atm

 const headers = new Headers()

    request.headers.entries().forEach(([key, value]) => {
        if (key == "authorization" && request.headers.get("cookie")?.includes("auth-token")) return
        headers.set(key, value)
    })

    const session = await auth.api.getSession({ headers })
@daveycodez commented on GitHub (Dec 18, 2024): This is my hack atm ```ts const headers = new Headers() request.headers.entries().forEach(([key, value]) => { if (key == "authorization" && request.headers.get("cookie")?.includes("auth-token")) return headers.set(key, value) }) const session = await auth.api.getSession({ headers }) ```
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 bug
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#423
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?