thank you @Thomas Broyer for providing very important and different approach i will try and then what was the working of app ,i will inform you
On Thursday, April 4, 2024 at 7:52:15 PM UTC+5:30 Thomas Broyer wrote: > On Thursday, April 4, 2024 at 2:21:36 PM UTC+2 [email protected] > wrote: > > ok, thanks again @Thomas Broyer for provide me the information on session > and cookies > > and also read this below conditions and let me this working is wrong or > right ...... > > 1)in current situation in my flask app multiple user login possible but > browsers also have different means one user login on one browser and if > users are same on same browser then it works properly but if user is same > and again same user login then generate new session id inside the cookies > and this session id also replace in all tabs of the same browser where > this specific user already login > > > That's right, which is why you'd want your app to somehow detect when it > loads that a session already exists and can just be reused, rather than > showing the login screen and forcing the creation of a new session, > replacing the previous one and possibly impacting other tabs. > > 2)i wants to test my flask app in same browser but i wants to different > user login and if new user login then previous user don't logout > automatically > > > Use incognito/private mode. In Firefox you can use "containers" to, well, > containerize, tabs with different sets of cookies: > https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/ > > > so read all above conditions or doubts and then provide me suggestions > On Thursday, April 4, 2024 at 3:13:20 PM UTC+5:30 Thomas Broyer wrote: > > Not sure what more I can say. > > > - "Server-side sessions" use cookies, which are global to the whole > browser (not per-tab), so if you want per-tab sessions you have to find > another approach than "server-side sessions" > - Per-tab sessions are not what most sites/apps do, so users will > likely not expect it (and most users login with a single account at a time > anyway, so it's mostly a non-issue). In other words, you want to do > something that people are not accustomed to. More clearly: don't do it > (unless you have very, very, very good reasons to) > - What you should do though (that you probably don't do nowadays, > which lead you to discover that behavior of your app) is to somehow check, > when your app loads, whether there's already a session or not (generally, > make a request to the server to get the user's information –username, > etc.– > and handle errors so you display the login form when unauthenticated). > Opening your app in multiple tabs (after authenticating in one tab) > shouldn't show you the login form. > > > > On Thursday, April 4, 2024 at 9:55:24 AM UTC+2 [email protected] > wrote: > > thanks @Thoms Broyer > can you elaborate more that can help me and clear what you wants to say > > On Wednesday, April 3, 2024 at 6:02:06 PM UTC+5:30 Thomas Broyer wrote: > > On Wednesday, April 3, 2024 at 1:16:58 PM UTC+2 [email protected] > wrote: > > Hello everyone, > In my flask application there is some issue related to login system and > issue as below 1)in flask app there are multiple users(roles) like > admin ,indentor.....etc. and the problem is that if any user login on same > browser where already any user logged in then previous user automatically > logout and recent user logging successfully > 2)if browser are different and users also different means only one user > login through one browser then there is no problem it works properly > 3)if browser is same and user also same then same name user login > successfully but previous same user session id change > 4)in any browser with same web page who running on local server all > tabs session id same inside the cookies it means on same browser all tabs > session id same for same web application > > i current situation i face the issue related to session management ,and > issue is that only one user login at same time with same browser > > > This is just how the web works. > > If you don't want this, then you can't use cookies to maintain your > session (e.g. generate some access token on the server that you send back > to the client and have it send it in a header with each request to the > server; the client could possibly save it in sessionStorage to store the > token so it survives a page refresh while segregating it to the current tab) > But note that I believe most users expect that middle-clicking a link (or > right-click → open in new tab) will preserve their session, and because > every web app out there shares the session across all tabs they won't even > try to login with a different user in a different tab (they'll expect that > their session is "detected" and reused, without seeing a login screen) > > Also, BTW, this is not GWT-related (in that, it applies whether you use > GWT or not). > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/07f051f2-ccb8-474e-a793-0463999660d4n%40googlegroups.com.
