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
We installed Zowe 2.12 in z/OS 2.5 several months ago, and configured using zowe.yaml scenario 1 “PKCS12 (keystore) with Zowe generated certificates”, without any problems.
We also configured Zowe using scenario 3 “z/OS Keyring with Zowe generated certificates”, and after manually adding to the keyring (used as keystore and truststore) the CA Intermediate and CA-Root who signed the z/OSMF certificate, everything worked correctly.
The problems began trying to use in Zowe a certificate signed by our internal PKI, with CA Intermediate and CA Root (the same as z/OSMF). We configured Zowe using zowe.yaml scenario 4 “z/OS Keyring and connect to existing certificate”. All the other zowe.yaml parameters except certificate parameters are the same in scenario 1, 3 and 4.
We are using a RACF keyring with Zowe certificate, CA Intermediate and CA Root.
With this configuration, we got the following error message:
ZWEAG108E z/OSMF instance 'zosmf' not found or incorrectly configured. Gateway is shutting down.
We solved this initial problem setting to DISABLED the “verifyCertificates” parameter in zowe.yaml. Notice that we got the same message using STRICT and NONSTRICT values, so the problem was validating if the certificate is trusted in truststore.
After that change Zowe started and we validated API ML using https://domain:port
We installed Zowe 2.12 in z/OS 2.5 several months ago, and configured using zowe.yaml scenario 1 “PKCS12 (keystore) with Zowe generated certificates”, without any problems.
We also configured Zowe using scenario 3 “z/OS Keyring with Zowe generated certificates”, and after manually adding to the keyring (used as keystore and truststore) the CA Intermediate and CA-Root who signed the z/OSMF certificate, everything worked correctly.
The problems began trying to use in Zowe a certificate signed by our internal PKI, with CA Intermediate and CA Root (the same as z/OSMF). We configured Zowe using zowe.yaml scenario 4 “z/OS Keyring and connect to existing certificate”. All the other zowe.yaml parameters except certificate parameters are the same in scenario 1, 3 and 4.
We are using a RACF keyring with Zowe certificate, CA Intermediate and CA Root.
With this configuration, we got the following error message:
ZWEAG108E z/OSMF instance 'zosmf' not found or incorrectly configured. Gateway is shutting down.
We solved this initial problem setting to DISABLED the “verifyCertificates” parameter in zowe.yaml. Notice that we got the same message using STRICT and NONSTRICT values, so the problem was validating if the certificate is trusted in truststore.
After that change Zowe started and we validated API ML using https://domain:port
But we have problems trying to access Desktop using https://domain:port/zlux/ui/v1/
We are getting the following messages in Zowe joblog:
We think that the problem is around certificates, but we are not able to found what is wrong.
Maybe Zowe cannot work with two CAs?
The text was updated successfully, but these errors were encountered: