SPARK FOR MAC KEEPS ASKING FOR PASSWORD PASSWORD
Most users are not really aware what's going on at this point, so they remove the stored password and replace it with the static secret plus OTP (48 characters in total). If a user mistypes the password or mishandles the token, authentication will fail and they're returned to the "Login/Password" dialog. Unfortunately this causes another problem: So if a user connects, they now just get a one line dialog with a useful title (which renders fine on Mac, but has some line-height layout issues on Windows). So to fix this problem, we started storing the username and a short irrelevant password in the keychain, and request the actual password plus OTP string through a static challenge (configuring "static-challenge" in the Advanced tab). Also, this way the static secret would always end up in the keychain, reducing its usefulness. This is clearly suboptimal, as the extra failed attempt takes time and increases the chance of locking oneself out of the system after too many failed attempts. As a result, they would always produce one failed login attempt on connect, and then enter the correct password. Originally the user would enter their username and this combination of a well known secret and a password into the "Login/Password" dialog.Īs users try to save time, they started using the "remember credentials" checkbox, so they wouldn't have to enter their username on every login. We use a combination of a known static secret and a generated one-time password, which are combined 48 characters in length. To give you some background, this is how we got into this situation:
In this case the connection attempt to Viscosity times out and the user has no clue what to do.
TLS Error: Auth Username/Password was not provided by peer When password and static-challenge combined are too long (we faced this with a 48 character password and a 48 character static challenge, so 96 characters in total), Viscosity doesn't seem to send credentials at all and we get this server side error message:
0 kommentar(er)
