freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00

History

Rob Crittenden a48a84a5ea Set the ipa-modrdn plugin precedence to 60 so it runs last The default precedence for plugins is 50 and the run in more or less alphabetical order (but not guaranteed). This plugin needs to run after the others have already done their work. https://fedorahosted.org/freeipa/ticket/1370		2011-07-17 22:24:30 -04:00
..
conf	rename static to ui	2011-01-20 14:12:47 +00:00
html	HBAC deny warning	2011-07-06 21:52:00 +00:00
migration	Removed FreeWay font files.	2011-06-20 12:59:05 -04:00
po	Make dogtag an optional (and default un-) installed component in a replica.	2011-06-23 19:04:33 -04:00
share	Set the ipa-modrdn plugin precedence to 60 so it runs last	2011-07-17 22:24:30 -04:00
tools	Create tool to manage dogtag replication agreements	2011-07-17 22:16:32 -04:00
ui	Fixed label capitalization	2011-07-14 11:44:48 -04:00
updates	Set the ipa-modrdn plugin precedence to 60 so it runs last	2011-07-17 22:24:30 -04:00
configure.ac	rename static to ui	2011-01-20 14:12:47 +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

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.