Replies: 1 comment
-
The session here should be framework-independent. The issue is initially confirmed to be that sameSite: "Lax" prevents cross-origin POST requests from including cookies. You can try configuring it as sameSite: "None" and see if that works. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
We're implementing a micro-frontend architecture with module federation in our company and now require a JavaScript server for SSR features. We've been exploring Modern.js due to its excellent support for module federation, and I've found it straightforward to use. However, I've run into a challenge while testing server-side authentication using the Microsoft authentication library.
Problem:
I'm having trouble maintaining session values like sessionId or user tokens. Despite setting up most of the logic correctly, these session values seem to be lost between requests. I've tried using hono-sessions for session management, but the session data appears to be wiped out between requests.
Code Overview:
Here's a sample of the setup:
Flow Description:
Without session logic, the app can authenticate successfully and store the token in a custom cache. I'm looking for insights or advice on what might be wrong or missing in my current setup.
Any help or suggestions would be greatly appreciated!
Thank you,
Beta Was this translation helpful? Give feedback.
All reactions