Hi,
We have a Laravel application with a login form where we use the Memberstack DOM package to authenticate users.
In our app, we’ve added a middleware that runs on each internal API request. This middleware verifies the user by calling Memberstack’s “get member details” endpoint using the access token.
I wanted to clarify the “session duration” setting, which logs users out after n days of inactivity.
What exactly counts as “inactivity” here?
For example, if a user logged in 14 days ago but has been actively using our app during that time—and on every request we call Memberstack to fetch their profile using the token—does that count as activity? Or is inactivity only based on interaction directly with Memberstack (events like "Logged in", "Plan Added", "Member Updated")?
Does calling memberstack api from serverside is counted as activity?
1 comment
Hey Muhammad Shahshan,
I believe the session is active based on the client-side actions that a user might take which interacts with Memberstack but just to be sure I am tagging Tyler Bell and Josh Lopez to see if they have more insights to share.
That being said, here's a documentation on session management where you can checkout the session refresh functionality to see if that helps your project to keep the session active as per your requirement.
Hope this gives you some idea.
Please sign in to leave a comment.