HP-UX AAA Server A.08.00.01 Administrator's Guide

Wildcard Support for IPv4 and IPv6
To allow access from any IP address or from any IP address of a particular subnet,
specify a wildcard pattern in the etc/opt/aaa/clients file. Wildcard IP addresses
are specified by using the high order components followed by the asterisk wildcard.
Following are some examples of valid IPv4 wildcard patterns:
*
192.*
192.0.*
192.0.2.*
Following are some examples of invalid IPv4 wildcard patterns:
*.0
192.0*
To allow access from any IPv6 address or from a group of IPv6 addresses, specify an
IPv6 wildcard pattern. The allowed IPv6 wildcard patterns are constructed by appending
an ‘*’ to a partial IPv6 address or by specifying a single ‘*’. Following are some examples
of valid IPv6 wildcard patterns:
*
fedc:ba98:7654:3210:fe*
fedc:ba98:7654:3210*
The special IPv6 syntax of compressing zeroes using "::" is not allowed in IPv6 Wildcard
patterns. Following example is incorrect:
fedc::ba98:fe*
The users File
User profiles associate information, like check and reply items, with a user name. The
server configuration must include profiles for all the users that can access services
through the AAA server. Profiles can be stored in flat text files, or in an external
database. If a user profile is not included in the configuration, the server will reject the
user's access request.
The default users, realm, or prefix.users files may contain user profiles for
authentication. Each user entry in one of these files can be one or more lines of
information. You do not have to edit the default users file when mapping realms to
authentication types in the authfile, since the user information for each defined
realm will be stored in a realm file or external database. Unless the default installation
of the configuration files has been changed, the users file can be found in the /etc/
opt/aaa directory.
518 Configuration Files