freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-26 08:51:50 -06:00

History

Endi S. Dewata 1dc48bca51 Removed debugging message.		2011-01-13 13:09:07 -05:00
..
conf	bad request workaround not a permanent fix, but makes the web server accept valied request. https://fedorahosted.org/freeipa/ticket/691	2011-01-07 06:14:54 -05:00
html	type prevented rendering on firefox4	2010-12-17 16:07:09 -05:00
migration	Change FreeIPA license to GPLv3+	2010-12-20 17:19:53 -05:00
po	Change FreeIPA license to GPLv3+	2010-12-20 17:19:53 -05:00
share	Restrict anonymous tgts	2011-01-12 17:20:09 -05:00
static	Removed debugging message.	2011-01-13 13:09:07 -05:00
tools	Exit if a DNS A or AAAA record doesn't exist for the replica we are preparing.	2011-01-11 10:22:33 -05:00
updates	Move automount, default HBAC services, netgroup and hostgroup bootstrapping.	2010-12-17 17:31:19 -05:00
configure.ac	build tweaks - use automake's foreign mode, avoid creating empty files to satisfy gnu mode - run autoreconf -f to ensure that everything matches	2010-11-29 11:39:55 -05: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.