Nico64 Comments - Answer Overflow

Topics

Nico64

•Created by Nico64 on 4/14/2025 in #help

What is the "token" returned by auth.api.signinEmail?

Ok thank you 👍 There's no need to return, because it's get-session that's called next?

7 replies

•Created by heneftees on 4/14/2025 in #help

Backend Solution Better-Auth Integration

Not full-backend, but I have overrided some endpoints (signin/email, signup/email ans verify-email). That works well.

4 replies

•Created by s on 4/12/2025 in #help

guys, is it possible to do with better-aauth??

Or database hooks https://www.better-auth.com/docs/concepts/database#database-hooks

12 replies

•Created by s on 4/12/2025 in #help

guys, is it possible to do with better-aauth??

Maybe with the hooks https://www.better-auth.com/docs/concepts/hooks

12 replies

•Created by ZKRD on 4/11/2025 in #help

Stripe Plugin

To handle downgrades, there's the solution of setting up a task (a cron or similar) that will check the accounts to be downgraded every day. Sure, it would be more sexy if it were managed by Stripe

5 replies

•Created by Glen Kurio on 4/10/2025 in #help

Server side validation

As I said in my previous message, for example, I want to prevent someone who hasn't finished verifying their mail from receiving a bunch of emails every time they try to signin (also on update its email). https://github.com/better-auth/better-auth/issues/788#issuecomment-2735069860 It's also a precaution to preserve the behavior I use. After an upgrade there was a breaking change on the reset password. But about this token, can you please tell me if I should return it to the front or not? What's the use of this token?

18 replies

•Created by Glen Kurio on 4/10/2025 in #help

Server side validation

some routes I do nothing, I just forward the request to auth.api

18 replies

•Created by Glen Kurio on 4/10/2025 in #help

Server side validation

I know, I used authClient and set the handler to the server side. But there are some behaviors I'm not a fan of. For example, sending an email for each login attempt when a verification process is in progress. I prefer to have a little more control and manage each endpoint myself to perform certain data validations, etc. So I directly query my backend, which in turn executes auth.api. So, I'm wondering if I should return "token" to the front end, or if it's data only for the backend.

18 replies

•Created by Glen Kurio on 4/10/2025 in #help

Server side validation

Yes with auth.api.signinEmail but what is its use? To understand if I need it at some point

18 replies

•Created by Glen Kurio on 4/10/2025 in #help

Server side validation

ok thanks. What's it for then?

18 replies

•Created by Glen Kurio on 4/10/2025 in #help

Server side validation

const result: {
    redirect: boolean;
    token: string;
    url: string | undefined;
    user: {
        id: string;
        email: string;
        name: string;
        image: string | null | undefined;
        emailVerified: boolean;
        createdAt: Date;
        updatedAt: Date;
    };
}

const result: {
    redirect: boolean;
    token: string;
    url: string | undefined;
    user: {
        id: string;
        email: string;
        name: string;
        image: string | null | undefined;
        emailVerified: boolean;
        createdAt: Date;
        updatedAt: Date;
    };
}

Hey @KINFISH By the way, do you know if this token can/should be returned to the frontend or is it private data for the backend? Because I use auth.api.signInEmail() on the backend to signin users, I don't use authClient.

18 replies