freeipa

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

History

Rob Crittenden aab27a76e2 Require ipactl be run as root to avoid a lot of misleading error msgs. Trying to run ipactl as non-root results in a slew of bogus error messages, some of which come because dirsrv can't read certain files as the wrong user, some based on our handling of that fact. ticket 936		2011-02-15 14:21: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	Fix migration page	2011-02-11 13:28:22 -05:00
po	Removed 'name' from 'Sudo Command Group name'.	2011-01-24 13:33:00 -05:00
share	Fine tuning DNS options	2011-02-14 14:45:22 -05:00
tools	Require ipactl be run as root to avoid a lot of misleading error msgs.	2011-02-15 14:21:08 -05:00
ui	DNS record search	2011-02-14 13:28:42 -05:00
updates	Add permission/privilege for updating IPA configuration.	2011-02-14 10:22:55 -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.