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
Installing zowe 1.19.1 with external CA failed, CA certificates was not exported to truststore. #2032
Comments
The following error reported in certificates setup script may not directly related to the failure of logon to desktop.
This may be a different problem? I saw following message in certificate setup log.
|
I can confirm this is a bug introduced in v1.18.0 release related to the quotation marks applied to this line https://github.com/zowe/zowe-install-packaging/blob/master/bin/apiml_cm.sh#L246. I will work on a fix and also move this issue to zowe-install-packaging. Thanks Jing Ren for reporting the issue! |
Signed-off-by: Jack (T.) Jia <jack-tiefeng.jia@ibm.com>
Signed-off-by: Jack (T.) Jia <jack-tiefeng.jia@ibm.com>
fixes #2032, issue of importing external CAs
Also applied to staging branch. |
Installing zowe 1.19.1 , when running zowe-setup-certificates.sh saw following error code.
After creating instance and start server, I failed to logon desktop. I asked about this issue in slack channel, Jack Jia pointed out there maybe some issue with external CAs not exported correctly.
I checked certificates setup log, seems in 1.19.1 version, extca1 and extca2 were missing in truststore. I ran certificates set up script several times, all failed. I was sure the external CA set in zowe-setup-certificates.env EXTERNAL_CERTIFICATE_AUTHORITIES was correct, I have used it for 1.17 and previous version. Could you please help to take a look?
Following was the three certificates in 1.17 truststore, in 1.19 I only have extca0.
In 1.17 certificate setup log, we can see following step was executed. But in 1.19.1 there's no such step.
Please let me know if this is not the correct place to report this issue. Thanks!
The text was updated successfully, but these errors were encountered: