freeipa/install
2012-10-04 22:15:36 -04:00
..
certmonger Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
conf Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Removal of delegation-uris instruction from browser config 2012-10-04 18:35:47 -04:00
migration Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
po Update the pot file (translation source) 2012-09-12 22:04:16 -04:00
restart_scripts Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
share Add new ipaIDobject to DNA plugin configuraton 2012-10-04 22:15:36 -04:00
tools Add SIDs for existing users and groups at the end of ipa-adtrust-install 2012-10-04 22:15:36 -04:00
ui Configuration pages changed to use new FF extension 2012-10-04 18:08:26 -04:00
updates Add new ipaIDobject to DNA plugin configuraton 2012-10-04 22:15:36 -04:00
configure.ac Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
Makefile.am Kerberos authentication extension makefiles 2012-10-04 18:07:34 -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.