We have a load balanced arrangement with multiple web site servers that also firewalls the backend servers from httpd requests. The only IP address that the web servers "see" is that of the balancer's gateway address, so no user IP addresses are available to our web server software. Will amember's login system still work properly without access to the user IP addresses?
Chimm, I don't think it is necessary that aMember can track the user's actual IP to provide its standard functions. You would not be able to take advantage of aMember's anti password sharing feature which can lock out a user if they logged in from X number or IPs in X number of minutes.
Gswaim: thanks for the info, it looked like that might be the case but I wanted to make sure from someone that's been using it.
Will it actually effect password sharing. You will not be getting any IP data to amember right? If thats the case its the same situation as running multiple logins from one IP which I do in testing all the time. My understanding is password sharing protection protects against multiple logins to the one account from different IP's at the one time. This is the opposite. Multiple logins on different accounts from the same IP (none) Bottom line is whatever the case is it will most likely work...MAYBE you might need to disable password sharing option