freeipa/install
2012-04-26 09:00:22 +02:00
..
conf Implement password based session login 2012-02-27 05:57:43 -05:00
html Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
migration Forms based authentication UI 2012-03-02 11:04:33 +01:00
po text unit test should validate using installed mo file 2012-04-10 18:11:48 -04:00
restart_scripts Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04:00
share - add a pair of ethers maps for computers with hardware addresses on file 2012-04-26 09:00:22 +02:00
tools Configure SELinux for httpd during upgrades 2012-04-03 18:20:51 -04:00
ui Added permission field to delegation 2012-04-17 17:53:25 -04:00
updates - add a pair of ethers maps for computers with hardware addresses on file 2012-04-26 09:00:22 +02:00
configure.ac Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04:00
Makefile.am Configure certmonger to execute restart scripts on renewal. 2012-04-10 01:08:41 -04: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.