Provided by: freeipa-client_2.1.4-0ubuntu1_i386
default.conf - IPA configuration file
/etc/ipa/default.conf, ~/.ipa/default.conf, /etc/ipa/server.conf,
The default.conf configuration file is used to set system-wide defaults
to be applied when running IPA clients and servers.
Users may create an optional configuration file in ~/.ipa/default.conf
which will be merged into the system-wide defaults file.
The following files are read, in order:
The IPA server does not read ~/.ipa/default.conf.
The first setting wins.
The configuration options are not case sensitive. The values may be
case sensitive, depending on the option.
Blank lines are ignored. Lines beginning with # are comments and are
Valid lines consist of an option name, an equals sign and a value.
Spaces surrounding equals sign are ignored. An option terminates at the
end of a line.
Values should not be quoted, the quotes will not be stripped.
# Wrong - don't include quotes
verbose = "9"
# Right - Properly formatted options
verbose = 9
Options must appear in the section named [global]. There are no other
sections defined or used currently.
Options may be defined that are not used by IPA. Be careful of
misspellings, they will not be rejected.
The following options are relevant for the server:
Specifies the base DN to use when performing LDAP operations.
The base must be in DN format (dc=example,dc=com).
Specifies the secure CA agent port. The default is 9443.
Specifies the secure CA end user port. The default is 9444.
Specifies the insecure CA end user port. The default is 9180.
Specifies the hostname of the dogtag CA server. The default is
the hostname of the IPA server.
Specifies the context that IPA is being executed in. IPA may
operate differently depending on the context. The current
defined contexts are cli and server. Additionally this value is
used to load /etc/ipa/context.conf to provide context-specific
configuration. For example, if you want to always perform client
requests in verbose mode but do not want to have verbose enabled
on the server, add the verbose option to /etc/ipa/cli.conf.
If True then logging will be much more verbose. Default is
The domain of the IPA server e.g. example.com.
Specifies whether the CA is acting as an RA agent, such as when
dogtag is being used as the Certificate Authority. This setting
only applies to the IPA server configuration.
Specifies whether an IPA client should attempt to fall back and
try other services if the first connection fails.
Specifies the hostname of the IPA server. This value is used to
construct URL values on the client and server.
Specifies whether requests should be forwarded to an IPA server
or handled locally. This is used internally by IPA in a similar
way as context. The same IPA framework is used by the ipa
command-line tool and the server. This setting tells the
framework whether it should execute the command as if on the
server or forward it via XML-RPC to a remote server.
This is used in development and is generally a detected value.
It means that the code is being executed within a source tree.
Specifies whether values should be prompted for or not. The
default is True.
Specifies the URI of the IPA LDAP server to connect to. The URI
scheme may be one of ldap or ldapi. The default is to use ldapi,
Specifies the mode the server is running in. The currently
support values are production and development. When running in
production mode some self-tests are skipped to improve
Specifies the mount point that the development server will
register. The default is /ipa/
Specifies that all options should be prompted for in the IPA
client, even optional values. Default is False.
Specifies the name of the CA back end to use. The current
options are selfsign and dogtag. This is a server-side setting.
Changing this value is not recommended as the CA back end is
only set up during initial installation.
Specifies the Kerberos realm.
If the IPA server fails to start and this value is True the
server will attempt to generate a python traceback to make
identifying the underlying problem easier.
Used internally in the IPA source package to verify that the API
has not changed. This is used to prevent regressions. If it is
true then some errors are ignored so enough of the IPA framework
can be loaded to verify all of the API, even if optional
components are not installed. The default is False.
Generates more output. The default is 0 which generates no
additional output. On the client a setting of 1 will provide
more information on the command and show the servers the client
contacts. A setting of 2 or higher will display the XML-RPC
request. This value has no effect on the server.
Specifies the URI of the XML-RPC server for a client. This is
used by IPA and some external tools as well, such as
ipa-getcert. e.g. https://ipa.example.com/ipa/xml
The following define the containers for the IPA server. Containers
define where in the DIT that objects can be found. The full location is
the value of container + basedn.
container_virtual: cn=virtual operations,cn=etc
system-wide IPA configuration file
user IPA configuration file
It is also possible to define context-specific configuration files. The
context is set when the IPA api is initialized. The two currently
defined contexts in IPA are cli and server. This is helpful, for
example, if you only want debug enabled on the server and not in the
client. If this is set to True in default.conf it will affect both the
ipa client tool and the IPA server. If it is only set in server.conf
then only the server will have debug set. These files will be loaded if
system-wide IPA client configuration file
system-wide IPA server configuration file