mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-11-03 12:48:53 -06:00
Rob Crittenden
8fda2e0dc7
Since PKI v10.8.0 the PKIConnection object can longer be created for a specific subsystem. The client that consumes the connection specifies the subsystem instead. Use this new API unconditionally as we require PKI >= 10.10.0 and what is available in supported repos is generally 11.5.0+. See https://github.com/dogtagpki/pki/wiki/PKI-10.8-Python-Changes Fixes: https://pagure.io/freeipa/issue/9691 Signed-off-by: Rob Crittenden <rcritten@redhat.com> Reviewed-By: Florence Blanc-Renaud <flo@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.