6 replies

Handling stateless account data with access and refresh tokens on the server side / NextJs

Next.js

@Better Auth Currently the behavior of

auth.api.getAccessToken

auth.api.getAccessToken

(server api) doesn't properly handle refreshing tokens when calling from a RSC. I have

nextCookies

nextCookies

already enabled in my auth config. It's not clear to me if this is a bug or a limitation of Next itself.

If calling

getAccessToken

getAccessToken

using the authClient, all works as expected. This makes sense as the set cookie headers are hitting the browser. That said, for this specific context, using the access token client-side is off limits. We have a external, server-only API needing the access token. The only work-around I have found so far is calling

auth.api.getAccessToken

auth.api.getAccessToken

within the proxy.ts file. This correctly handles the set cookies header and will rotate the better-auth.account_data cookie when the refresh token is called. This feels heavy-handed having to call this on every request. Any other suggestions? Also, is this a bug with stateless account data or a Next limitation?

Better Auth•6d ago•

6 replies

shu-sin

Handling stateless account data with access and refresh tokens on the server side / NextJs

Next.js

@Better Auth Currently the behavior of

auth.api.getAccessToken

auth.api.getAccessToken

(server api) doesn't properly handle refreshing tokens when calling from a RSC. I have

nextCookies

nextCookies

already enabled in my auth config. It's not clear to me if this is a bug or a limitation of Next itself.

If calling

getAccessToken

getAccessToken

auth.api.getAccessToken

auth.api.getAccessToken

Handling stateless account data with access and refresh tokens on the server side / NextJs

Similar Threads

Handling stateless account data with access and refresh tokens on the server side / NextJs

Similar Threads

Similar Threads

Similar Threads