You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change enables TLS-based communication with the Registrar service
in the push model agent, providing secure registration and activation.
Key changes:
- Added registrar_tls_enabled, registrar_tls_ca_cert,
registrar_tls_client_cert, and registrar_tls_client_key configuration
options with empty defaults for backwards compatibility
- Updated RegistrarClientBuilder to accept TLS configuration parameters
(ca_certificate, certificate, key, insecure, timeout)
- Modified RegistrarClient to use HTTPS client when TLS is configured,
falling back to plain HTTP when TLS parameters are not provided
- Refactored to use single ResilientClient for all HTTP/HTTPS requests
instead of maintaining separate client instances
- Added RegistrarTlsConfig struct in push model agent to manage TLS
configuration from config file
- Updated StateMachine to accept and pass registrar_tls_config to
registration functions
Backwards compatibility:
- Defaults to plain HTTP when registrar_tls_enabled is false (default)
- Defaults to plain HTTP when TLS certificate paths are empty (default)
- TLS only enabled when all three certificate paths are provided AND
registrar_tls_enabled is true
- Pull model agent unchanged - maintains existing behavior with None
values for all new TLS fields
The implementation separates Registrar TLS configuration from Verifier
TLS configuration, allowing each service to be secured independently
based on deployment requirements.
Co-Authored-By: Claude <[email protected]>
Signed-off-by: Sergio Arroutbi <[email protected]>
0 commit comments