Documentation

 

 

Versions Compared

Old Version 100

changes.mady.by.user Laura Bridges

Saved on

compared with

New Version Current

changes.mady.by.user Laura Bridges

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NOTE: To use the proxy bypass feature with Windows, a proxy server and proxy bypass list must be configured. See Login for Windows Installer Configuration for information about configuring the proxy server and proxy bypass list.

Verify TLS 1.1 and TLS 1.2 enablement via GPO on Windows Server OS

Verify TLS 1.1 and TLS 1.2 are enabled via the Group Policy Object (GPO) to ensure a streamlined and secure login experience for users logging on a Remote Desktop.

The external article How to Enable TLS 1.1 and TLS 1.2 in Internet Explorer via Group Policy provides instructions on how to enable TLS 1.1 and TLS 1.2.

NOTE: TLS 1.1 and TLS 1.2 are not enabled by default on Windows 7 or Windows Server 2008 R2 Windows 7 or Windows Server 2008 R2 is required to use legacy_http_communication set to true in the config.json file.

End user

First-time usage requirements

...

Anchor
proxyserver
proxyserver
A. "proxy_server" and "proxy_bypass" configuration from config.json file. These settings are derived from entries made in the Web Admin Login for Endpoints Installer Configuration section. A "proxy_server" can be configured on the Windows OS, but if present as a root parameter in the config.json file, takes precedence over the OS setting. The format to configure the proxy is: "http://[user[:password]@]host[:port]\"

Anchor
legacy
legacy
Parameters surrounded by [ ] are optional. Both "user" and "password" are not supported on HTTP clients on Login for Windows version 19.06 and earlier, or on 19.09 or later that choose to use the legacy HTTP client by setting "legacy_http_communication”: true in the config.json file.

...