Chapter 12. Managing SASL
370
Realms are used by the server to associate the DN of the client in the following form, which looks like
an LDAP DN:
uid=
user_name
/[
server_instance
],cn=
realm
,cn=
mechanism
,cn=auth
NOTE
Kerberos systems treat the Kerberos realm as the default realm; other systems default to
the server.
Mike Connors in the
engineering
realm of the European division of
example.com
would have the
following association if he tried to access a different server, such as
cyclops
:
uid=mconnors/cn=Europe.example.com,
cn=engineering,cn=gssapi,cn=auth
Babara Jensen in the
accounting
realm of
US.example.com
would not have to specify a realm:
uid=bjensen,cn=accounting,cn=gssapi,cn=auth
If realms are supported by the mechanism and the default realm was not used,
realm
must be
specified; otherwise, it is omitted. Currently, only
GSS-API
supports the concept of realms.
12.5.2. Configuring the KDC Server
To use
GSS-API
, the user first obtains a ticket granting ticket (TGT). In many systems, this TGT is
issued when the user first logs into the operating system. There are usually command-line utilities
provided with the operating system —
kinit
,
klist
, and
kdestroy
— that can be used to acquire,
list, and destroy the TGT. The ticket and the ticket's lifetime are parameters in the Kerberos client and
server configuration.
Refer to the operating system documentation for information on installing and configuring a Kerberos
server (also called a
key distribution center
or KDC). Configuring a KDC for Directory Server is
described in
Section 12.5.3, “Example: Configuring an Example KDC Server”
.
NOTE
On Red Hat Enterprise Linux, the client-side Kerberos configuration is in the
/etc/
krb5.conf
. On Solaris, the client-side Kerberos configuration is in the
/etc/krb5/
krb5.conf
.
The HP server and client are separate packages with their own configuration. The server
stores config files in
/opt/krb5
. The client is classic MIT and uses
/etc/krb5.conf
.
Both the server and client must be configured to have a working Kerberos system.
In order to respond to Kerberos operations, the Directory Server requires access to its own
cryptographic key. This key is read by the Kerberos libraries that the server calls, through
GSS-API
,
and the details of how it is found are implementation-dependent. However, in current releases of the
supported Kerberos implementations, the mechanism is the same: the key is read from a file called a
Содержание DIRECTORY SERVER 8.0
Страница 18: ...xviii ...
Страница 29: ...Configuring the Directory Manager 11 6 Enter the new password and confirm it 7 Click Save ...
Страница 30: ...12 ...
Страница 112: ...94 ...
Страница 128: ...110 ...
Страница 190: ...Chapter 6 Managing Access Control 172 4 Click New to open the Access Control Editor ...
Страница 224: ...206 ...
Страница 324: ...306 ...
Страница 334: ...316 ...
Страница 358: ...340 ...
Страница 410: ...392 ...
Страница 420: ...402 ...
Страница 444: ...426 ...
Страница 454: ...436 ...
Страница 464: ...446 ...
Страница 484: ...466 ...
Страница 512: ...494 ...
Страница 522: ...504 ...