When a user signs into CONNECTION Clent, it retrieves and stores a login token valid for seven days, enabling CONNECTION Client to automatically sign in again without prompting the user. When the expiration for the login token falls within 24 hours, CONNECTION Client will renew the login token for another seven days if running. However, the new expiration date will be seven days from the renewal date, not the original expiration date. Consequently, every token renewal will potentially be one day in the week early than the previous one which will eventually hit a weekend. If CONNECTION Client is not running on the weekend (i.e. the machine is turned off), the login token will fail to renew and will expire, prompting the user to sign in again on Monday. An enhancement has been filed to address this issue.
Best workaround: If computers will not be used over the weekend, lock the screen, but leave users signed into Windows. CONNECTION Client will remain running in the background so it can renew the login token as needed.
Alternative workaround: Sign into CONNECTION Client on a Friday. Despite the drift, CONNECTION Client will successfully renew for four weeks before requiring a user to sign in again.
Deutsch