Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Kerberos Server Version 3.12 Administrator's Guide: HP-UX 11i v3 > Chapter 9 Propagating the Kerberos Server

Configuring Multirealm Enterprises

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

When you support multiple realms, additional configuration steps are required for both the security servers and clients. This section discusses the servers requirements.

Number of Realms per Database

A single primary security server supports more than one realm. If you have a centralized administration group that controls the security needs of your enterprise, you can support all the realms on one primary security server.

Alternatively, if you have distributed administration groups, you may need to support a single realm for a single primary security server. This arrangement has different configuration requirements.

If you are supporting only one realm per primary security server, you must configure the server normally, and create the required trust relationships, as described in “Configuring Direct Trust Relationships”.

You must perform additional configuration tasks if you are supporting more than one realm per primary security server.

primary security servers Supporting Multiple Realms

If you choose to support more than one realm in a database of a primary security server, you must decide if all the secondary security servers also support multiple realms. Alternatively, you can have different branches of secondary security servers: one branch for each realm supported in the principal database.

You can configure propagation to propagate only selected realms to a secondary security server. With this propagation configuration, you can maximize the benefits of creating multiple security boundaries in your enterprise. In the event that an authentication server in one branch is compromised, database information about other branches is still secure.

Multiple primary security servers Supporting a Single Realm

You must have one primary security server for each realm if you have distributed administrative groups in which each group maintains its own realm information.

You cannot propagate changes from one primary security server to another. You can only propagate changes from a primary security server to a secondary security server. Therefore, when you have multiple primary security servers supporting only a single database, you do need not to change your propagation configuration from a single-realm scheme.

Adding More Realms to a Multirealm Database

Before adding realms to a database, complete the following steps:

  • Install the primary security server and create the database.

  • Install each secondary security server and create their respective databases.

  • Create the first administrative principal, and assign permissions for all realms of this principal.

In the next section, HP assumes that you have not yet configured propagation before you start adding realms.

To add realms to the database, you can authenticate from a client using the administrative principal account and run the remote administrator, kadmin_ui, or you can log on to the primary security server and run the local administrator, kadminl_ui.

When you are running administrator, add additional realms using the Realms tab. For more information on creating realms, see “Realms Tab”.

After adding all the realms to the database, you must decide on the secondary security servers that support multiple realms.

Database Propagation for Multirealm Databases

If you plan to support more than one realm in a single principal database on a primary security server and to propagate only selected realms to certain secondary security servers, you must perform additional steps when you configure propagation.

HP assumes that you are familiar with the propagation setup procedure as specified in “Propagation Hierarchy”.

You can follow the standard propagation configuration if you have configured a multirealm environment that has only one realm for every primary security server. In other words, if you have multiple primary security servers or if you want to propagate all realms from the primary security server to each secondary security server, complete the following steps:

  1. Edit the Kerberos configuration file, krb.conf, on the primary security server to contain one entry for each secondary security server that supports a given realm. If a secondary security server supports more than one realm, you must add multiple entries to the file for that server, one for each supported realm. Ensure that you also add one primary security server entry for each realm that the primary security server supports. After you add all the entries, save and close the file.

  2. Run the mkpropcf utility to create an initial version of the kpropd.ini file or registry key.

  3. You must edit the file/registry key to contain the correct information for your propagation design. For instance, if you want to propagate only certain realms to a selected secondary security server, you must edit the entry/key for the parent of that server to indicate only the required realms. For more information on indicating only select realms to propagate, type man 4 kpropd.ini at the HP-UX prompt.

  4. After configuring the kpropd.ini file of the primary security server, follow the propagation configuration steps.

    On each Kerberos security server, you need to extract only the host/key for the default realm of the primary security server, and not for each realm supported by the secondary security server. Even if the secondary security server does not support the default realm of the primary security server, you must still create a host/principal for the secondary security server and extract the key to the key table file of the secondary security server.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2007 Hewlett-Packard Development Company, L.P.