Unable to get cookies onAfterLogin
I am triying to acces req.cookies but it is always empty.
export const onAfterLogin: OnAfterLoginHook = async ({
providerId,
user,
oauth,
prisma,
req,
}) => {
try {
console.log(providerId); console.log(user); console.log(oauth); console.log(prisma); // console.log(req); console.log('cookies', req.cookies); const cookies = req.cookies;
} catch (error) { // Log error but don't block login process console.error('Error in onAfterLogin:', error); } };
console.log(providerId); console.log(user); console.log(oauth); console.log(prisma); // console.log(req); console.log('cookies', req.cookies); const cookies = req.cookies;
} catch (error) { // Log error but don't block login process console.error('Error in onAfterLogin:', error); } };
5 Replies
Hi @julien. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, I can see that you're having an issue with accessing cookies in the
onAfterLogin hook in Wasp.
The issue you're experiencing is likely related to how Wasp handles authentication. According to the documentation, Wasp currently uses sessions that are stored in localStorage on the client and in the database on the server, rather than using cookies:
Wasp's auth uses sessions to keep track of the logged-in user. The session is stored in localStorage on the client and in the database on the server. Under the hood, Wasp uses the excellent Lucia Auth v3 library for session management.
Wasp Auth Documentation
This explains why req.cookies is empty - Wasp's current authentication implementation doesn't use cookies by default.
There has been an ongoing discussion in the Wasp community about switching from JWT + localStorage to sessions + cookies for authentication, as evidenced by the GitHub issue #573. However, it appears this change hasn't been fully implemented yet:
In this PR https://github.com/wasp-lang/wasp/pull/1625 we started using sessions with the Lucia lib, but we didn't change to cookies.If you need to work with cookies in your authentication flow, you might need to implement a custom solution or wait for Wasp to fully support cookie-based authentication, which seems to be in their roadmap based on the discussions in the GitHub issues. For now, you should focus on working with the session data that's available through the user object and the database, rather than trying to access cookies. I hope this helps clarify why you're not seeing any cookies in your hook! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @julien, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
Which cookies are you trying to get? Did you add anything in the cookies yourself?
yes it is a visitor id from fingerprint.js
and it is in the cookie
Your client and server apps are two different things, you can't get client app cookies in the server app @sodic invoking the extra explanation
Hey @julien, I recommend reading up on Cookies: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Cookies
If you're still unclear after understanding that, ping me and we'll figure it out 🙂
@miho anything particular you were hoping I share?
MDN Web Docs
Using HTTP cookies - HTTP | MDN
A cookie (also known as a web cookie or browser cookie) is a small piece of data a server sends to a user's web browser. The browser may store cookies, create new cookies, modify existing ones, and send them back to the same server with later requests. Cookies enable web applications to store limited amounts of data and remember state informatio...