mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-09-03 20:52:56 -05:00
Florence Blanc-Renaud
7b149b3c7f
ipa-replica-conncheck can be called with --principal / --password or with an existing Kerberos credential cache in order to supply the authorized identity logging in to the master machine (in auto-master-check mode). In domain-level 0, the tool is called with --principal and password and tries to obtain a TGT by performing kinit, but does not set the env var KRB5CCNAME. Subsequent calls to IPA API do not use the credential cache and fail. In this case, ipa-replica-conncheck falls back to using SSH to check master connectivity instead of IPA API, and the ssh check is less robust. The code should set the KRB5CCNAME env var for IPA API to use the credential cache. Fixes: https://pagure.io/freeipa/issue/7221 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.