This is a complementary and server-side response. I am posting as an additional option.
Advantage of the method: it respects the user name autocomplete, and only protects the password.
Using some server side language, you can change the name
from the password field to a pseudo-random string, and use an Hidden field to store that string, thus:
<input type="text" name="usuario">
<input type="password" name="SYG2d7s6f1Sr874yYGJ4">
<input type="hidden" name="auxiliar" value="SYG2d7s6f1Sr874yYGJ4">
Thus, the password field (virtually) will never be the same, taking the effectiveness of what was previously saved under another name.
Then, in a language like PHP, just use it like this:
$auxiliar=$_POST['auxiliar']
$usuario=$_POST['usuario']
$senha=$_POST[$auxiliar]
Another complementary trick is to create two fields of the type password
, some browsers understand this as probable form
password reset, and do not save in this case (can hide one of them with CSS, for example).
Gustavo, what password? refers to password when logging into a website? Only in Chrome or other browsers?
– Sergio
The password to login. When my client logs in appears to him the option to save password, and after he enable it always when he accesses the system he remains logged in. I want to disable this in any Browser.
– Gustavo
I gave an answer with a complementary method, see if it helps as extra protection.
– Bacco