When auth is enabled, the cluster times gossiped throughout a sharded cluster are signed and validated using keys from a collection on the config server. If a node in one cluster with auth enabled receives a message with a cluster time signed using the keys from a different cluster (or not signed at all), that request should be rejected by the node and the node should not advance its understanding of the latest config server opTime. The purpose of this ticket is to verify this with a test.