--- title: "Collective Replication" slug: "collective-replication-v7-0" description: "Collective replication enables centralized configuration distribution, ensuring consistent security and access across multiple target Collectives." tags: ["Collective Replication", "Replication Source", "Replication Targets"] status: "update" updated: 2026-09-18T21:11:49Z published: 2026-09-18T21:11:49Z canonical: "support.appgate.com/collective-replication-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Collective Replication Collective replication distributes a shared configuration baseline from a **source Collective** to one or more **target Collectives**. The shared configuration can include policies, entitlements, conditions, roles, and more. Collective replication helps organizations and managed service providers (MSPs) scale consistently across regions, tenants, and environments while maintaining a governed security and access posture. Collective replication provides: - Centralized configuration distribution to multiple target Collectives, whether in a single enterprise or across multiple tenants. - Continued access even when parts of the environment are unreachable, degraded, or operating offline. - Safe, reliable movement of a configuration between lifecycle stages, keeping non-production and disaster recovery environments functional. Collective replication is a separately licensable feature. For more information, see [Licenses](/v1/docs/licenses-v7-0). ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/collective-replication-1-architecture.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A31%3A21Z&se=2026-11-21T22%3A31%3A21Z&sr=b&sp=r&sig=1qDjWsCp%2FRw9Pi4v4j%2BB3cEVEfhk3OPz%2Bbt081c2Pg8%3D) #### Source Collective The **source Collective** holds the [entities](/v1/docs/collective-replication-v7-0#replicated-entities) to replicate. From the source Collective, administrators can: - Configure entities. - Configure replication target Collectives and assign tags to replicate to each target Collective. - Control which entities replicate to each target Collective by applying the target Collective’s tag. The source Collective acts as the central point of configuration distribution for all subscribed target Collectives. #### Target Collective The **target Collective** receives a selected subset of AppGate ZTNA [entities](/v1/docs/collective-replication-v7-0#replicated-entities) from the source Collective. The target Collective uses the Admin API and a service on the Controller on which the replication was configured. It contains a replicated copy of only the entities tagged for that target Collective. Collective replication uses a pull-down model: - The target Collective connects to the source Collective. - The target Collective retrieves (pulls) the entities it needs using the admin API. - The source Collective does not maintain a constant connection to the target Collective, reducing dependency on continuous connectivity. --- ## Registering a target Collective Before a target Collective can receive a configuration, it must be registered with the source Collective. To register the target Collective: 1. In the **source Collective**, generate a registration key in the [**Replication Targets**](/v1/docs/replication-targets-v7-0#configuring-a-replication-target) page (System > Replication Targets) and copy it. 2. In the **target Collective**, paste the registration key into the ***Key*** field on the [**Replication Source**](/v1/docs/replication-source-v7-0) (System > Replication Source) page to connect to the source Collective. 3. In the **source Collective**, apply one or more of the target Collective’s tags to the entities to replicate—for example, Sites, policies, or entitlements. Only entities with at least one of those tags are eligible for replication to that target Collective. --- ## Replication synchronization Once registered, a target Collective synchronizes its configuration with the source Collective in two ways: periodic or on-demand replication. ### Periodic replication The **target Collective** periodically pulls configuration from the **source Collective** using the admin API. To see when the next replication will occur, go to the **Replication Source** page and check ***Source Replication Status***. ### On-demand replication To trigger a manual replication: 1. In the **target Collective**, go to the **Replication Source** page. 2. Select **Actions** > ***Replicate from source now****.* ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/collective-replication-2-sync-lifecycle.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A31%3A21Z&se=2026-11-21T22%3A31%3A21Z&sr=b&sp=r&sig=oQxn85hVUZM1ifbNjwCcbO3Uw0NUSGXB%2F4hUTB1A6%2F4%3D) --- ## CA certificate renewal with Collective Replication When renewing the CA certificate (Settings > Licenses) for a Collective that uses Collective Replication, wait at least 30 minutes after uploading the new certificate before activating it. Replication runs every 15 minutes and receives the next CA certificate automatically during authentication. Activating the CA certificate before Collective Replication receives it breaks replication and requires manual reregistration. The 30-minute wait accounts for delays caused by system load, network latency, and internal timing. --- ## **Disconnecting and reconnecting replication** To remove entities from the target Collective before disconnecting: 1. In the source Collective, go to **Replication Targets**. 2. Select **Actions** > ***Change item replication tags*** *> Remove item replication tag*. 3. Select the tags to remove from the drop-down menu. 4. Wait for the next sync. 5. In the target Collective, go to **Replication Source** and select **Actions** > ***Disconnect***. If you do not need to remove entities first, select ***Disconnect*** directly. When you reconnect a target Collective to the same source: 1. Previously replicated entities are automatically reclaimed by their matching IDs. 2. Reclaimed entities: - Become read-only again. - Have their configuration replaced with the current version from the source Collective. - Lose any changes made during the disconnected period. To preserve changes made while disconnected, clone the entity before reconnecting. ### Service downtime restrictions Do not stop Collective replication for extended periods. Restart the service within three to seven days of stopping it. If downtime exceeds this window, you must reregister the target Collective to resume replication. --- ## Replicated entities The following AppGate ZTNA entities can be replicated: - Admin roles - Client profile groups - Conditions - Criteria scripts - Device claim scripts - Entitlement scripts - Entitlements - Identity providers - IP pools - MFA providers - Policies - Ringfence rules - Sites - Tags (only the tags configured for the target Collective) - User claim scripts If you attempt to edit a replicated entity, a message with a blue **R** icon indicates that the entity cannot be modified. To make a replicated entity editable, clone the entity or disconnect the target Collective. > [!NOTE] > NOTE > > Only the tags specified for the target Collective are included in the replicated entities ### Entity relationships and order Some entities depend on others. For example: - **Sites** are foundational and referenced by many other entities. - **Entitlements** require that their referenced Sites already exist. Because of these dependencies, tag all interdependent entities with the same tags. Incomplete tagging produces replication warnings and an incomplete replication. --- ## Secrets management between Collectives Collective replication uses the standard Controller API, which does not expose secrets. You must manually move secrets from the source Collective to the target Collective. The following fields are treated as secrets: | Field Name | Admin UI Location | | --- | --- | | ***Client Secret*** | Identity Providers > OIDC > Google OIDC Configuration > Enable | | ***Password*** | Sites > Cloud Resolvers > Illumio Resolvers | | ***Password*** | Sites > Cloud Resolvers > VMware VSphere Resolvers | | ***Password*** | Sites > Tunneling > Tunnel Traffic > Terminate tunneled… > PKCS #12 Files | | ***Secret*** | Sites > Cloud Resolvers > Azure Resolvers | | ***Service Access Key*** | Sites > Cloud Resolvers > AWS Resolvers > Access Method > Use Access Key | | ***Service Account Password*** | Identity Providers > LDAP/LDAP Certificate > LDAP Configuration | | ***Shared Secret*** | Identity Providers > RADIUS > RADIUS Configuration | | ***User Shared Secret*** | MFA Providers > Authentication > Authentication Mode > RADIUS server MFA | | ***User Shared Secret*** | MFA Providers > Authentication > Authentication Mode > Appgate SDP Challenge-Response MFA | If you have not moved these fields to the Secrets store: 1. See [Secrets](/v1/docs/secrets-v7-0) to add the secret. 2. Go to the field, select ***Refer to local secret***, and select the saved secret from the drop-down menu. Add the secret to the target Collective manually, using the same name as in the source Collective. If an entity uses a standard password entry or the secret is missing, replication of that entity fails and a warning appears in the **Replication Status Details** page. --- ## Monitoring replication health ### Replication Status Details After Collective replication starts, you can view replication status from: - The **Replication Targets** page, by selecting the health status of a target. - The **Replication Source** page, by selecting the replication entry under ***Source Replication Status***. Both options open the **Replication Status Details** window, which lists entities and how many have completed replication. Possible statuses are: - ***Healthy****.* All entities replicated successfully. - ***Warning****.* Only some entities replicated. - ***Error****.* Replication failed. Error details are provided.