Limit simultaneous user login by IP, unique location, attempt
Permalink
Is there any method in C5 to limit the number of times a user can login or how many unique IP's that user can login from?
Specifically I'm looking for a method to keep users from sharing their username/password which accesses private/purchased content. Eg: If a user purchases a membership to the site he can only log in from 3 IP's/devices, then a limit is reached and no more logins from new IP's. If the user e-mails all his friends his username/password, they wont all be able to log in before that limit is reached.
Any current methods to enforce this kind of limit or any add-ons that might achieve it?
Thanks!
Specifically I'm looking for a method to keep users from sharing their username/password which accesses private/purchased content. Eg: If a user purchases a membership to the site he can only log in from 3 IP's/devices, then a limit is reached and no more logins from new IP's. If the user e-mails all his friends his username/password, they wont all be able to log in before that limit is reached.
Any current methods to enforce this kind of limit or any add-ons that might achieve it?
Thanks!
No existing solutions? Bummer. Guess I'll start hacking away at one on my own. Any/all guidance welcome.
Looks like you and I are in the same boat on this one. Were you able to figure anything out?
My first though would be to mod the login script by getting a list of logged-in-users, matching the logging-in userID with an ID from the list, and then either running the rest of the script or kicking them back to the login page with a message.
My first though would be to mod the login script by getting a list of logged-in-users, matching the logging-in userID with an ID from the list, and then either running the rest of the script or kicking them back to the login page with a message.
Due to time and budget constraints I didn't get a chance to follow through with this for that project. Hope to get back to this someday when I get the time.
I was interested in this too. But would there be a problem with…
- ISPs that provide dynamic IP addresses instead of static? Maybe that is a rarity these days.
-Public wi-fi or large organsiations, or even households that now have more than 1 user, and that only present 1 IP to the world.
- ISPs that provide dynamic IP addresses instead of static? Maybe that is a rarity these days.
-Public wi-fi or large organsiations, or even households that now have more than 1 user, and that only present 1 IP to the world.
I'm looking for a similar solution to my ongoing project. I was thinking of using evercookie, to set at the registration time, and then check for its availability at each login. Still trying to figure out if it would suffice/work at all. Any input is appreciated.
Hello,
I know this is an old message but I just released an add-on that helps prevent users from sharing their account with other.
It's called Simultaneous Login Killer and you can check it out herehttp://www.concrete5.org/marketplace/addons/simultaneous-login-kill...
I know this is an old message but I just released an add-on that helps prevent users from sharing their account with other.
It's called Simultaneous Login Killer and you can check it out herehttp://www.concrete5.org/marketplace/addons/simultaneous-login-kill...
