
488
| Reference
ClearPass Guest 3.9 | Deployment Guide
listen.type
= not set
Type of packets to listen for. Allowed values are “auth” for authentication packets,
and “acct” for accounting packets.
hostname_lookups
= off
Log the names of clients or just their IP addresses, for example, www.examle.com
(on) or 209.97.207.76 (off). The default is ‘off’ because it would be overall better for
the net if people had to knowingly turn this feature on, as enabling it means that each
client request will result in AT LEAST one lookup request to the name server. Enabling
hostname_lookups will also mean that your server may stop randomly for 30 seconds
from time to time, if the DNS requests take too long. Turning hostname lookups off
also means that the server won’t block for 30 seconds, if it sees an IP address which
has no name associated with it. Allowed values are
no
and
yes
.
log_stripped_names
= no
Log the full User-Name attribute, as it was found in the request. Allowed values are
no
and
yes
.
log_auth
= yes
Log authentication requests to the log file. Allowed values are
no
and
yes
.
log_auth_badpass
= no
Log incorrect passwords with the authentication requests. Allowed values are
no
and
yes
.
log_auth_goodpass
= no
Log correct passwords with the authentication requests. Allowed values are
no
and
yes
.
lower_user
= no
lower_pass
= no
Convert the username or password to lowercase “before” or “after” attempting to
authenticate. If set to “before”, the server will first modify the request and then try to
authenticate the user. If set to “after”, the server will first attempt to authenticate using
the values provided by the user. If that fails it will reprocess the request after
modifying it as you specify below. This is as close as ClearPass Guest can get to case
insensitivity. It is the admin’s job to ensure that the username on the auth db side is
also lowercase to make this work. Allowed values: before, after, no
nospace_user
= no
nospace_pass
= no
Some users like to enter spaces in their username or password incorrectly. To save
yourself the tech support call, you can eliminate those spaces here. Allowed values:
before, after, no (as for ‘lower_user’ above)
rfc2868_zero_tag
= no
Allow the insertion of RFC 2858 tags with a zero value. Normally, zero indicates an
unused tag, and in string attributes (for example, Tunnel-Private-Group-Id) a zero tag
would be omitted. However, some vendors require the tag to be present even if it is
zero. In this case, setting this to ‘yes’ will allow the insertion and use of a zero tag.
Default is ‘no’ (RFC 2868 compliant). Allowed values: no, yes
allow_authorize_only
= no
Specify this option to enable support for authorization-only RADIUS requests, which
have the Service-Type attribute set to the value “Authorize-Only” and do not contain a
User-Password attribute.
Default is ‘no’.
Allowed values: no, yes
Table 56
General Configuration Settings (Continued)
Value
Description
Содержание ClearPass Guest 3.9
Страница 1: ...ClearPass Guest 3 9 Deployment Guide ...
Страница 32: ...32 Management Overview ClearPass Guest 3 9 Deployment Guide ...
Страница 178: ...178 RADIUS Services ClearPass Guest 3 9 Deployment Guide ...
Страница 316: ...316 Guest Management ClearPass Guest 3 9 Deployment Guide ...
Страница 328: ...328 Report Management ClearPass Guest 3 9 Deployment Guide Figure 46 Components of the Report Editor Report Type ...
Страница 410: ...410 Administrator Tasks ClearPass Guest 3 9 Deployment Guide ...
Страница 414: ...414 Administrator Tasks ClearPass Guest 3 9 Deployment Guide ...
Страница 423: ...ClearPass Guest 3 9 Deployment Guide Hotspot Manager 423 ...
Страница 440: ...440 High Availability Services ClearPass Guest 3 9 Deployment Guide ...
Страница 518: ...518 Index ClearPass Guest 3 9 Deployment Guide ...