mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-10-25 14:40:16 -05:00
Rob Crittenden
43f0284080
This reduces the reliance on specific REST/XML API in PKI and will allow the pki client library to choose which RPC API(s) to use. Add the new, versioned REST endpoint paths (v1, v2) to the httpd configuration. This needs additional refactoring once the certprofile class is ported and the RestClient class can be dropped or repurposed so some of the duplication can be re-centralized. Also catch a bare Exception when we can't reach the local server on port 443 in ipa-ca-install. This is because proxying isn't configured yet. So catch that Exception and try again with port 8443 like other exceptions. Fixes: https://pagure.io/freeipa/issue/9738 Signed-off-by: Rob Crittenden <rcritten@redhat.com> Signed-off-by: Fraser Tweedale <ftweedal@redhat.com> Reviewed-By: Fraser Tweedale <ftweedal@redhat.com> Reviewed-By: Florence Blanc-Renaud <frenaud@redhat.com> Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com> Reviewed-By: Rafael Guterres Jeffman <rjeffman@redhat.com> Reviewed-By: Thomas Woerner <twoerner@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.