Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS 1.3 Support #892

Closed
Joe-Winchester opened this issue Dec 2, 2020 · 5 comments
Closed

TLS 1.3 Support #892

Joe-Winchester opened this issue Dec 2, 2020 · 5 comments
Labels
architecture enhancement New feature or request Technical currency TSC Technical Steering Committee
Milestone

Comments

@Joe-Winchester
Copy link
Member

Is your feature request related to a problem or limitation? Please describe.
Investigate TLS 1.3 and allowed ciphers within Zowe

@Joe-Winchester Joe-Winchester added the enhancement New feature or request label Dec 2, 2020
@Joe-Winchester Joe-Winchester added the TSC Technical Steering Committee label Dec 2, 2020
@1000TurquoisePogs
Copy link
Member

Currently, node 12 supports tls 1.3, but I don't believe 8 does.
I heard from Petr that java 8 doesnt support tls 1.3 either.
Yet, sooner or later there will be a java that supports 1.3.
It could be a long time until the minimum java & node we support support 1.3, so until then I suggest a transition period where zowe will accept either 1.2 or 1.3, and clients can handle this behavior. It may also be possible for us to have a heterogeneous tls support by which our node services could have this 1.3-optional behavior while the java services wouldn't yet.

@supmi01
Copy link
Contributor

supmi01 commented Oct 11, 2021

I think it makes sense to list tls support per component.
Since Zowe is modular, to the point, you can run components like APIML standalone, without having to install node at all.

@supmi01
Copy link
Contributor

supmi01 commented Oct 12, 2021

It looks like TLS 1.3 support was added back to Java 8, in February this year please confirm @achmelo
I am reading this https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS220-008/index.html&request_locale=en
And this https://www.ibm.com/support/pages/apar/PH19502

@balhar-jakub balhar-jakub changed the title TLS 1.3 investigation TLS 1.3 Support May 4, 2023
@balhar-jakub balhar-jakub added this to the 23PI3 milestone May 4, 2023
@balhar-jakub
Copy link
Member

We need to verify that we have tests in place in the Marist system that uses TLS 1.3 setup. I believe this is missing at the moment.
Once we have this verification we need to make sure that the documentation is updated appropriately.

With V3 I believe we should look into changing TLS 1.3 as the default.

@1000TurquoisePogs
Copy link
Member

I've observed Zowe defaulting to TLS v1.3 for a long time, within v2 and v3.
The zowe yaml now makes this both more obvious but also configurable https://github.com/zowe/zowe-install-packaging/blob/v3.x/staging/example-zowe.yaml#L352
I'm closing this as a result but please re-open if you think I misunderstood.

@github-project-automation github-project-automation bot moved this from Technological Validation to Done in Technical Steering Committee Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture enhancement New feature or request Technical currency TSC Technical Steering Committee
Projects
Status: Done
Development

No branches or pull requests

8 participants