Consider a method that parses our authconf collection from upscli_get_authconf_list() just to upscli_add_host_port_cert() en masse, and set up the one most applicable set of client identity data for that [user@host:port] combo that we want to use (e.g. the closest hit being inherited from a global default or host default section).
Consider extending same-named section support (including a named default global section) with an explicit sslbackend to land into separate list entries, so the same file can spell out settings for NSS and OpenSSL (Python, Perl) clients.
Follows up on issue #3329 and PR #3435.
Consider a method that parses our authconf collection from
upscli_get_authconf_list()just toupscli_add_host_port_cert()en masse, and set up the one most applicable set of client identity data for that[user@host:port]combo that we want to use (e.g. the closest hit being inherited from a global default or host default section).Consider extending same-named section support (including a named default global section) with an explicit
sslbackendto land into separate list entries, so the same file can spell out settings for NSS and OpenSSL (Python, Perl) clients.Follows up on issue #3329 and PR #3435.