You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am kindly asking for clarification on the Proxying step-ca traffic section of the production considerations documentation. Specifically, I would like to understand if this is accurate or not:
step will expect to be able to perform a TLS handshake with the proxy, and use the CA's root certificate to complete the trust chain. So, for inbound TLS connections, the proxy should use a server certificate issued by step-ca.
What seems to be the case is that whichever CA issued the proxy certificate, one can use the --root parameter with step ca commands to make step trust the issuing CA (ref). So, it seems that there is no requirement to have the proxy use certificates issued by step-ca, contrary to what the documentation mentions. Did I miss something?
The text was updated successfully, but these errors were encountered:
Hey @hasan7n, yes, it's likely that will work in terms of ensuring the CLI will trust the connection. However, it's not guaranteed that all functionalities will work while operating in such a configuration. That's why we don't explicitly mention this in our docs, currently.
I am kindly asking for clarification on the
Proxying step-ca traffic
section of the production considerations documentation. Specifically, I would like to understand if this is accurate or not:What seems to be the case is that whichever CA issued the proxy certificate, one can use the
--root
parameter withstep ca
commands to makestep
trust the issuing CA (ref). So, it seems that there is no requirement to have the proxy use certificates issued by step-ca, contrary to what the documentation mentions. Did I miss something?The text was updated successfully, but these errors were encountered: