Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I didn't realize. I was about to commit the changes that we where talking about after I figured out the update_N hook code and adding the description field back in. ip_login seems to be based off of the profile module. I'll have to try it out. Thank you for letting me know.
Just wanted to add my 2cents that ip_login doesn't appear to do a few things I need which maybe ip_authenticator can?
1. Handle complex ranges like 100.100.1-100.1-100 (or atleast the value is just stored as text and there's no documentation about what pattern matching the module is doing on that value). Obviously, I could split that single range up into hundreds of smaller ranges but that only makes my second point more critical...
2. Handle multiple ranges for the same user
3. Allow a user to elect to log in using username/password to gain additional privileges even though they've been ip authenticated already
It sounds like ip_authenticator might be able to do these things. If so, I think there's still a need for this module despite the availability of ip_login.
I tried downloading the official version 6 release of ip_authenticator but it doesn't seem to match up to what you've written recently on the project page. Is an updated version coming?
Handle complex ranges like 100.100.1-100.1-100 (or atleast the value is just stored as text and there's no documentation about what pattern matching the module is doing on that value).
I didn't undertand your example range.
Handle multiple ranges for the same user
That is possible with ip_authenticator.
Allow a user to elect to log in using username/password to gain additional privileges even though they've been ip authenticated already
This is possible as well.
I tried downloading the official version 6 release of ip_authenticator but it doesn't seem to match up to what you've written recently on the project page. Is an updated version coming?
There are no plans on my side to port the things I'v added to drupal 6 as I don't know the differences between 5 and 6 and I don't use drupal 6 yet. But if you're planning to do the port yourself I'll be happy to answer your questions which might arise during coding.
Comments
Comment #1
jonfrancisskydiver commentedI didn't realize. I was about to commit the changes that we where talking about after I figured out the update_N hook code and adding the description field back in. ip_login seems to be based off of the profile module. I'll have to try it out. Thank you for letting me know.
Comment #2
melmore commentedJust wanted to add my 2cents that ip_login doesn't appear to do a few things I need which maybe ip_authenticator can?
1. Handle complex ranges like 100.100.1-100.1-100 (or atleast the value is just stored as text and there's no documentation about what pattern matching the module is doing on that value). Obviously, I could split that single range up into hundreds of smaller ranges but that only makes my second point more critical...
2. Handle multiple ranges for the same user
3. Allow a user to elect to log in using username/password to gain additional privileges even though they've been ip authenticated already
It sounds like ip_authenticator might be able to do these things. If so, I think there's still a need for this module despite the availability of ip_login.
I tried downloading the official version 6 release of ip_authenticator but it doesn't seem to match up to what you've written recently on the project page. Is an updated version coming?
Thanks!
Comment #3
hajo commentedHi,
I didn't undertand your example range.
That is possible with ip_authenticator.
This is possible as well.
There are no plans on my side to port the things I'v added to drupal 6 as I don't know the differences between 5 and 6 and I don't use drupal 6 yet. But if you're planning to do the port yourself I'll be happy to answer your questions which might arise during coding.
Regards,
Hajo