Unable to logon to Zowe 2.18 desktop after making certificate change

[bobbydixon]

Describe the bug
A clear and concise description of what the bug or error is.

Client changed their zowe certificate, and can no longer logon to the Zowe desktop.

Steps to Reproduce

1. Change the name of the Zowe certificate
2. Save the change in RACF, carried out a RACF refresh,
3. Recycled Zowe and z/OSMF

Expected behavior
A clear and concise description of what you expected to happen.

They used to be able to logon to the Zowe desktop.

Screenshots
If applicable, add screenshots to help explain your problem.

The client sees the following red message when they try to logon to the Zowe desktop:

Authentication failed for 3 types. Types: ["saf","apiml","zss"]

Logs
If applicable, add server logs collected at the time of your problem.

I see the following error in their ZWESLSTC JOBLOG:

library: 'SSL routines',
reason: 'sslv3 alert certificate unknown',
code: 'ERR_SSL_SSLV3_ALERT_CERTIFICATE_UNKNOWN'

Details

• Version and build number: [e.g. 0.4.4-SNAPSHOT build # 155] - Zowe v2.18
• Prod environment: SYSPLEX, z/OS , RACF

Web Browser Details (if the bug relates to Zowe Desktop usage):

• OS: [e.g. macOS, Windows]
• Browser [e.g. Chrome, Safari]
• Version [e.g. 71.0.3578.98]

REST API client (in case of REST API issue):

• Technology: [e.g. Spring Boot, Node.js, Postman]
• OS: [e.g. Windows 10]

Shell Environment Details (if the bug relates to CLI):

• Technology: [e.g. zsh, cygwin, cmd, powershell, bash]
• OS: [e.g. MacOS 10.13, Windows 10, Ubuntu 16.04 LTS]

Additional context
Add any other context about the problem here.

I have confirmed with our RACF team that the certificates now match what's in the clients zowe.yaml file, so I believe that rules that out, imho

I confirmed with the client they do NOT have the the z/OSMF APAR PH66874 installed that's mentioned in our technote - https://www.ibm.com/support/pages/node/7259539