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

Using auth.api.getAccessToken with Prisma + GitHub throws FAILED_TO_GET_A_VALID_ACCESS_TOKEN - 403 Forbidden #1300

New Issue
Closed
opened 2026-03-13 08:31:56 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 08:31:56 -05:00
Owner
Copy Link

Originally created by @MathiasWP on GitHub (Jun 3, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

I'm using BetterAuth on a SvelteKit project with Prisma. I have generated the prisma schemas, and they all work as expected. However, when i try to the following in my SvelteKit server load method the auth.api.getAccessToken throws a FAILED_TO_GET_A_VALID_ACCESS_TOKEN 403 Forbidden error:

const { accessToken } = await auth.api.getAccessToken({
	body: {
		providerId: 'github'
	},
	headers: request.headers
});

My current workaround is to do the following:

import { auth } from '$auth/config';
import { prisma } from '$prisma/client';
import { redirect } from '@sveltejs/kit';
import type { LayoutServerLoad } from './$types';

export const load: LayoutServerLoad = async ({ request }) => {
	const session = await auth.api.getSession({
		headers: request.headers
	});

	if (!session) {
		redirect(302, '/sign-in');
	}

	const account = await prisma.account.findFirst({
		where: {
			providerId: 'github',
			userId: session.user.id
		}
	});

	// For some reason this throws a FAILED_TO_GET_A_VALID_ACCESS_TOKEN with 403 Forbidden
	// May need to create an issue on the betterauth repo, or try to figure out why this happens
	// const { accessToken } = await auth.api.getAccessToken({
	// 	body: {
	// 		providerId: 'github'
	// 	},
	// 	headers: request.headers
	// });

	if (!account?.accessToken) {
		redirect(302, '/sign-in');
	}

	return {
		session,
		accessToken: account.accessToken
	};
};

So the access token is correctly stored in my Prisma DataBase (as far as i can understand). Why does the auth.api.getAccessToken fail?

Current vs. Expected behavior

I'm expecting this method to work out of the box, since my Prisma schemas are the exact ones generated from BetterAuth.

What version of Better Auth are you using?

1.2.8

Provide environment information

- OS: MacOs 15.5
- NodeJS 22
- pnpm 10
- `prisma` `6.8.2` with `@prisma/extension-accelerate` `2.0.1`

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

Backend

Auth config (if applicable)

export const auth = betterAuth({
	database: prismaAdapter(prisma, {
		provider: 'postgresql'
	}),
	baseURL: BETTER_AUTH_URL,
	secret: BETTER_AUTH_SECRET,
	socialProviders: {
		github: {
			clientId: OAUTH_GITHUB_CLIENT_ID,
			clientSecret: OAUTH_GITHUB_CLIENT_SECRET,
			scope: ['repo', 'read:org']
		}
	}
});

Additional context

My Prisma Client setup:

import { PRISMA_DATABASE_URL } from '$env/static/private';
import { withAccelerate } from '@prisma/extension-accelerate';
import { PrismaClient } from '../generated/prisma/client';

const prisma = new PrismaClient({
	datasources: {
		db: {
			url: PRISMA_DATABASE_URL
		}
	}
}).$extends(withAccelerate());

export { prisma };
Originally created by @MathiasWP on GitHub (Jun 3, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce I'm using BetterAuth on a SvelteKit project with Prisma. I have generated the prisma schemas, and they all work as expected. However, when i try to the following in my SvelteKit server load method the `auth.api.getAccessToken` throws a FAILED_TO_GET_A_VALID_ACCESS_TOKEN 403 Forbidden error: ```ts const { accessToken } = await auth.api.getAccessToken({ body: { providerId: 'github' }, headers: request.headers }); ``` My current workaround is to do the following: ```ts import { auth } from '$auth/config'; import { prisma } from '$prisma/client'; import { redirect } from '@sveltejs/kit'; import type { LayoutServerLoad } from './$types'; export const load: LayoutServerLoad = async ({ request }) => { const session = await auth.api.getSession({ headers: request.headers }); if (!session) { redirect(302, '/sign-in'); } const account = await prisma.account.findFirst({ where: { providerId: 'github', userId: session.user.id } }); // For some reason this throws a FAILED_TO_GET_A_VALID_ACCESS_TOKEN with 403 Forbidden // May need to create an issue on the betterauth repo, or try to figure out why this happens // const { accessToken } = await auth.api.getAccessToken({ // body: { // providerId: 'github' // }, // headers: request.headers // }); if (!account?.accessToken) { redirect(302, '/sign-in'); } return { session, accessToken: account.accessToken }; }; ``` So the access token is correctly stored in my Prisma DataBase (as far as i can understand). Why does the `auth.api.getAccessToken` fail? ### Current vs. Expected behavior I'm expecting this method to work out of the box, since my Prisma schemas are the exact ones generated from BetterAuth. ### What version of Better Auth are you using? 1.2.8 ### Provide environment information ```bash - OS: MacOs 15.5 - NodeJS 22 - pnpm 10 - `prisma` `6.8.2` with `@prisma/extension-accelerate` `2.0.1` ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript export const auth = betterAuth({ database: prismaAdapter(prisma, { provider: 'postgresql' }), baseURL: BETTER_AUTH_URL, secret: BETTER_AUTH_SECRET, socialProviders: { github: { clientId: OAUTH_GITHUB_CLIENT_ID, clientSecret: OAUTH_GITHUB_CLIENT_SECRET, scope: ['repo', 'read:org'] } } }); ``` ### Additional context My Prisma Client setup: ```ts import { PRISMA_DATABASE_URL } from '$env/static/private'; import { withAccelerate } from '@prisma/extension-accelerate'; import { PrismaClient } from '../generated/prisma/client'; const prisma = new PrismaClient({ datasources: { db: { url: PRISMA_DATABASE_URL } } }).$extends(withAccelerate()); export { prisma }; ```
GiteaMirror commented 2026-03-13 08:31:57 -05:00
Author
Owner
Copy Link

@chroxify commented on GitHub (Jun 6, 2025):

Hey @MathiasWP, just ran into this myself so dug into it a little and seems like this was related to #2764 which was merged with v1.2.9-beta.6 and upwards. Upgrading to it fixed this!

@chroxify commented on GitHub (Jun 6, 2025): Hey @MathiasWP, just ran into this myself so dug into it a little and seems like this was related to #2764 which was merged with [v1.2.9-beta.6](https://github.com/better-auth/better-auth/releases/tag/v1.2.9-beta.6) and upwards. Upgrading to it fixed this!
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
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#1300
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?