-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
SSL CA Certificate loading is broken... #199
Comments
@brendandburns I have left comments in #197 |
@brendanburns
it is because of default value of verifySSl being true. |
@kondapally1989 I don't think that's quite correct. The underlying problem is that applySslSettings can not be called more than once after the CA certificate has been set. We need to ultimately fix that in the ApiClient so that applySslSettings is idempotent... |
@ceeaspb I don't quite follow your comments... Can you clarify the issue you're seeing and the needed repro? Thanks |
@brendanburns |
with #200 similarly it works. I didn't spot the PR earlier. thanks |
@brendanburns byte[] targetArray = null ;
try {
targetArray = new byte[sslCaCert.available()];
sslCaCert.read(targetArray);
}
catch(Exception e) {
}
sslCaCert = new ByteArrayInputStream(targetArray);
char[] password = null; // Any password will work.
InputStream sslCaCertCopy = new ByteArrayInputStream(targetArray);
CertificateFactory certificateFactory = CertificateFactory.getInstance("X.509");
Collection<? extends Certificate> certificates = certificateFactory.generateCertificates(sslCaCertCopy); above works without placing client.setSslCaCert at end of ClientBuilder |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We try to load the CA certificate twice, but the
InputStream
is exhausted...The text was updated successfully, but these errors were encountered: