The information contained herein is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this
manual, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be held liable for errors contained herein or direct, indirect,
special, incidental or consequential damages in connection with the
furnishing, performance, or use of this material.
Warranty
A copy of the specific warranty terms applicable to your Hewlett-Packard
product and replacement parts can be obtained from your local Sales and
Service Office.
U.S. Government License
Proprietary computer software. Valid license from HP required for
possession, use, or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation,
and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor's standard commercial license.
Trademark Notices
UNIX is a registered trademark in the United States and other
countries, licensed exclusively through The Open Group.
MS-DOS, Microsoft and Windows are U.S. registered trademarks of
Microsoft Corporation.
Intel and Itanium are trademarks or registered trademarks of Intel
Corporation in the United States and other countries.
Authentication Process 28
Integrating a Kerberos Principal in to the LDAP Directory 34
Principals Tab 137
Principal Information Window 139
Change Password Window 144
Administrative Permissions Window 147
Password Tab 160
Change Password Window 163
Attributes Tab 168
LDAP Attributes Tab 176
Extract Service Key Table Window 180
Group Information Window 185
Administrative Permissions Window 189
Realms Tab 194
Realm Information Window 195
Logon Screen 199
Change Password Screen 200
Warning Message 200
Hierarchical Interrealm Configuration 283
Figures
15
Figures
16
About This Manual
This manual describes how to install, configure, administer, and
troubleshoot the Kerberos server on HP Integrity servers running the
HP-UX 11i v2 operating system.
Intended Audience
HP intends this manual for system managers or administrators
responsible for configuring and maintaining the Kerberos server running
HP-UX 11i v2.
This manual is based on the assumption that you meet the following
prerequisites:
•Understand distributed network concepts and client/server
computing
•UNIX operating system
•Understand the Kerberos basics
•Understand LDAP concepts
What Is in This Document
Kerberos Server Version 3.1 Administrator’s Guide is divided into the
following chapters, which contain information about installing,
configuring, and administering the Kerberos server:
•Chapter 1, “Overview,” on page 23: Provides an introduction to the
Kerberos server, outlines the new features in this release, and
highlights the key advantages of using the Kerberos server. It also
provides an introduction to LDAP, and provides details on
integrating Kerberos v3.1 with LDAP.
•Chapter 2, “Installing the Kerberos Server v3.1,” on page 35:
Describes how to install the Kerberos server on the HP-UX 11i v2
operating system.
•Chapter 3, “Migrating to a Newer Version of the Kerberos Server,” onpage 41: Explains the migration process from earlier versions of the
Kerberos server to v3.1.
17
•Chapter 4, “Interoperability with Windows 2000,” on page 51:
Contains information specific to establishing interoperability with
Windows 2000 Kerberos implementations.
•Chapter 5, “Configuring the Kerberos Server With C-Tree Backend,”on page 63: Provides information on the configuration files required
to configure the Kerberos server with C-tree as the backend
database.
•Chapter 6, “Configuring the Kerberos Server with LDAP,” on
page 73: Provides information on the configuration files required to
configure the Kerberos server with LDAP as the backend database.
•Chapter 7, “Configuring the Primary and Secondary Security
Server,” on page 95: Describes the procedure for configuring the
primary and secondary servers.
•Chapter 8, “Administering the Kerberos Server,” on page 109:
Describes the procedures for administering the Kerberos server
database. It also discusses principals and their attributes.
•Chapter 9, “Propagating the Kerberos Server,” on page 241: Describes
how to propagate the Kerberos server database from the primary
security server to the secondary security servers.
•Chapter 10, “Managing Multiple Realms,” on page 275: Explains
interrealm authentication and interoperability trust. In addition, it
gives you an overview of the additional server configuration
requirements in deployments that use multiple realms and
interrealm authentication.
18
•Chapter 11, “Troubleshooting,” on page 289: Describes how to
troubleshoot the common problems encountered while using the
Kerberos server. In addition, it contains a brief note on reporting
problems to your Hewlett-Packard Support Contact.
•Appendix A, “Configuration Worksheet,” on page 311: Provides a
worksheet that will help you configure the Kerberos server with
LDAP as the backend database.
•Appendix B, “Sample krb.conf File,” on page 317: Provides a sample
krb.conf file.
•Appendix C, “Sample krb.realms File,” on page 319: Provides a
sample krb.realms file.
•Glossary
•Index
Typographic Conventions
The following conventions are used throughout this manual:
Text Conventions
italicIdentifies book titles.
boldIdentifies options, command buttons, and menu
items.
Syntax Conventions
fixed widthIdentifies file names, system prompts, operating
system commands, and UNIX error and system
messages.
italic fixed widthIdentifies variables that you need to replace
according to your environment.
bold fixed
width
|Separates mutually exclusive parameters; only
[ ]Indicate that the enclosed parameters are
{ }Indicate that only one of the enclosed parameters
\Indicates that a command line, parameter, or code
#Precedes a UNIX command that must be
%Precedes a UNIX command that must be
Identifies the default in a series of parameters.
one of the parameters separated by the bar is
allowed.
optional.
are required.
continues on the following line.
performed as a root user.
performed as an ordinary user.
19
HP-UX Release Name and Release Identifier
Each HP-UX 11i release has an associated release name and release
identifier. The uname (1) command with the -r option returns the release
identifier. Table 1 lists the releases available for HP-UX 11i.
Table 1HP-UX 11i Releases
Release
Identifier
B.11.11HP-UX 11i v1PA-RISC
B.11.20HP-UX 11i v1.5Intel Itanium
B.11.22HP-UX 11i v1.6Intel Itanium
B.11.23HP-UX 11i v2Intel Itanium
Release Name
Publishing History
Table 2 provides, for a particular document, the manufacturing part
number, the respective operating systems, and the publication date.
Table 2Publishing History Details
Document
Manufacturing
Part Number
T1417-90001HP-UX 11.0 and 11i v1September 2001
T1417-90003HP-UX 11.0 and 11i v1June 2002
Operating System
Supported
Supported
Processor
Architecture
Publication Date
20
T1417-90007HP-UX 11i v2October 2003
T1417-90009HP-UX 11i v2April 2004
Related Software Products
Following are the products related to the Kerberos server:
•PAM Kerberos on HP-UX 11i v2, delivered as part of the HP-UX
Internet operating environment component.
•KRB5 Client Software on HP-UX 11i v2, delivered as part of the core
operating system.
•GSS-API on HP-UX 11i v2, delivered as part of the core operating
system.
Related Documentation
For more information on the Kerberos server, see the following manuals:
•Configuration Guide for Kerberos Client Products on HP-UX
(T1417-90006)
•PAM Kerberos Release Notes for HP-UX 11i v2 (J5849-90011)
•PAM Kerberos Release Notes for HP-UX 11i (J5849-90002)
•KRB5 Client Software Release Notes for HP-UX 11.0 (J5849-90005)
•GSS-API Release Notes for HP-UX 11.0 (J5849-90006)
•HP-UX Internet Services Administrator’s Guide (B2355-90774)
•Using HP-UX Internet Services (B2355-90827)
•
HP-UX 11i v2 Installation and Update Guide
operating system v11i v1 or later) (5187-2725)
(for HP-UX
Accessing the World Wide Web
See the following web sites for more information on the Kerberos server:
•Using a feedback form located at the following URL:
http://docs.hp.com/assistance/feedback.html
Please include the following information along with your comments:
•The full title of the manual and the part number. (The part number
appears on the title page of printed and PDF versions of a manual.)
•The section numbers and page numbers of the information on which
you are commenting.
22
•The version of HP-UX that you are using.
1Overview
This chapter provides an introduction to the Kerberos server v3.1,
available on the HP-UX 11i v2 operating system.
Chapter 123
Overview
This chapter discusses the following topics:
•“How the Kerberos Server Works” on page 26
•“Authentication Process” on page 27
•“DES Versus 3DES Key Type Settings” on page 31
•“Introduction to LDAP” on page 32
— “Integrating Kerberos Server v3.1 with LDAP” on page 33
Chapter 124
Overview
Introduction
Introduction
The term Kerberos was derived from the Greek mythology. Cerberus is
the latin variant of Kerberos, who guarded the entrance of Hades, the
Greek hell. The Kerberos security system, on the other hand, guards
electronic transmissions that are sent across a network.
Kerberos is a mature network authentication protocol based on the RFC
1510 (The Kerberos Network Authentication Service (V5)) specification of
the Internet Engineering Task Force (IETF). It is designed to provide
strong authentication for client or server applications using the shared
secret key cryptography.
The Kerberos server is based on a distributed client/server architecture.
It ensures secure communication in a networked environment by
leveraging individual trust relationships. It then brokers that trust
across enterprise wide, distributed client/server networks.
Chapter 125
Overview
How the Kerberos Server Works
How the Kerberos Server Works
The basic currency of Kerberos is the ticket, which the user presents to
use a specific service. Each service, be it a login service or an FTP
service, requires a different kind of ticket. The applications on the
Kerberos server keep track of all the various kinds of tickets.
When you first log on to Kerberos each day, you enter your Kerberos
password. In return, the Kerberos server gives you an initial ticket,
which you use to request additional tickets from the Kerberos server for
all the other services. For this reason, the initial ticket is also called the
ticket-granting ticket, or TGT.
Use the Kerberos protocol to secure the communication between the
client and server. Thus, client programs make authentication requests to
an authentication server, and server programs in turn service those
client requests. Based on your user credentials, the server program
grants or denies your request to access network applications and
services. The Kerberos server allows entities to authenticate themselves,
without having to transmit their passwords in clear text form over the
network.
For more information on the basics of Kerberos, see Installing,
Configuring and Administering the Kerberos Server on HP-UX 11i
(T1417-0001), available at
http://www.docs.hp.com/hpux/internet/index.html#Kerberos.
Chapter 126
Overview
Authentication Process
Authentication Process
The Kerberos server grants tickets to your user principal to access
secured network services. You must log on to the server by providing
your user name and password. When the server authenticates you, it
returns a set of initial credentials for you, including a TGT and a session
key.
The Kerberos server grants a service ticket for a specific service principal
that can be associated with one or more Kerberos-secured services on the
same system. A client application uses your service ticket to authenticate
you to a Kerberos-secured network service. The secured client
application automatically handles the transactions with the server and
the secured application server. Service tickets and associated session
keys are generally cached in your user credentials cache along with the
TGT of the user.
Chapter 127
Overview
Authentication Process
Figure 1-1 illustrates the actions of the components and the Kerberos
protocol in a secured environment.
Figure 1-1Authentication Process
The following is a description of how a client and server authenticate
each other using Kerberos:
Step 1. You can begin to use a Kerberos-secured application by entering your
principal name and password. Optionally, you can request specific ticket
flags and specify the key type to be used to construct the secret key. You
can also accept the default values configured for the client.
You can send the following information to the Authentication Service
(AS) to obtain credentials:
Chapter 128
Overview
Authentication Process
•Client-indicates the user name, also referred to as the principal
name
•Server-indicates the Application Server
•Time stamp
•Nonce
Step 2. If the AS decrypts the message successfully, it authenticates the
requesting user and issues a TGT. The TGT contains the user name, a
session key for your use, and name of the server to be used for any
subsequent communication. The reply message is encrypted using your
secret key.
Step 3. The client decrypts the message using your secret key. The TGT and the
session key from the message are stored in the client’s credential cache.
These credentials are used to obtain tickets for each network service the
principal wants to access.
The Kerberos protocol exchange has the following important features:
•The authentication scheme does not require that the password be
sent across the network, either in encrypted form or in clear text.
•The client (or any other user) cannot view or modify the contents of
the TGT.
Step 4. To obtain access to a secured network service such as rlogin, rsh, rcp,
ftp, or telnet, the requesting client application uses the previously
obtained TGT in a dialogue with the TGS to obtain a service ticket. The
protocol is the same as used while obtaining the TGT, except that the
messages contain the name of the server and a copy of the previously
obtained TGT.
Step 5. The TGS returns a new service ticket that the application client can use
to authenticate the service.
Step 6. The application client tries to authenticate to the service on the
application server using the service ticket obtained from the TGS.
The secure application validates the service ticket using the service key
of the server that is present in the key tab file. Using the session key, the
server decrypts the authenticator and verifies the identity of the user. It
Chapter 129
Overview
Authentication Process
Step 7. (Optional) At the client’s request, the application server can also return
also verifies that the user’s service ticket has not expired. If the user does
not have a valid service ticket, then the server will return an appropriate
error code to the client.
the timestamp sent by the client, encrypted in the session key. This
ensures a mutual authentication between the client and the server.
Chapter 130
Loading...
+ 297 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.