freeipa/install
Timo Aaltonen e6c707b168 ipaplatform, ipa.conf: Use paths variables in ipa.conf.template
Reviewed-By: Stanislav Laznicka <slaznick@redhat.com>
2018-02-09 09:14:22 +01:00
..
certmonger ipa-cacert-manage renew: switch from ext-signed CA to self-signed 2017-10-18 12:34:03 +02:00
html Address more 'to login' 2017-12-12 12:53:21 +01:00
migration logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
oddjob wsgi, oddjob: remove needless uses of Env 2017-07-14 15:55:59 +02:00
restart_scripts renew_ra_cert: fix update of IPA RA user entry 2017-12-07 17:28:12 +01:00
share ipaplatform, ipa.conf: Use paths variables in ipa.conf.template 2018-02-09 09:14:22 +01:00
tools Check if replication agreement exist before enable/disable it 2018-02-09 08:30:21 +01:00
ui Documenting kinit_lifetime in /etc/ipa/default.conf 2018-01-12 20:33:20 +01:00
updates 10-config.update: remove nsslapd-sasl-max-buffer-size override as https://pagure.io/389-ds-base/issue/47457 was fixed directly in 389 Directory Server. 2018-01-04 16:36:54 +01:00
wsgi logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
Makefile.am Move config templates from install/conf to install/share 2018-02-09 09:14:22 +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.