Closed (fixed)
Project:
Restrict Login or Role Access by IP Address
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
22 Mar 2008 at 22:45 UTC
Updated:
22 Jun 2011 at 19:37 UTC
Jump to comment: Most recent file
Comments
Comment #1
ymmatt commentedA good feature, shouldn't be too hard to implement
Comment #2
bentterp commentedWould be very useful to me as well, i.e. Admins and Superadmin only access through VPN :-D
Except, I'd want to run version 6.current....
Comment #3
ymmatt commentedComment #4
dmjossel commentedToo bad this is postponed-- seems to me to be an extremely useful feature, one I'm actually looking for.
Comment #5
panthar commentedHere we go, I did it! Role based ip restriction!!
It needs review, but it would be really cool if we could add this to the core.
If you currently have restrict by ip installed, FULLY uninstall it, as the database table will change. After re-installing see the readme.txt as you have to add 1 line to the settings.php to override the drupal session functions.
Hope this works out for everyone, and hope I can become a co-maintainer in the near future!
Thanks!
Comment #6
panthar commentedSorry, still new to this, did not realize this was posted originally as 5.x, this feature addition is for 6.x!
Comment #7
panthar commentedComment #8
msumme commentedI also think this feature would be incredibly useful. It would make it very easy to sell to a client, so that you could tell them their superadmin and special roles with privileges will be secure from password theft. If they try to log in from elsewhere, or an imposter does, they won't be able to use the site. This would keep the site much more secure if it's managed from a central network.
This would be an AWESOME feature, because it would still allow lesser roles to participate and get usernames on the site.
Comment #9
dmjossel commentedWould it be possible to restrict only the registration of a role within an IP block?
While currently this is good as an extra level of protection for admin access, it's not so good for other roles.
For instance, at an ISP, this would allow the automatic assignation of the "client" role to users within a certain IP range.
However, once registered, that user account should be a "client" even when they are accessing the site from another location.
Comment #10
dmjossel commentedAlso, use of the module modified for restricting role access produces this error:
Uninstalling/reinstalling and running update.php had no effect.
UPDATE: A second round of uninstalling and reinstalling did it. Not sure why.
Comment #11
panthar commentedThe primary reason for having to uninstall/reinstall is that there is a database modification. I am not certain why it would take uninstalling/reinstalling twice, but if it does the trick, then awesome.
The thought has crossed my mind to make a new project specifically for restricting ip by roles, since this maintainer has not responded to me for several months. What do you guys think?
Comment #12
ymmatt commentedIt's obvious that even though I've attempted to make time, I haven't been able to work on features. Would you like to be added as a contributor, or to take over maintenance?
Comment #13
panthar commentedI definitely want to be a contributor, and I can certainly help maintain, although would rather it be a co-maintenance thing between the two of us.
Thanks.
Comment #14
coltrane@#5 you'll want to provide a patch, as that's easier to test.
Comment #15
james.wilson commentedThis was added in 6.x-2.x and further modified/improved in 6.x-3.x.