Open snmigerl opened 5 years ago
Thanks for contacting us, @snmigerl. We don't have anything in place to help out with this. You'll have to handle this yourself using a background task to track the last activity.
Under the approach recommended by @mkArtakMSFT, how would a background task go about determining the timestamp of the last activity? Or would the timestamp need to be recorded manually by a service injected into each component the user could potentially access?
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
At the moment I'm looking for an option to automatically logout a user from my serverside-blazor-app when he's inactive for a definded amount of time.
The old way of doing this by configuring the cookie expiration that worked in mvc don't seem to work.
ANy suggestions or hints, or is it planned to implement an easy way to do that?
Thanks Michael