[Utility] allow configuration of TLS Settings for HTTPS services

[adshmh]

Objective

HTTPS services may need custom, individualized configuration, e.g. allowing self-signed certificates in some cases.

Origin Document

Goals

• Allow custom TLS configuration for each service

Deliverable

• PR to add the feature
• Updated user documentation

Non-goals / Non-deliverables

General issue deliverables

• Update any relevant local/global README(s)
• Update relevant source code tree explanations
• Add or update any relevant or supporting mermaid diagrams

Testing Methodology

• Task specific tests or benchmarks: make ...
• New tests or benchmarks: make ...
• All tests: make test_all
• LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
• k8s LocalNet: verify a k8s LocalNet is still functioning correctly by following the instructions here

---

Creator: [@adshmh]
Co-Owners: [@Olshansk ]

[Olshansk]

Thanks for putting this together @adshmh. Ccing @bryanchriswhite for visibility since he has thought about TLS as well.

---

Questino about this:

, e.g. allowing self-signed certificates in some cases.

Since this is a decentralized, permissionless network, aren't all TLS certs going to be self-signed?

[adshmh]

Since this is a decentralized, permissionless network, aren't all TLS certs going to be self-signed?

One exception could be specific services, e.g. a Portal, with easy-to-establish identity. The TLS here is more about privacy, integrity, and/or identity than permission (I think, but not sure yet whether the decentralized nature of the network could make this a non-issue)