The settings on this page are somewhat self-explanatory, but we’ll take a moment and go through them here
- Restrict Admin by IP
This forces admin users to register an IP to their username. This is simply done with the guruin script, or you can add their IP from the backend. Multiple IP addresses CAN be used. This is just a bit of security - Require Login before order
This will require users to create an account and login in order to place an order through your site - How long to block for (hours)
This is only relative to the user login failure aspect of the module. Repeated login failures will result in automatic blocking for the number of hours you set here. - Block after how many failures
This allows you to protect your client’s accounts by blocking the attacking IP address. Set this to a higher number to prevent it triggering, but this is not advised - Throttle traffic
Do you want to throttle your traffic? This option is for you. This will allow you to limit traffic to x requests per y minutes - Throttle limit
How many requests for the above option? - Throttle Timeframe
How long should those requests last? - Log throttle clears?
This will add a log entry when your cron job clears the throttles - Send login notification mails to customers
When customers login, they can be notified. this adds an additional level of security - Allow ‘stealth’ admin logins
If you use the ‘login as client/customer’ option, keep this option on. Otherwise, your clients will be given your IP address, location, hostname, etc, when you login to their account. - Automatically sign new customers up for login notifications
This will prevent clients from having to register for login notifications on their own. You may need to disclose that you are doing this, depending on the laws in your region. - Clear database on deactivate
Wipes out everything when you deactivate / uninstall. Everything. All client login history, traffic history, everything.