rtmorgan Comments - Answer Overflow

Topics

rtmorgan

•Created by chumpo on 3/11/2025 in #help

Set tables in auth not public

@MaveriX89 that is definitely a solid approach for using a custom ORM schema within better-auth, but - if used with PostgreSQL - would not change what PostgreSQL schema the objects were created in and would default to them being created in the public schema (short a previous database/user customization with the PostgreSQL environment) unless a pgSchema object from "drizzle-orm/pg-core" was used in combination with the Drizzle pgTable objects.
The schema referenced in the OP question was an 'auth' Postgresql schema as opposed to the default use of the 'public' PostgreSQL schema to store better-auth database objects.

8 replies

•Created by chumpo on 3/11/2025 in #help

Set tables in auth not public

I don't remember with javascript/typescript PostgreSQL drivers, but you may need to escape the space and equal characters in the connection URI: connectionString: [existing postgresql connecting string]?option=-c%20search_path%3Dauth

8 replies

•Created by chumpo on 3/11/2025 in #help

Set tables in auth not public

One option would be to set the default schema for the PostgreSQL user you plan to use before generating/migrating the schema: Given a better-auth database user 'authuser' and a schema 'auth': ALTER USER authuser SET SEARCH_PATH TO auth; Another way to set this (again before generating/migrating the better-auth schema) is within the connectionString that you are using with your better-auth config by appending '?option=-c search_path=<schema_name>' to the connection URI : connectionString: [existing postgresql connecting string]?option=-c search_path=auth For both these approaches, make sure the PostgreSQL schema exists and the PostgreSQL user has permissions to use it.

8 replies

•Created by sanser on 3/7/2025 in #help

401 doing listActiveSubscriptions on server side

Can you try it with headers set (similar to the getSession call): const data = await auth.api.listActiveSubscriptions({ headers: request.headers });

22 replies

•Created by sanser on 3/7/2025 in #help

401 doing listActiveSubscriptions on server side

Can you share your route structure?

22 replies

•Created by sanser on 3/7/2025 in #help

401 doing listActiveSubscriptions on server side

What does your hooks.server.ts look like? Are you using the svelteKitHandler?

22 replies

•Created by sanser on 3/7/2025 in #help

401 doing listActiveSubscriptions on server side

Which authentication (email and password, social, etc) are you using prior to the route that uses that +page.server.ts? Also, how are you navigating to that route - from a redirect or from a direct navigation link? thanks

22 replies

•Created by sanser on 3/7/2025 in #help

401 doing listActiveSubscriptions on server side

Can you test it with a new session / new session cookie as 1.2 changed the session token validation check on the HMAC signature. If you are using a older, but still valid pre 1.2 cookie, it is not going to pass checks in v1.2 and higher getSession from what I can tell. This might be a long shot but worth testing if you recently upgraded.

22 replies

•Created by sanser on 3/7/2025 in #help

401 doing listActiveSubscriptions on server side

Hi @sanser - what version of better-auth are you currently using? Also, can you confirm that your request.headers above contains a valid better-auth session token?

22 replies

•Created by Vivillies on 3/6/2025 in #help

[SvelteKit] Stripe checkout redirects to /api/auth/dashboard

thank you for patiently testing my theories 😀 I'm glad it's working!

10 replies

•Created by Vivillies on 3/6/2025 in #help

[SvelteKit] Stripe checkout redirects to /api/auth/dashboard

Can you test with setting 'successUrl' to the full url of the dashboard, "http://localhost:5173/dashboard" thank you - I believe there is url parsing logic (internally) on the options that will support using a full url as well.

10 replies

•Created by Vivillies on 3/6/2025 in #help

[SvelteKit] Stripe checkout redirects to /api/auth/dashboard

What is your 'baseURL' set to in your authClient config? thank you

10 replies

•Created by Vivillies on 3/6/2025 in #help

[SvelteKit] Stripe checkout redirects to /api/auth/dashboard

Could you post the portion of your source code where you are calling client.subscription.upgrade and setting the successUrl? thank you

10 replies

•Created by vamshinenu on 3/3/2025 in #help

Session returns null, v.1.2

Did you test it with a recent, non-expired cookie? If so, definitely test it with a new session / new session cookie as 1.2 changed the validation check on the HMAC signature. A pre 1.2 cookie is not going to pass checks in getSession from what I can tell. This might be a long shot but worth testing if you didn't make any other changes to your codebase other than update to 1.2

2 replies

•Created by Duki on 2/28/2025 in #help

Is it possible to set callbackUrl on server-side email sign Ups?

I just wanted to make sure you understood there was a callbackURL available on the server api call.

12 replies

•Created by Duki on 2/28/2025 in #help

Is it possible to set callbackUrl on server-side email sign Ups?

It's supported on the server-side as well with 'auth.api.sendVerificationEmail' - there is a '/send-verification-email' endpoint used by it that accepts a callbackURL for after the email verification: https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/api/routes/email-verification.ts#L78

12 replies

•Created by Duki on 2/28/2025 in #help

Is it possible to set callbackUrl on server-side email sign Ups?

I believe callbackURL is a key within body like name, email, password:

body: {
        name: username,
        email,    
        password,
        callbackURL
    }

body: {
        name: username,
        email,    
        password,
        callbackURL
    }

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

12 replies

•Created by braveheartwilliam on 2/26/2025 in #help

GetSession not returning user and/or session objects, here’s details

try removing the 'asResponse:true' in your +hooks.server.ts: const sessionResponse = await auth.api.getSession({ headers: event.request.headers, asResponse: true <--- remove this }); you don't need to get a Web API Response object here to get the session and user returned from getSession but rather just normal data returned from getSession will contain them

3 replies

•Created by braveheartwilliam on 2/25/2025 in #help

getSession returns/is null in hooks.server.ts (svelte5/sveltekit)

I don't believe you can set the cookie with the token value returned from the auth.api.signInEmail call. This is a valid token (meaning it matches the token value stored in the session table), but the cookie's token value needs to be set to a value of the token concatenated with a '.' and then the hmac-sha256 hash of the token using your auth secret so that it can be validated during subsequent usage. If instead you use the response object returned from auth.api.signInEmail, there will be a 'set-cookie' header that contains this full token value (token + hmac) which you can extract and set as a cookie within your action.

4 replies

•Created by roze789 on 2/20/2025 in #help

How to check permissions on server side

What do the member records look like in table 'member'? Is there a valid record for a organization member with role 'admin'?

25 replies