freeipa

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

History

Rob Crittenden eaec3c4968 Add explicit instructions to ipa-replica-manage for winsync replication https://fedorahosted.org/freeipa/ticket/1946		2011-10-14 09:05:06 +02:00
..
conf	Revert "Always require SSL in the Kerberos authorization block."	2011-09-27 08:54:42 +02:00
html	Fixed links to images in config and migration pages	2011-10-06 23:24:12 -05:00
migration	Fixed links to images in config and migration pages	2011-10-06 23:24:12 -05:00
po	Ticket 1718 - Fix Spanish po translation file	2011-10-11 22:46:02 -04:00
share	Remove more redundant configuration values from krb5.conf.	2011-10-11 22:00:50 -04:00
tools	Add explicit instructions to ipa-replica-manage for winsync replication	2011-10-14 09:05:06 +02:00
ui	Fix dynamic display of UI tabs based on rights	2011-10-12 23:19:54 -04:00
updates	updates: Change default limits on ldap searches	2011-10-12 22:42:03 -04:00
configure.ac	ticket 1650 - compute accurate translation statistics	2011-08-18 14:25:58 +02: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.