| United States-English |
|
|
|
![]() |
Kerberos Server Version 3.12 Administrator's Guide: HP-UX 11i v3 > Chapter 7 Configuring the Primary
and Secondary Security ServerConfiguring the Primary Security Server |
|
The following sections describe the initial configuration tasks you need to perform to get your primary and secondary security server up and running. The primary security server requires the following basic configuration tasks:
If you choose not to create the principal database during installation, create it before configuring the security server. To create the principal database, execute the following command:
If you are using Kerberos server v2.0 or v3.0, and want to migrate the principal database to Kerberos server v3.12, see Chapter 3 “Migrating to a Newer Version of the Kerberos Server”. Use the HP Kerberos Administrator (kadminl_ui) instead of the command-line administrator (kadminl) to add the principal account. For more information on using the HP Kerberos Administrator and the command-line administrator, see “The kadmin and kadminl Utilities”. Though it is possible to use the kadmin option to create an administrative principal, you cannot use kadmin to assign administrative privileges. If you want to use the kadmin utilities to manage your administrative principals, use a text editor to add the required entries to the file.
For the first administrative principal, HP recommends that you assign all permissions, indicated by * in admin_acl_file. For more information, see “The admin_acl_file File”. You can add an administrative principal through the HP Kerberos Administrator GUI, or through the command-line interface. Following steps show you how to add an administrative principal using the HP Kerberos Administrator:
For more information on using the HP Kerberos Administrator, see “HP Kerberos Administrator”. Following steps show how to add an administrative principal through the command-line interface:
For more information on assigning administrative privileges to principals, see “Manual Administration Using kadmin”. To allow principal database propagation, the primary security server must have a host/<fqdn> principal and the service key for this principal must be extracted to the service key table file of the server. The host/<fqdn> principal is not automatically added to the principal database during security server software installation; you must manually add the host/<fqdn> principal using the kadminl_ui or kadminl command.
HP recommends that you create a host/<fqdn> principal and extract its service key using the kadminl command. To do this, type the following command at the prompt:
The host/<fqdn> is added to the principal database, along with a random key. The random key is added to the service key table. To verify that these operations are successful, use the ktutil-k command to list the contents of the key table file. The existence of a host/entry file indicates that the principal has been successfully added to the database with a random key.
You can use the krbsetup tool to start the following Kerberos daemons:
Alternatively, you can use the following command to start the Kerberos daemons kdcd and kadmind:
To start the kpropd daemon, use the following command:
To configure propagation, alter the Kerberos configuration files to define server network locations. For more information, see Chapter 9 “Propagating the Kerberos Server”. For each secondary security server installed on your network, edit the krb.conf file on the primary security server by adding an entry to define the role of this secondary security server in the realm. For more information on the configuration files, see “The krb.conf File”. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||