Silicon Graphics Gauntlet, Administrator'S Manual, Page: 206 / 306

180
Chapter 18: Managing User Authentication
strongly authenticate themselves to login, using login-sh(1M), which supports any of the
authentication mechanisms aforementioned.
Configuring Authentication Management System Rules
If you are using the Gauntlet Firewall default configuration, you do not need to modify
the configuration rules for the user authentication management system. If you have
chosen a different port or a different location for your database, you must modify
/usr/gauntlet/config/template.netperm-table to reflect your configuration. See Appendix B
for more information on authentication manager options, netperm-table options, and
order of precedence.
Verifying Your Installation
Verify your installation by accessing the firewall from a host on the outside network.
To verify an installation using TELNET:
1. On a host on the outside network, TELNET to the firewall.
2. At the TELNET proxy user name prompt, enter a user name you have created.
3. At the TELNET proxy password prompt, enter the appropriate password or
response for the user you have created.
4. When you see the “Login Accepted” banner, you have verified your installation.
You are now ready to begin creating groups, adding users and assigning them to
groups. These tasks are described in the sections on managing groups and users in
this chapter.
Managing Groups
As with IRIX systems, the Gauntlet user authentication management system makes use
of groups. Groups allow you to permit or deny services based on groups, rather than
individual user names. For example, you can configure the TELNET proxy to require
authentication for everyone in the group “sales”. See “Extended Permissions” in the
authserv(1M) reference page for details.