freeipa/install
Martin Basti 30551a8aa3 Add NSEC3PARAM to zone settings
Ticket: https://fedorahosted.org/freeipa/ticket/4413
Reviewed-By: Petr Vobornik <pvoborni@redhat.com>
2014-07-02 14:54:41 +02:00
..
certmonger ipaplatform: Move paths from installers to paths module 2014-06-26 09:22:21 +02:00
conf Add /session/token_sync POST support 2014-06-26 15:55:24 +02:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html webui: remove remnants of jquery-ui 2014-06-10 10:23:22 +02:00
migration ipaplatform: Move all filesystem paths to ipaplatform.paths module 2014-06-16 19:48:20 +02:00
po Update translations 2014-06-27 16:40:02 +02:00
restart_scripts ipaplatform: Remove redundant imports of ipaservices 2014-06-16 19:48:20 +02:00
share Add NSEC3PARAM to zone settings 2014-07-02 14:54:41 +02:00
tools ipaplatform: Move paths from installers to paths module 2014-06-26 09:22:21 +02:00
ui Add NSEC3PARAM to zone settings 2014-07-02 14:54:41 +02:00
updates Add NSEC3PARAM to zone settings 2014-07-02 14:54:41 +02:00
wsgi ipaplatform: Move all filesystem paths to ipaplatform.paths module 2014-06-16 19:48:20 +02:00
configure.ac RCUE initial commit 2014-01-21 12:04:02 +01:00
Makefile.am Change group ownership of CRL publish directory 2013-07-16 12:17:40 +02:00
README.schema

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.