I don't support having clients save usernames and passwords since you'd then have a file on your machine with your account details saved on it, and that would make hacking way easier. Even if they couldn't read the file directly, all they'd need is the file itself.
Other than that, complete support. The client should remember all user preferences, there's no reason not to.
I don't support having clients save usernames and passwords since you'd then have a file on your machine with your account details saved on it, and that would make hacking way easier. Even if they couldn't read the file directly, all they'd need is the file itself.
Other than that, complete support. The client should remember all user preferences, there's no reason not to.
If that was the case, there is an IP-checking system which identifies whether or not your account has been logged in on that machine. If it hasn't, or the machine wasn't given the proper clearance, it would trigger a prompt asking for your authenticator code (2FA). That issue is already solved.
If that was the case, there is an IP-checking system which identifies whether or not your account has been logged in on that machine. If it hasn't, or the machine wasn't given the proper clearance, it would trigger a prompt asking for your authenticator code (2FA). That issue is already solved.
Not everyone uses 2FA, it's not a mandatory feature, thank god.