you should track somewhere that userA from machineA is in there and check
when userA logs in from machineB.
There's a pretty outstanding issue in your design, though how do you
recognize machineA from machineB ?
On Tuesday, October 14, 2014 8:01:19 PM UTC+2, Mandar Vaze wrote:
This is
You could check things like IP address and user agent, but these are
imperfect identifiers (generating false positives and false negatives). You
should also decide if you really need this level of security, as users may
legitimately want to be logged in from multiple places (e.g., from laptop
I agree that this could be annoying, but the request came from customer
:) - We are trying to negotiate this down, but in the mean time I would
like to be prepared, if this becomes hard requirement.
(As I explained - this is also tied to security issue - I'll write to you
separately)
Anyway -
Thanks for the pointers.
If I decided to add this check - *where in the code/flow should this check
go* ?
-Mandar
On Wednesday, October 15, 2014 1:01:42 AM UTC+5:30, Niphlod wrote:
you should track somewhere that userA from machineA is in there and check
when userA logs in from machineB.
On Tuesday, October 14, 2014 9:01:19 PM UTC+3, Mandar Vaze wrote:
Is it possible to either :
not allow login from MachineB (show message that You are currently logged
in from MachineA - continue to access the application from MachineA, or
logout from MachineA... or some such message.)
OR
5 matches
Mail list logo
