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

3. Modify the properties on the Local Realm Attributes screen according to the information given
in Table 14.
4. To submit changes to the realm entry to the Server Manager, click Modify.
To return to the Realms screen without making any changes to your server configuration, click
Cancel.
NOTE: indicates that the configuration file cannot be modified using the Server Manager.
Edit the file manually using a command line editor.
Special Entries
There are a few special entries that you can use while configuring realms. Table 15 shows the
various special entries you can use.
Table 15 Special Entries
When to UseSpecial Entries
When specifying the primary realm for an entry, you can use a wild card syntax
such as *.realm. This syntax provides a shorthand for associating several
Wildcard Entries
related realms with a single authentication type. For example, a company may
have several branches, eastern.company.com, western.company.com, and
central.company.com. The wild card entry for that company would define
*.company.com as the realm. This notation would include all three realms. HP
recommends that any such wild card entry be listed after more specific entries.
This order allows the preceding, specific entries to override the wild card entry.
The DEFAULT realm acts as a matching realm entry for all realms. By default,
the DEFAULT realm is configured to authenticate against the default set of users.
DEFAULT Realm
Disable the DEFAULT realm by choosing the No Store - Deny All Users option
in the User Profile Storage drop-down list.
The Null realm authenticates users that do not identify their realm when
requesting access (for example, the AAA server receives an access request
NULL Realm
from user, instead of [e-mail]). By default, the NULL realm is
disabled with the No Store: Deny All Users setting.
Deleting a Realm
Complete the following steps to delete a realm:
Special Entries 75