sfpipauth - blazing fast IP-authentication
On large sites you may sometimes encounter a slowing down when using common IP-authentication services (e.g. cc_ipauth & cc_iplogin_fe).
These performance-problems are caused by the way those Extensions check for matching IPs: By Regexp-Search over the whole fe_users table.
Usually, you don't have lots of Users that are able to login with their IP, but if you have ten thousands of fe_users on your site, this search lasts. Since the authentication service is (if set so, see FE_fetchUserIfNoSession) executed on every single page hit, this search can kill your DB-server and it may take very long for the FE to be displayed.
Now, enough bad news: We have a solution!
We've created an Extension called "sfpipauth" that is blazing fast, easy to use and provides some cool options. I want to briefly introduce it's advantages to you:
- the Extension has a separate table for the records, which is searched (thus it's fast...)
- you can assign the IPs to fe_users and/or fe_groups
- you can automatically log in a user with matching IP
- you can allow normal login on matching IP
- you can completely lock out a user with not matching IP
- you can configure the service to run only if the user starts a session (it's then not run on every page hit, but if the user tries to log in etc...)
Further details, screenshots and a userguide can be found in the documentation. Here, thanks to Patrick who managed the impossible task of getting a Documentation to be rendered nicely by the TER.
Please report Feature-Requests (e.g. BE-login) and Bugs on forge.
Edit: The Extension is also in sfp-Repository. Please include it there.
It's online
The Extension is published on forge and uploaded to the TER:
Forge: http://forge.typo3.org/projects/extension-sfpipauth
TER: http://typo3.org/extensions/repository/view/sfpipauth
If you have any questions, just stop by :D
Now, what lasts to say is: never ever use cc_ip* again, use sfpipauth.