Diagnosing the problemĪ Connect:Direct trace with DEBUG=8C00006E may show additional information as in this example. System SSL: Modify code or System SSL application configurations to enable null encryption, RSA-Export, or RC4 ciphers provides more details on this change. If you upgraded to z/OS 2.2 this may also occur.Ĭipher codes 00 – 06 (00000 – 0006) were removed by this APAR. This APAR removed 7 ciphers that were previously available. Recent z/OS maintenance or upgrade was applied.Ĭheck to see if z/OS APAR OA47405 has been recently applied. ![]() These messages may also been seen, but they do not indicate the specific cause:ĬSPA003E Security Violation - SNODE authentication errorĬSPA004E Security Violation - PNODE authentication errorĬSPA202E SSL handshake failure, reason=Socket closed by remote partnerĬiphers selected in the Secure Plus PARMFILE are not available on the z/OS SSL subsystem. ![]() This message specifically indicates that invalid Ciphers have been selected:ĬSPA202E SSL handshake failure, reason=GSK_ERR_BAD_V3_CIPHER This may be seen after applying z/OS maintenance. SymptomĬonnect:Direct Secure Plus connections fail with GSK_ERR_BAD_V3_CIPHER. IBM Sterling Connect:Direct for z/OS Secure Plus receiving error 'CSPA202E SSL handshake failure, reason=GSK_ERR_BAD_V3_CIPHER'.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |