Zowe V3.3 installation

[krasen11]

Hello,

We are installing Zowe V3.3 on the same system where Zowe V2.18 is running and we would like to use both versions concurrently.
For Zowe V3.3 we set the same certificates like in Zowe V2.18 but it is complaining that Certificate EKU is missing Client Auth:

ZWED:50332478 ZWESLSTT CRITICAL (_zsf.verify,certificateChecker.js:134) Error: Certificate EKU missing Client Auth 1.3.6.1.5.5.7.3.2 attribute.

Is there a way to bypass this chek in Zowe V3.3(Zowe V2.18 is working perfectly fine with it)?
Thanks in advance.

[1000TurquoisePogs]

I checked the code and it looks like this may incorrectly trigger when zowe.verifyCertificates = DISABLED
If zowe.verifyCertificates is anything other than DISABLED, this output is correct about you not meeting requirements of Zowe and that things are going to break.

When zowe.verifyCertificates = DISABLED, you're signaling to the servers to just ignore that the certificates are invalid and not check security fully.

So, v2 may be working but I wouldn't use DISABLED in production. It's there for testing and troubleshooting and the best thing to do is to get the check to pass by using a certificate with valid EKU.

If you need to disable this check in v3, the code appears to respect ZWED_SKIP_VALIDATE_CERT="true"
which you could set in the zowe YAML as:

zowe:
  environments:
    ZWED_SKIP_VALIDATE_CERT: "true"

Current plan is for zowe v3.5.0 we'll have a new certificate check process so this issue about the check triggering even when zowe.verifyCertificates=DISABLED will be resolved.