mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-02-25 18:55:28 -06:00
00a84464ea
When deploying ACME set up configsources.conf to retrieve engine configuration from engine.conf. In the initial configuration, the ACME service is disabled (i.e. it will refuse to service requests). A subsequent commit will add command(s) for flipping the ACME service on or off (on a per-server basis). Later we will move to LDAP configuration so that management of the ACME service is deployment-wide. The default configuration also disables issuance of wildcard certificates. Part of: https://pagure.io/freeipa/issue/4751 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.