As of now, when security settings on target, e.g., clientCertAuth, are changed, existing data connections to target will continue to work. All subsequent http calls to target will fail, though. This leads to two issues:

1. data replication will continue with old security settings, this may not be what customer wants.

2. essential replication functions that reply on target info, e.g., topology change detector, will stop working, which leaves replication in a vulnerable state.

One way to fix this is to periodically poll target for security setting changes. This can be piggybacked on existing http calls to target or new calls.