freeipa

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

History

Adam Young de28abc236 delegation work around Since the delegation enityt is using membergroup as the property name at this stage, we can use that as the value until the pluing is consistant		2011-01-29 23:16:08 -05:00
..
conf	rename static to ui	2011-01-20 14:12:47 +00:00
html	error handling style	2011-01-25 16:47:09 -05:00
migration	error handling style	2011-01-25 16:47:09 -05:00
po	Removed 'name' from 'Sudo Command Group name'.	2011-01-24 13:33:00 -05:00
share	Address entryusn initialization on replica installation	2011-01-28 13:58:43 -05:00
tools	Don't perform some API self-tests in production mode for performance reasons	2011-01-28 18:49:17 -05:00
ui	delegation work around	2011-01-29 23:16:08 -05:00
updates	Move automount, default HBAC services, netgroup and hostgroup bootstrapping.	2010-12-17 17:31:19 -05: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.