Load
Explore posts from serversBABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
I am thinking I am returning the wrong thing or Iām not adding the correct header to the response
12 replies
BABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
I am still running into this issue after testing those though š
12 replies
BABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
I think I missed the cross-domain cookies section of the better-auth documentation. so I am going to do a deep dive into that.
https://www.better-auth.com/docs/integrations/hono#cross-domain-cookies
12 replies
BABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
I think I am missing a key detail about what header || cookie I must return from the "auth/login" route. I have been scraping the documentation about this issue and havent seen anything about building in a serverless env or how to handle Cookies / what cookies need to be saved. I feel this lack of docs is because better-auth has been built mostly with Next.js and other full stack frameworks in mind.
12 replies
BABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
@Ping - So my problem is as follows:
1. I have a lambda function that uses Hono since there is a simple integration with the framework and I can specify different routes/middleware per route in my API. I am using the "/auth/login" route to log into my application ("duh"). This route uses the auth.api.signInEmail() function to sign into my app using better auth, which in turn creates a session in my backend (hosted by neon postgres db w/drizzle ORM). This function returns the following object while creating a session in the "session" table:
{
redirect: false,
token: '5imOHhOhIvERV3Dp1h1x1fbburDEbaut',
url: undefined,
user: {
id: 'bvDuazbLUB7S9AbA2tnZOcH0B78YMsBO',
email: '[email protected]',
name: 'Leo Cucinell',
image: null,
emailVerified: false,
createdAt: 2025-04-02T02:13:22.822Z,
updatedAt: 2025-04-02T02:13:22.822Z
}
}
I am assuming that I am supposed to encrypt the "token" item in the above object to add as a cookie as a reponse from my hono/lambda route. I am adding a link to my example repo below. This repo uses AWS CDK to deploy to AWS and outputs an API URL and API Key. If you are going to replicate this in your environment, you will need to set up the following:
1. a postgres database with DATABASE_URL in the .env file
2. a BETTER_AUTH_SECRET in .env
3. and a BETTER_AUTH_URL set to the API url that is returned when building the API the first time.
Github Repo: https://github.com/leocucinell/aws.better-auth-serverless-api
12 replies
BABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
@Ping - lol thanks for the heads up. yes no rush, going to be continuing to work on this in my free time so I will let you know whats up and share my findings!
12 replies
BABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
@Ping -
I definitely can! However, I am at work at the moment, just saw this on my phone. I can get back to you and update this thread around 4 pm PST. Thanks!
12 replies
BABetter Auth
ā¢Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
I am also wondering if I need to encrypt the cookie on the server, then send it to the react app. I am assuming yes, since that is most secure, and would love to see fi anyone has implemented it!
12 replies
hono aws lambda 404 issues
Oh my gosh. I had app.get() and was using the wrong method.
yikes... can't believe I did that š
Thanks for answering my post @Arjix !
I obviously still have much to learn about hono, I will be adding the logger and seeing what I can do!
I obviously still have much to learn about hono, I will be adding the logger and seeing what I can do!
14 replies
hono aws lambda 404 issues
https://hono.dev/docs/api/routing#basic
Yes it looks like the woldcard routing works in hono!
14 replies
hono aws lambda 404 issues
the 404 originates from hono. Since the lambda function is being triggered, the ApiGateway + lambda are configured correctly.
the path "/*" is valid in express and I might have just lazily transferred my knowledge over. Ill dive deeper into the hono docs to verify. I did test with multiple other paths ("/", "/test", etc...) and all returned 404s.
I think you might be in the right direction with the hono basePath. I will test and let you know.
Thanks for responding!:hono:š¤
14 replies