freeipa/install
2014-11-26 14:33:23 +01:00
..
certmonger Fix wrong expiration date on renewed IPA CA certificates 2014-11-19 14:25:26 +00:00
conf Fixed KRA backend. 2014-11-04 16:33:16 +01:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02: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 Add a KRA to IPA 2014-08-22 09:59:31 +02:00
restart_scripts Add a KRA to IPA 2014-08-22 09:59:31 +02:00
share copy_schema_to_ca: Fallback to old import location for ipaplatform.services 2014-11-25 09:20:28 +01:00
tools Use singular in help metavars + update man pages. 2014-11-26 14:33:23 +01:00
ui webui: add radius fields to user page 2014-11-25 14:05:09 +01:00
updates Upgrade: fix trusts objectclass violationi 2014-11-13 13:31:17 +01:00
wsgi Remove trivial path constants from modules 2014-11-04 12:57:01 +01: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 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.