You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If only 5 seconds are remaining on the google auth timer, by the time the password we type in reaches point of authentication, it has expired. These cases lead to failure of auth. In case only 5 seconds or lesser are remaining, we should wait until we get the new password, then connect to VPN.
Also, we can keep the last seconds remaining configurable. Because in times of bad internet connections, I have seen that this thing matters a lot.
The text was updated successfully, but these errors were encountered:
This extra check is not needed, in case of failure, the management console will receive a request for re-authentication, and then will go into the normal flow of the app.
@olttwa Thanks for pointing this out. Yeah, the timing mismatch between password generation and server authentication is a problem.
These won't be an issue once moor interfaces directly with openvpn using its management interface. Timing should not be problem in this case as there is no step where the user has to intervene, unlike the current version.
If only 5 seconds are remaining on the google auth timer, by the time the password we type in reaches point of authentication, it has expired. These cases lead to failure of auth. In case only 5 seconds or lesser are remaining, we should wait until we get the new password, then connect to VPN.
The text was updated successfully, but these errors were encountered: