freeipa/install
2011-12-02 18:35:59 +00:00
..
conf Revert "Always require SSL in the Kerberos authorization block." 2011-09-27 08:54:42 +02:00
html Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
migration ticket 2022 - modify codebase to utilize IPALogManager, obsoletes logging 2011-11-23 09:36:18 +01:00
po Ticket 1718 - Fix Spanish po translation file 2011-10-11 22:46:02 -04:00
share Add NT domain GUID attribute. 2011-11-21 18:52:48 -05:00
tools Add DNS service records for Windows 2011-11-30 11:28:39 +01:00
ui Added cross browser support of Array.indexOf method 2011-12-02 18:35:59 +00:00
updates Enable automember for upgraded servers 2011-11-29 09:02:06 +01:00
configure.ac Fixed inconsistent image names. 2011-10-27 14:05:12 +00: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.