Transfer Keys in v21 for TLS enabled agents

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

Are there any differences in how transfer keys work in v21 with TLS agents?

Environment

Release : 21.0

Component : AUTOMATION ENGINE

Resolution

The TLS enabled agents use a public key that's created from the keypair.  The following scenarios are in place with two 21.0 (TLS enabled) windows agents, one called WIN01, second called WIN02:

Agent WIN01 - same agent server name, change folder structure, same agent name as one that already started: This starts up correctly
Agent WIN01 - same agent server name, same folder structure, change agent name to WIN02: This starts up correctly
Agent WIN01 - Change agent server name, same folder structure, same agent name: This starts up correctly
Agent WIN01 - Change agent server name, change folder structure, change agent name to WIN02: This starts up correctly
Agent WIN01 - Change agent server name, remove info from .security folder (this is the public key), keep same agent name: Will not start up as the system thinks the public key has changed

So if the same-named agent needs to be moved or deployed on a different server, the ./security folder should be copied as well so that the same public key is used