mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-24 16:10:02 -06:00
a59f6e00d9
bind-dyndb-ldap uses the krb5_keytab directive to set the path to the keytab to use. This directive was not being used in the configuration template, resulting in a failure to start named if the keytab path differed from the defaults. This issue was discovered when packaging FreeIPA for Debian, which is one of the platforms where the path is customized. Signed-off-by: Jarl Gullberg <jarl.gullberg@gmail.com> Fixes: https://pagure.io/freeipa/issue/9344 Reviewed-By: Timo Aaltonen <tjaalton@ubuntu.com> Reviewed-By: Rob Crittenden <rcritten@redhat.com> |
||
|---|---|---|
| .. | ||
| certmonger | ||
| custodia | ||
| html | ||
| migration | ||
| oddjob | ||
| restart_scripts | ||
| share | ||
| tools | ||
| ui | ||
| updates | ||
| wsgi | ||
| Makefile.am | ||
| README.schema | ||
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.