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
The builtin TLS capabilities of each Zowe server varies considerably; it can vary by capability, but also by ways in which the capabilities are configured.
Consider these scenarios. How would a user configure all of Zowe's servers to:
Limit the minimum TLS version used
Limit the maximum TLS version used
Limit the ciphers used
Limit the curves used
Stating which IP/hostname(s) to bind to (including, ipv4 vs ipv6)
Documentation may not exist for several servers, and perhaps some do not even support customizing these things.
Even if they do support & document how to customize these, there would be different ways for each server because the codebases are not unified with regards to this. There are Java ways to do things, there are nodejs ways to do things, etc.
Solution:
Create a standard area within zowe.yaml's "zowe" section which details the defaults for HTTPS settings, such as but not limited to the above cases.
Create a standard area within each "component" section of zowe.yaml such that each component could have overrides.
Document these in the Zowe schema
Enhance our servers to utilize this information when available. note: configmgr templating could be used to assign already-existing configuration parameters of our servers to these new standards, so that the enhancement could be reduced to configuration default changes rather than code changes, if desired.
The text was updated successfully, but these errors were encountered:
i started some work here zowe/zowe-install-packaging#3356 but would be happy if others picked it up or gave feedback, because it's something i was only working on with spare time at the moment.
The builtin TLS capabilities of each Zowe server varies considerably; it can vary by capability, but also by ways in which the capabilities are configured.
Consider these scenarios. How would a user configure all of Zowe's servers to:
Documentation may not exist for several servers, and perhaps some do not even support customizing these things.
Even if they do support & document how to customize these, there would be different ways for each server because the codebases are not unified with regards to this. There are Java ways to do things, there are nodejs ways to do things, etc.
Solution:
The text was updated successfully, but these errors were encountered: