You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not at all sure if it's appropriate to post my findings here. Sorry if it isn't. But here it goes.
I was working with an Express/MSAL example from MS Learning and had the session in memory with express-session. Being annoyed with having te signin at every node restart I decided to use session-file-store.
Most of the time it does not work. After a signin only a part of data is stored. Things like the token-cache and account info are missing from the session. On occasion I do get a valid session. Say once every 10 tries.
Posted a question about this on Stackoverflow (no replies as of now)
If you would like to see how I implemented the module: the app is here on github, I've commented session-file-store out in favor of better-sqlite3-session-store.
Looking at the last updates I was wondering if this module is still alive. Looks like the last update is over a year ago. Would be a shame, seems to be an elagant solution.
The text was updated successfully, but these errors were encountered:
Not at all sure if it's appropriate to post my findings here. Sorry if it isn't. But here it goes.
I was working with an Express/MSAL example from MS Learning and had the session in memory with express-session. Being annoyed with having te signin at every node restart I decided to use session-file-store.
Most of the time it does not work. After a signin only a part of data is stored. Things like the token-cache and account info are missing from the session. On occasion I do get a valid session. Say once every 10 tries.
Posted a question about this on Stackoverflow (no replies as of now)
If you would like to see how I implemented the module: the app is here on github, I've commented session-file-store out in favor of better-sqlite3-session-store.
Looking at the last updates I was wondering if this module is still alive. Looks like the last update is over a year ago. Would be a shame, seems to be an elagant solution.
The text was updated successfully, but these errors were encountered: