Repeater to agent

For traffic between a repeater and an agent, TrueSight Server Automation relies on TLS to secure communication and the following options for authenticating the repeater host to the agent:

• Self signed, client-side certs — Enables agents to authenticate repeaters. To accomplish this, agents are provisioned with SHA1 fingerprints of repeaters' self-signed certificates.
  
  Implementation
  
  For implementation details, see Implementing security - Repeater to agent.
  
  
• IP address — Limits an agent's incoming traffic to IP addresses of specific repeaters. (If necessary, Application Servers and specific clients can be specified in the same way.)
  
  Implementation
  
  To implement this approach, modify the exports file on each agent. For more information, see Configuring-the-exports-file.
  
  
• No authentication — By default, when a repeater connects to an agent, no authentication occurs.
  
  Implementation
  
  A default installation of TrueSight Server Automation provides no authentication for this communication leg.