1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
.. _kadmind(8):
kadmind
=======
SYNOPSIS
--------
**kadmind**
[**-x** *db_args*]
[**-r** *realm*]
[**-m**]
[**-nofork**]
[**-proponly**]
[**-port** *port-number*]
[**-P** *pid_file*]
[**-p** *kdb5_util_path*]
[**-K** *kprop_path*]
[**-F** *dump_file*]
DESCRIPTION
-----------
kadmind starts the Kerberos administration server. kadmind typically
runs on the master Kerberos server, which stores the KDC database. If
the KDC database uses the LDAP module, the administration server and
the KDC server need not run on the same machine. kadmind accepts
remote requests from programs such as :ref:`kadmin(1)` and
:ref:`kpasswd(1)` to administer the information in these database.
kadmind requires a number of configuration files to be set up in order
for it to work:
:ref:`kdc.conf(5)`
The KDC configuration file contains configuration information for
the KDC and admin servers. kadmind uses settings in this file to
locate the Kerberos database, and is also affected by the
**acl_file**, **dict_file**, **kadmind_port**, and iprop-related
settings.
:ref:`kadm5.acl(5)`
kadmind's ACL (access control list) tells it which principals are
allowed to perform administration actions. The pathname to the
ACL file can be specified with the **acl_file** :ref:`kdc.conf(5)`
variable; by default, it is |kdcdir|\ ``/kadm5.acl``.
After the server begins running, it puts itself in the background and
disassociates itself from its controlling terminal.
kadmind can be configured for incremental database propagation.
Incremental propagation allows slave KDC servers to receive principal
and policy updates incrementally instead of receiving full dumps of
the database. This facility can be enabled in the :ref:`kdc.conf(5)`
file with the **iprop_enable** option. Incremental propagation
requires the principal ``kiprop/MASTER\@REALM`` (where MASTER is the
master KDC's canonical host name, and REALM the realm name) to be
registered in the database.
OPTIONS
-------
**-r** *realm*
specifies the realm that kadmind will serve; if it is not
specified, the default realm of the host is used.
**-m**
causes the master database password to be fetched from the
keyboard (before the server puts itself in the background, if not
invoked with the **-nofork** option) rather than from a file on
disk.
**-nofork**
causes the server to remain in the foreground and remain
associated to the terminal. In normal operation, you should allow
the server to place itself in the background.
**-proponly**
causes the server to only listen and respond to Kerberos slave
incremental propagation polling requests. This option can be used
to set up a hierarchical propagation topology where a slave KDC
provides incremental updates to other Kerberos slaves.
**-port** *port-number*
specifies the port on which the administration server listens for
connections. The default port is determined by the
**kadmind_port** configuration variable in :ref:`kdc.conf(5)`.
**-P** *pid_file*
specifies the file to which the PID of kadmind process should be
written after it starts up. This file can be used to identify
whether kadmind is still running and to allow init scripts to stop
the correct process.
**-p** *kdb5_util_path*
specifies the path to the kdb5_util command to use when dumping the
KDB in response to full resync requests when iprop is enabled.
**-K** *kprop_path*
specifies the path to the kprop command to use to send full dumps
to slaves in response to full resync requests.
**-F** *dump_file*
specifies the file path to be used for dumping the KDB in response
to full resync requests when iprop is enabled.
**-x** *db_args*
specifies database-specific arguments.
Options supported for LDAP database are:
**-x nconns=**\ *number_of_connections*
specifies the number of connections to be maintained per
LDAP server.
**-x host=**\ *ldapuri*
specifies the LDAP server to connect to by URI.
**-x binddn=**\ *binddn*
specifies the DN of the object used by the administration
server to bind to the LDAP server. This object should
have read and write privileges on the realm container, the
principal container, and the subtree that is referenced by
the realm.
**-x bindpwd=**\ *bind_password*
specifies the password for the above mentioned binddn.
Using this option may expose the password to other users
on the system via the process list; to avoid this, instead
stash the password using the **stashsrvpw** command of
:ref:`kdb5_ldap_util(8)`.
**-x debug=**\ *level*
sets the OpenLDAP client library debug level. *level* is
an integer to be interpreted by the library. Debugging
messages are printed to standard error, so this option
must be used with the **-nofork** option to be useful.
New in release 1.12.
SEE ALSO
--------
:ref:`kpasswd(1)`, :ref:`kadmin(1)`, :ref:`kdb5_util(8)`,
:ref:`kdb5_ldap_util(8)`, :ref:`kadm5.acl(5)`
|
