freeipa/install
Jan Cholasta d5fc0ddd87 install: do not assume /etc/krb5.conf.d exists
Add `includedir /etc/krb5.conf.d` to /etc/krb5.conf only if
/etc/krb5.conf.d exists.

Do not rely on /etc/krb5.conf.d to enable the certauth plugin.

This fixes install on platforms which do not have /etc/krb5.conf.d.

https://pagure.io/freeipa/issue/6589

Reviewed-By: Martin Babinsky <mbabinsk@redhat.com>
Reviewed-By: Christian Heimes <cheimes@redhat.com>
Reviewed-By: Lukas Slebodnik <lslebodn@redhat.com>
2017-06-28 15:44:51 +02:00
..
certmonger renew agent: get rid of virtual profiles 2017-05-15 12:14:28 +02:00
conf Changing cert-find to go through the proxy instead of using the port 8080 2017-06-16 08:56:53 +02:00
html fix spelling mistake; minor rewording 2017-05-19 09:52:46 +02:00
migration Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
oddjob Add a new user to run the framework code 2017-02-15 07:13:37 +01:00
restart_scripts Turn off OCSP check 2017-06-06 13:33:54 +02:00
share install: do not assume /etc/krb5.conf.d exists 2017-06-28 15:44:51 +02:00
tools ipa-dns-install: remove check for local ip address 2017-06-20 11:29:41 +02:00
ui WebUI: add support for changing trust UPN suffixes 2017-06-14 16:55:15 +02:00
updates Add Role 'Enrollment Administrator' 2017-06-09 16:37:40 +02:00
wsgi wsgi plugins: mod_wsgi expects bytes as an output 2017-06-27 16:48:21 +02:00
Makefile.am Configure HTTPD to work via Gss-Proxy 2017-02-15 07:13:37 +01:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.