4 Replies
We have a problem in such a case:
- the first user logs in, performs some actions on the site that should later display a notification to him
- logout
- the second user logs in and receives notifications from the first user
for init Novu session we use
when user logout we use:
@SuPP
I see we are missing the logout function in headless
@SuPP
When second user log-in, are you calling
initializeSession
again?
calling initializeSession
again should generate new session for this second user and clear old session of first userthe headless on the front-end should be client-only, I think, so it wouldn't really be able to take information from another user.
Are you sure you change the subscriber id when you log in?
In addition, the socket immediately detects that you are no longer focused on the application or that you have logged out and changes the user status to inactive, I don't think a logout function is needed, it is done automatically.