mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-01-11 08:41:55 -06:00
b3c2197b7e
When Dogtag 10 based FreeIPA replica is being installed for a Dogtag 9 based master, the PKI database is not updated and miss several ACLs which prevent some of the PKI functions, e.g. an ability to create other clones. Add an update file to do the database update. Content is based on recommendation from PKI team: * https://bugzilla.redhat.com/show_bug.cgi?id=1075118#c9 This update file can be removed when Dogtag database upgrades are done in PKI component. Upstream tickets: * https://fedorahosted.org/pki/ticket/710 (database upgrade framework) * https://fedorahosted.org/pki/ticket/906 (checking database version) Also make sure that PKI service is restarted in the end of the installation as the other services to make sure it picks changes done during LDAP updates. https://fedorahosted.org/freeipa/ticket/4243 Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com> Reviewed-By: Petr Viktorin <pviktori@redhat.com> |
||
|---|---|---|
| .. | ||
| 10-config.update | ||
| 10-enable-betxn.update | ||
| 10-schema_compat.update | ||
| 10-selinuxusermap.update | ||
| 10-uniqueness.update | ||
| 19-managed-entries.update | ||
| 20-aci.update | ||
| 20-dna.update | ||
| 20-host_nis_groups.update | ||
| 20-indices.update | ||
| 20-nss_ldap.update | ||
| 20-replication.update | ||
| 20-syncrepl.update | ||
| 20-user_private_groups.update | ||
| 20-winsync_index.update | ||
| 21-ca_renewal_container.update | ||
| 21-replicas_container.update | ||
| 25-referint.update | ||
| 30-policy.update | ||
| 30-s4u2proxy.update | ||
| 40-automember.update | ||
| 40-delegation.update | ||
| 40-dns.update | ||
| 40-otp.update | ||
| 40-realm_domains.update | ||
| 40-replication.update | ||
| 45-roles.update | ||
| 50-7_bit_check.update | ||
| 50-dogtag10-migration.update | ||
| 50-groupuuid.update | ||
| 50-hbacservice.update | ||
| 50-ipaconfig.update | ||
| 50-krbenctypes.update | ||
| 50-lockout-policy.update | ||
| 50-nis.update | ||
| 55-pbacmemberof.update | ||
| 60-trusts.update | ||
| 61-trusts-s4u2proxy.update | ||
| 62-ranges.update | ||
| Makefile.am | ||
| README | ||
The update files are sorted before being processed because there are cases where order matters (such as getting schema added first, creating parent entries, etc). Updates are applied in blocks of ten so that any entries that are dependant on another can be added successfully without having to rely on the length of the DN to get the sorting correct. The file names should use the format #-<description>.update where # conforms to this: 10 - 19: Configuration 20 - 29: 389-ds configuration, new indices 30 - 39: Structual elements of the DIT 40 - 49: Pre-loaded data 50 - 59: Cleanup existing data 60 - 69: AD Trust 70 - 79: Reserved 80 - 89: Reserved These numbers aren't absolute, there may be reasons to put an update into one place or another, but by adhereing to the scheme it will be easier to find existing updates and know where to put new ones.