[rankogrba]

Yes, an option which forces the user to use at least a password that is not identical to his username. That would be already much “stronger” than to have identical username and password.

[rankogrba]

Just to be sure you understand what I asked. Of course a user is supposed to be able to enter a username and a password in the process of registration. The question was about restricting the user to have identical username and password. Example: the user enters the usernanme ADMIN and then if he enters the password also ADMIN, the system displays a note saying that the username and the password can not be identical.

[rankogrba]

Update:

Tried with another test account and this time when trying to login from 4th IP address, got a message that the number of login attempts is more than today’s limit (something like that).

My questions:

1. I thought that this 4th IP address and the account email address will end up in the blacklist but it didn’t. Is it not the way it should work?

2. The first account that wasn’t blocking after 3 different IP addresses was one with a “disposable” email address (@sharklasers.com). Could that be the reason why the blocking did not work?

[rankogrba]

Of course. Yes, the same wpemember account username and password.

[rankogrba]

No, this is not the case.

Testing has been done like this:

1. a friend login in from work computer, checked the IP address (last login).

2. me login in from home computer, last login IP address changed (checked).

3. me login in from my mobile phone (on celular network), last login IP address changed (checked).

4. me login in from my server on azure, last login IP address changed (checked).

5. another friend login in from computer, last login IP address changed (checked).

[Author]

Posts