[HTCondor-users] populating a pool signing key to a new HA collector/scheduler?

[Thomas Hartmann <thomas.hartmann@xxxxxxx>]

Hi all,

short question, but it is possible to populate a newly spawned central 
manager (collector/scheduler) with a pool's signing key from an existing 
central manager?
I.e., when spawning a new cluster, assuming that a collector initializes 
itself with a a fresh pool signing key, can I populate another collector 
showing up with the same signing key with a TOFU-like request auto approval?
Or is it better to populate the new central manager with an existing key 
via a parallel trusted path (Puppet, Ansible,...)?

Cheers,
 Thomas

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature