We seem to support TLS Server Name Indication (SNI) in the interceptor which allows serving different TLS certificates from the single TLS endpoint.
IIRC, admins can configure multiple certificates the interceptor then uses for incoming TLS requests, SNI works automatically by default.
We should at least do the following:
Out of scope:
- rewriting the whole TLS config handling, it is IMO a bit wonky and maybe a separate topic
We seem to support TLS Server Name Indication (SNI) in the interceptor which allows serving different TLS certificates from the single TLS endpoint.
IIRC, admins can configure multiple certificates the interceptor then uses for incoming TLS requests, SNI works automatically by default.
We should at least do the following:
Out of scope: