Struct epp_proxy::client::ClientConf

pub struct ClientConf<'a, C: Into<Option<&'a str>>> {

    pub host: &'a str,
    pub tag: &'a str,
    pub password: &'a str,
    pub log_dir: PathBuf,
    pub client_cert: Option<ClientCertConf<'a>>,
    pub source_address: Option<&'a IpAddr>,
    pub root_certs: &'a [&'a str],
    pub danger_accept_invalid_certs: bool,
    pub danger_accept_invalid_hostname: bool,
    pub new_password: C,
    pub pipelining: bool,
    pub errata: Option<String>,
    pub nominet_dac: Option<NominetDACConf<'a>>,
    pub keepalive: bool,
}

Fields

host: &'a str

The server connection string, in the form domain:port

tag: &'a str

The client ID/tag to login with

password: &'a str

The password to login with

log_dir: PathBuf

Directory path to log commands to

client_cert: Option<ClientCertConf<'a>>

source_address: Option<&'a IpAddr>

Source address to bind the TLS connection to, for IP based ACLs etc.

root_certs: &'a [&'a str]

List of PEM file paths

danger_accept_invalid_certs: bool

Accept invalid TLS certs

danger_accept_invalid_hostname: bool

Accept TLS certs with a hostname that doesn’t match the DNS label

new_password: C

New password to set after login

pipelining: bool

Does the server support multiple commands in flight at once

errata: Option<String>

Errata of this server

nominet_dac: Option<NominetDACConf<'a>>

keepalive: bool

Should the client send keepalive commands automatically