mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-10-25 22:50:12 -05:00
Christian Heimes
2bfe5ff689
The httpd options Allow, Deny, Order, and Satisfy are deprecated in Apache httpd 2.4. These options are provided by the mod_access_compat module and should no longer be used. Replace "Allow from all" with "Require all granted". Removal of "Satisfy Any" needs more investigation. See: httpd.apache.org/docs/2.4/upgrading.html See: httpd.apache.org/docs/2.4/mod/mod_access_compat.html Fixes: pagure.io/freeipa/issue/8305 Signed-off-by: Christian Heimes <cheimes@redhat.com> Reviewed-By: Rob Crittenden <rcritten@redhat.com>
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.