This soft copy for use by IBM employees only.
3.2 Terminology
Kerberos clients (user) and services are uniquely identified by a principal
identifier, which consists of three components:
•
A principal name
•
An instance name
•
A realm name
3.2.1 Principal
Kerberos defines a name space of authenticated users and services. Each
different client and service has a unique
principal name. An RS/6000 SP user
who wishes to use any Kerberos-authenticated service must be registered to
Kerberos (by using
kadmin
or
kdb_edit
commands). By virtue of this registration,
the user then becomes a Kerberos user (also known as a principal). A private
DES key is created for the user and stored in the Kerberos database.
Note that the Kerberos name space is unrelated to the AIX name space, so that
an individual may be known by one name to Kerberos and by another name to
AIX. However, it is more convenient to assign the same name in each space.
It is possible to have multiple AIX users all using the same Kerberos user to
gain access to authenticated services. For example, you can do the following:
1. Define two non-root AIX users, Fred and Joe, on the Control Workstation
(make sure that the users are exist on the nodes, as well).
2. Use the command /usr/kerberos/bin/kadmin to add a Kerberos user called
kerb.
3. Create a new file, .klogin, in the home directory of the two new AIX users.
This file should contain a line similar to kerb@SP21CW0.
4. Log on as either user Fred or Joe and execute
kinit kerb
. The user can
now run any of the Kerberos-authenticated commands.
A principal can also refer to a Kerberos-protected service. In this way server
programs can be authenticated. For example, the hardmon service principal is
used by the hardmon and splogd server daemons.
3.2.2 Instance
The
instance name is a label that allows the same client or service to exist in
several different forms that each require distinct authentication. In the case of
services, an instance may specify the host that provides the service. For client
principals, the instance can be useful when one wishes to have different
identifiers for different privileges. The usual case is that users operate using a
name with a null instance.
For example, the client or user principal “root.admin” represents an instance
(admin) used for administrative tasks. The service principal “hardmon.sp21cw0”
represents an instance (sp21cw0) indicating the node providing the service.
72
SP PD Guide
Содержание RS/6000 SP
Страница 2: ......
Страница 14: ...This soft copy for use by IBM employees only xii SP PD Guide...
Страница 16: ...This soft copy for use by IBM employees only xiv SP PD Guide...
Страница 106: ...This soft copy for use by IBM employees only 86 SP PD Guide...
Страница 178: ...This soft copy for use by IBM employees only 158 SP PD Guide...
Страница 214: ...This soft copy for use by IBM employees only 194 SP PD Guide...
Страница 248: ...This soft copy for use by IBM employees only 228 SP PD Guide...
Страница 250: ...This soft copy for use by IBM employees only Figure 102 setup_authent Script Flow Chart 2 7 230 SP PD Guide...
Страница 252: ...This soft copy for use by IBM employees only Figure 104 setup_authent Script Flow Chart 4 7 232 SP PD Guide...
Страница 254: ...This soft copy for use by IBM employees only Figure 106 setup_authent Script Flow Chart 6 7 234 SP PD Guide...
Страница 258: ...This soft copy for use by IBM employees only Figure 110 install_cw Script Flow Chart 3 3 238 SP PD Guide...
Страница 260: ...This soft copy for use by IBM employees only Figure 112 setup_server Script Flow Chart 2 23 240 SP PD Guide...
Страница 262: ...This soft copy for use by IBM employees only Figure 114 setup_server Script Flow Chart 4 23 242 SP PD Guide...
Страница 264: ...This soft copy for use by IBM employees only Figure 116 setup_server Script Flow Chart 6 23 244 SP PD Guide...
Страница 266: ...This soft copy for use by IBM employees only Figure 118 setup_server Script Flow Chart 8 23 246 SP PD Guide...
Страница 268: ...This soft copy for use by IBM employees only Figure 120 setup_server Script Flow Chart 10 23 248 SP PD Guide...
Страница 270: ...This soft copy for use by IBM employees only Figure 122 setup_server Script Flow Chart 12 23 250 SP PD Guide...
Страница 272: ...This soft copy for use by IBM employees only Figure 124 setup_server Script Flow Chart 14 23 252 SP PD Guide...
Страница 274: ...This soft copy for use by IBM employees only Figure 126 setup_server Script Flow Chart 16 23 254 SP PD Guide...
Страница 276: ...This soft copy for use by IBM employees only Figure 128 setup_server Script Flow Chart 18 23 256 SP PD Guide...
Страница 278: ...This soft copy for use by IBM employees only Figure 130 setup_server Script Flow Chart 20 23 258 SP PD Guide...
Страница 280: ...This soft copy for use by IBM employees only Figure 132 setup_server Script Flow Chart 22 23 260 SP PD Guide...
Страница 284: ...This soft copy for use by IBM employees only Figure 136 rc switch Script Flow Chart 3 8 264 SP PD Guide...
Страница 286: ...This soft copy for use by IBM employees only Figure 138 rc switch Script Flow Chart 5 8 266 SP PD Guide...
Страница 288: ...This soft copy for use by IBM employees only Figure 140 rc switch Script Flow Chart 7 8 268 SP PD Guide...
Страница 290: ...This soft copy for use by IBM employees only 270 SP PD Guide...
Страница 292: ...This soft copy for use by IBM employees only 272 SP PD Guide...
Страница 300: ...This soft copy for use by IBM employees only 280 SP PD Guide...
Страница 304: ...This soft copy for use by IBM employees only 284 SP PD Guide...
Страница 308: ...This soft copy for use by IBM employees only 288 SP PD Guide...
Страница 310: ...This soft copy for use by IBM employees only 290 SP PD Guide...
Страница 316: ...IBML This soft copy for use by IBM employees only Printed in U S A SG24 4778 00...