freeipa

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

History

Adam Young 4270e26adb define entities using builder and more declarative syntax merged hbac and sudo in to single files associaton facet and table supports linking		2011-03-31 17:29:33 -04: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	Use ldapi: instead of unsecured ldap: in ipa core tools.	2011-03-03 14:04:34 -05:00
po	Update translation file (ipa.pot).	2011-03-18 14:59:34 -04:00
share	Store list of non-master replicas in DIT and provide way to list them	2011-03-02 09:46:46 -05:00
tools	Add note about ipa-dns-install to ipa-server-install man page.	2011-03-31 16:38:43 -04:00
ui	define entities using builder and more declarative syntax	2011-03-31 17:29:33 -04:00
updates	Allow a client to enroll using principal when the host has a OTP	2011-03-30 10:03:44 -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.