Hey guys,
what is the intended behavior when I block an user which has an active session right now? Is it comparable to an IP-ban?
I have a Flutter web app which loads perfectly fine on Google Chrome, Safari and so on.
Step 1: Signing user in on web app on Google Chrome -> Everything fine Step 2: Block Account in the appwrite backend Step 3: Any action in the web app -> Nothing is loading anymore properly which is good Step 3: Opening the web app on Safari (not signed in) -> Nothing is loading anymore properly
Only the account itself is blocked. You might still have a session in safari...can you try opening a private browsing window?
You were right. It was about an old session on Safari. (I asked the person I was testing it on and he told me that he has not been using Safari for the web app before - maybe he forgot). After deleting all sessions before going through the steps, it worked the intended way.
But still:
- Is it a good approach to delete all sessions when blocking a user? There might be another one trying to access the web app from this computer and browser.
- How long are sessions stored? -> Auth Security Tab ✅
That sounds like a good feature request. Would you be able to create a GitHub issue for it?
Just created one https://github.com/appwrite/appwrite/issues/6061 - Thank you very much for your responses so far 🙂 Should this be marked in any way since there wont be a discussion here anymore I suppose
Thank you! You can update the title of the post with the prefix [SOLVED]
[SOLVED] Behavior after blocking an user
Recommended threads
- Images/Videos in storage appearing broke...
I am running into a storage issue after upgrading my self-hosted Appwrite instance , all of my previously uploaded images and videos are now showing as broken i...
- executeFunction intermittently throws Fo...
Environment: Flutter app using the Appwrite Flutter SDK, calling executeFunction for [describe endpoint, e.g. live-stream-related function]. *Description*: Int...
- How to update from 1.8.1 to 1.9.6
Due to the number of issues reported in version 1.9.5, I am hesitant to proceed with the update. Could anyone advise if version 1.9.6 is stable and resolves tho...