freeipa/install
2011-10-24 15:10:11 +02:00
..
conf Revert "Always require SSL in the Kerberos authorization block." 2011-09-27 08:54:42 +02:00
html Fixed: Duplicate CSS definitions 2011-10-19 10:44:44 -02:00
migration Fixed: Duplicate CSS definitions 2011-10-19 10:44:44 -02:00
po Ticket 1718 - Fix Spanish po translation file 2011-10-11 22:46:02 -04:00
share Remove more redundant configuration values from krb5.conf. 2011-10-11 22:00:50 -04:00
tools Add support for systemd environments and use it to support Fedora 16 2011-10-24 15:10:11 +02:00
ui Ticket 1201 - Unable to Download Certificate with Browser 2011-10-21 15:29:47 +00:00
updates updates: Change default limits on ldap searches 2011-10-12 22:42:03 -04:00
configure.ac ticket 1650 - compute accurate translation statistics 2011-08-18 14:25:58 +02:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00: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.