ENC Client Policy Group
The ENC Client policy group lets you view or edit the following policies for the ENC client service. You can modify policy parameter values by double-clicking a policy to display the Setting Properties dialog.
Specifies the IP address or fully qualified domain name (FQDN) of the ENC Gateway Server with which to register. Clients must make their existence known to the rest of the ENC infrastructure in order to be available for connections. To do this, they register with an ENC Gateway Server.
Default: empty, <locally managed>
Specifies the address of a HTTP proxy server that the ENC Client uses to connect to hosts outside of the local network.
Default: empty, <locally managed>
Specifies the address of the SOCKS proxy used by the ENC Client to connect to hosts outside of the local network.
Default: empty, <locally managed>
Defines the method used to send credentials to the HTTP proxy server for httpConnect and httpProxy connection types. This can be one of the following values:
No authentication.
Send plain text credentials. This only works if credentials are explicitly specified.
Note: This type is incompatible with the Authenticate with HTTP proxy as logged on user policy.
Credentials are sent using NT LAN Manager (NTLM). This option must be used when authenticating with the credentials of the currently logged on user.
Note: The Secure mode is currently not supported for httpProxy connections; only httpConnect (HTTP Proxy SSL Tunnel) connections support Secure authentication.
The Secure method is tried first, then Basic.
Note: Since the Secure mode is currently not supported for HTTP proxy connections, only the Basic method is tried if this connection type is specified.
Default: Secure, <locally managed>
Defines the method used to send credentials to the SOCKS proxy server. This is used for the socks5Auth connection type, and can be one of the following values:
No authentication.
Send plain text credentials. This only works if credentials are explicitly specified.
Note: This type is incompatible with the Authenticate with SOCKS proxy as logged on user policy.
Credentials are sent using NT LAN Manager (NTLM). This option must be used when authenticating with the credentials of the currently logged on user.
The Secure method is tried first, then Basic.
Default: Both, <locally managed>
If True, the client authenticates with the HTTP proxy server using the specified user ID and password of the currently logged on user, if available. This option has no effect if the HTTP Proxy User Name and HTTP Proxy Password parameters are also set, as these parameters take precedence.
If no user is logged on to the machine, authentication as the logged on user is not attempted. This implies that if the only open communication path to the ENC Gateway Server is via an authenticating HTTP proxy for which credentials have not been explicitly configured, ENC connectivity will only be available when a user with appropriate access is logged on.
Note: When authenticating as the logged on user, only Secure authentication mode will be used.
Default: True, <locally managed>
If True, the client authenticates with the SOCKS proxy server using the specified user ID and password of the currently logged on user, if available. This option has no effect if the Socks Proxy User Name and Socks Proxy Server Password parameters are also set, as these parameters take precedence.
If no user is logged on to the machine, authentication as the logged on user is not attempted. This implies that if the only open communication path to the ENC Gateway Server is via an authenticating SOCKS proxy for which credentials have not been explicitly configured, ENC connectivity will only be available when a user with appropriate access is logged on.
Note: When authenticating as the logged on user, only Secure authentication mode will be used.
Default: False, <locally managed>
If True, the client uses the Internet Explorer's settings to find the SOCKS proxy address.
If the address of a SOCKS proxy server has been explicitly configured, this setting is ignored.
Default: True, <locally managed>
Defines the order of connection types that will be tried when attempting to contact the ENC Gateway Server and ENC Gateway Router. This policy parameter is a string containing 0 (zero) or more space-separated tokens from the following list:
Direct socket connection to ENC Gateway Server/Router.
Socket connection via anonymous SOCKS4 proxy.
Socket connection via authenticating SOCKS5 proxy.
Socket connection via anonymous SOCKS5 proxy.
Socket connection via HTTP Proxy SSL Tunnel.
HTTP encapsulation direct to ENC Gateway Server/Router.
HTTP encapsulation via HTTP Proxy.
For example, if you know that a direct socket is not available, you would not pass the socket token in as an option in the connection order list. If unspecified (empty), the default is to try a socket connection, then http, implying the following order: Socket socks4Anon socks5Auth socks5Anon httpConnect http httpProxy
Note: You can specify a SOCKS proxy server, which if specified, would be used for SOCKS connections. You can also specify an HTTP proxy server, which if specified, will be used for HTTP connections. Either, both, or none can be specified, but only one SOCKS and one HTTP proxy can be specified. Client Automation does not support specifying more than one proxy of either type. If you do not configure the address of an appropriate proxy server, and auto-discovery options are disabled, then the listed connection types that require a configured proxy will not be attempted. Therefore, in the default configuration, SOCKS connections will never be attempted, despite the fact that three SOCKS connection methods are chosen in the implicit default value for ENC Client Proxy Connection Order.
Default: empty, <locally managed>
Specifies the HTTP port number of the ENC Gateway Server used by the ENC Client to connect to using HTTP. A value of 0 (zero) indicates that an HTTP connection is not to be used.
Default: 80, <locally managed>
Default: <locally managed>
If True, the ENC Client attempts to discover details about the Internet HTTP proxy using the settings for Internet Explorer or WPAD (web proxy auto discovery).
If an HTTP proxy server has been explicitly configured, this setting is ignored, and the discovery is not performed.
Default: True, <locally managed>
Specifies the password of the HTTP proxy user. Note that this parameter is encrypted and is not displayed in the Setting Properties dialog used for editing policies. The default value is blank, or empty, which is displayed in the Setting Properties dialog as <encrypted>.
Default: <encrypted>, <locally managed>
Specifies the port number of the HTTP proxy server to which the ENC Client must connect.
Default: 8080, <locally managed>
Specifies the user name if the HTTP proxy requires authentication.
Default: empty, <locally managed>
Default: <locally managed>
Default: <locally managed>
Default: <locally managed>
Specifies the port number of the SOCKS proxy server to which the ENC Client must connect.
Default: 1080, <locally managed>
Specifies the password of the SOCKS proxy user. Note that this parameter is encrypted and is not displayed in the Setting Properties dialog used for editing policies. The default value is blank, or empty, which is displayed in the Setting Properties dialog as <encrypted>.
Default: <encrypted>, <locally managed>
Specifies the SOCKS proxy user name.
Default: empty, <locally managed>
Specifies the TCP port number of the ENC Gateway Server used by the ENC Client to connect to using a direct socket.
Default: 443, <locally managed>
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|
