Re: Concurrent Logins of same User ID's?
Hi Steve,
Thanks for testing. That's very helpful.
To clarify for others that means same user ID can log in as many times as they want to an application from many computers. This may not be a desirable operation when a user is paying for using your web application on a per concurrent user basis.
I'm not sure I follow you 100%. I only want to log off selected active session users based on a criteria, not all users. I obviously can set a flag when they log in, and clear it if they log out, but don't think I can determine if the security framework has logged them off for any other reason.
Without building a replacement security framework, I don't think this is doable unless Alpha gives us a function to return active session users, which shouldn't be difficult I suspect
And it probably would be good for Alpha to add some other functions to make it easier to get supplementary info about the user that they can get via the browser. E.g. IP, browser type, OS type, referrer URL, and browser resolution.
Another piece of information that is real difficult to ascertain is the total time a person has spent on your application. There are some applications that might be time based (especially for trial usages) so that you'd want to log them off after a certain number of minutes logged in for that session, or total cumlative time for all sessions. So you'd want to be able to get the length of time from their login to when they they logged out or were logged out. Probably an event that is called when a user logs out or is logged out would allow you to capture the time spent on the system, and a separate ability to check for current time a user has been active on the system.
Hi Steve,
Thanks for testing. That's very helpful.
To clarify for others that means same user ID can log in as many times as they want to an application from many computers. This may not be a desirable operation when a user is paying for using your web application on a per concurrent user basis.
Originally posted by Steve Wood
View Post
Without building a replacement security framework, I don't think this is doable unless Alpha gives us a function to return active session users, which shouldn't be difficult I suspect
And it probably would be good for Alpha to add some other functions to make it easier to get supplementary info about the user that they can get via the browser. E.g. IP, browser type, OS type, referrer URL, and browser resolution.
Another piece of information that is real difficult to ascertain is the total time a person has spent on your application. There are some applications that might be time based (especially for trial usages) so that you'd want to log them off after a certain number of minutes logged in for that session, or total cumlative time for all sessions. So you'd want to be able to get the length of time from their login to when they they logged out or were logged out. Probably an event that is called when a user logs out or is logged out would allow you to capture the time spent on the system, and a separate ability to check for current time a user has been active on the system.
Comment