freeipa/install
Martin Basti 54a91c3ed3 Exclude o=ipaca subtree from Retro Changelog (syncrepl)
CA and DS have issues with Retro Changelog plugin. CA subtree should be
excluded from syncrepl.
This should improve speed of CA related operations too.

https://fedorahosted.org/freeipa/ticket/5538

Reviewed-By: Christian Heimes <cheimes@redhat.com>
2016-01-21 11:28:21 +01:00
..
certmonger Refactor ipautil.run 2015-12-14 10:54:23 +01:00
conf mod_auth_gssapi: Remove ntlmssp support and restrict mechanism to krb5 2015-11-26 15:20:19 +01:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html Drop configure.jar 2015-11-13 14:02:45 +01:00
migration Remove unused imports 2015-12-23 07:59:22 +01:00
oddjob Refactor ipautil.run 2015-12-14 10:54:23 +01:00
po translations: Update ipa.pot file 2015-12-02 12:40:48 +01:00
restart_scripts Remove unused imports 2015-12-23 07:59:22 +01:00
share Use only AES enctypes by default 2016-01-13 15:24:53 +01:00
tools logger: Use warning instead of warn 2016-01-18 17:49:54 +01:00
ui Set close button type attribute to 'button'. 2016-01-20 18:50:25 +01:00
updates Exclude o=ipaca subtree from Retro Changelog (syncrepl) 2016-01-21 11:28:21 +01:00
wsgi Modernize 'except' clauses 2015-08-12 18:17:23 +02:00
configure.ac trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02:00
Makefile.am trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02: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.