TLS 1.3 handshake is not yet supported by most browsers, including Chrome, therefore, we should stick with TLS 1.2 handshakes for browser based clients for now.
For simplifying development and debugging of x509 authentication workflows, it will definitely help to enforce the use of TLS 1.2 protocol and ciphers in the dev container's default apache config.
TLS 1.3 handshake is not yet supported by most browsers, including Chrome, therefore, we should stick with TLS 1.2 handshakes for browser based clients for now.
The rucio server already enforces this: https://github.com/rucio/containers/blob/c3d12c8b8826da1e379f5fcfe015a0c5fc210a15/server/rucio.conf.j2#L62-L69
For simplifying development and debugging of x509 authentication workflows, it will definitely help to enforce the use of TLS 1.2 protocol and ciphers in the dev container's default apache config.