freeipa/install
Pavel Vomacka 9d2ef64fb9 Coverity: removed useless semicolon which ends statement earlier
Reviewed-By: Tomas Krizek <tkrizek@redhat.com>
2017-01-18 09:15:54 +01:00
..
certmonger renew agent: handle non-replicated certificates 2017-01-16 14:37:25 +01:00
conf Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
html Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
migration Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
oddjob Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
restart_scripts Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
share dsinstance: extract function for writing certmap.conf 2017-01-11 15:26:20 +01:00
tools Add sanity checks for use of --ca-subject and --subject-base 2017-01-11 15:28:50 +01:00
ui Coverity: removed useless semicolon which ends statement earlier 2017-01-18 09:15:54 +01:00
updates Remove "Request Certificate with SubjectAltName" permission 2016-12-21 17:04:18 +01:00
wsgi Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
Makefile.am Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +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.