mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-10-25 14:40:16 -05:00
Florence Blanc-Renaud
49cf5ec64b
The scenario switching from externally signed CA to self-signed CA is currently failing because the certmonger helper goes through the wrong code path when the cert is not self-signed. When the cert is not self-signed but the admin wants to switch to self-signed a new cert needs to be requested, not retrieved from LDAP. https://pagure.io/freeipa/issue/7173 Reviewed-By: Fraser Tweedale <ftweedal@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.