Files
freeipa/install
Endi S. Dewata a95b44face Fixed sudo rule association dialogs.
The adder dialog for the user and host tables in sudo rule details
page have been fixed to use --not-in-sudorules to avoid showing
entries that are already added into the rule either directly or
indirectly via groups.

This does not apply to the command and run-as tables because they
do not support such option.

Ticket #1768
2011-09-09 19:47:27 +00:00
..
2011-08-29 17:54:49 -04:00
2011-08-17 17:28:25 +00:00
2011-08-31 16:46:12 +02:00
2011-09-07 13:02:43 +02:00
2011-09-09 19:47:27 +00:00
2011-01-20 14:12:47 +00:00

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.