mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-11-03 12:48:53 -06:00
Rob Crittenden
42a94e9998
Originally the RA certificate was stored in the Apache NSS database so it was available natively to the framework. It was subsequently moved into PEM files even prior to the switch from mod_nss to mod_ssl. This code was introduced with 4.5.0 and was last seen in Fedora in 27 in 2017. We don't support direct in-place upgrades from such an old version so we should be safe from bricking a user's installation. Fixes: https://pagure.io/freeipa/issue/9739 Signed-off-by: Rob Crittenden <rcritten@redhat.com> Reviewed-By: Alexander Bokovoy <abokovoy@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.