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

[CXF-8997] AbstractSTSToken and TransportBinding Tests use TLSv1 on IBM #1785

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

jgoodyear
Copy link
Contributor

AbstractSTSTokenTest and TransportBindingTests no longer need to set https protocol to TLSv1 on IBM Java.

Current builds of CXF 4.0.x on IBM Java will fail the AbstractSTSTokenTest and TransportBindingTests due to their use of TLSv1. Note: IBM JDKs disable TLSv1 by default since around Java 8 (https://community.ibm.com/community/user/wasdevops/blogs/hiroko-takamiya1/2021/06/19/ibm-java-80630-disables-tlsv1-tlsv11-by-default-ho).

Removing the test case IBM control flag allows the default TLS to pass the tests.

Patch tested on:
CentOS Stream 9 on POWER with IBM Semeru 17, RedHat OpenJDK 17, and Eclipse Adoptium (Temurin) 17.
Windows 11 Pro on x64 Intel with IBM Semeru 17, and Azul Zulu 17.
MacOS 14.4.1 on AArch64 with IBM Semeru 17, and Amazon Corretto 17.

…eed to set https protocol to TLSv1 on IBM Java
@reta reta merged commit 93a29d7 into apache:main Apr 3, 2024
4 checks passed
reta pushed a commit that referenced this pull request Apr 3, 2024
…eed to set https protocol to TLSv1 on IBM Java (#1785)

(cherry picked from commit 93a29d7)
reta pushed a commit that referenced this pull request Jul 9, 2024
…eed to set https protocol to TLSv1 on IBM Java (#1785)

(cherry picked from commit 93a29d7)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants