mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-10-31 17:17:48 -05:00
Florence Blanc-Renaud
7ec0cb4ced
When certmonger renews the auditSigningCert for the CA or the KRA, it has to add the P trust flag to the NSS database in /etc/pki/pki-tomcat/alias. If IPA is installed in FIPS mode with an HSM, the certutil commands must be provided a password file containing both the internal token password and the HSM password, and the cert name must be prefixed with the tokenname (otherwise certutil -M succeeds but does not update the trust flags). Fixes: https://pagure.io/freeipa/issue/9705 Signed-off-by: Florence Blanc-Renaud <flo@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.