freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00

History

Rob Crittenden e648e03d0c Set ipaUniqueId to be unwritable and add to uniqueness configuration. We don't want admins messing with this value. ticket 231		2010-09-20 15:59:53 -04:00
..
conf	IPA HTTPD config uses /usr/share/static as target for /ipa/ui	2010-08-09 15:07:06 -04:00
html	Get merged tree into an installalble state.	2009-02-03 15:29:20 -05:00
migration	Add DS migration plugin and password migration page.	2010-01-20 16:54:17 -05:00
po	This patch removes the existing UI functionality, as a prep for adding the Javascript based ui.	2010-07-29 10:44:56 -04:00
share	Set ipaUniqueId to be unwritable and add to uniqueness configuration.	2010-09-20 15:59:53 -04:00
static	links and facet icons	2010-09-20 12:11:33 -04:00
tools	Add missing man pageas for ipa-dns-install and ipa-upgradeconfig.	2010-09-20 15:57:21 -04:00
updates	Enabling SUDO support	2010-09-16 11:31:27 -04:00
configure.ac	Changes to the install and config files to support deploying the javascript code.	2010-08-06 11:55:52 -04:00
Makefile.am	Changes to the install and config files to support deploying the javascript code.	2010-08-06 11:55:52 -04:00
README.schema	Add some basic rules for adding new schema	2010-08-27 13:40:37 -04:00

README.schema

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.