Ansicht
Dokumentation

CPDBC8C - SSL record contained a bad message authentication code. ( OS/400 )

BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.


Message : CPDBC8C
SSL record contained a bad message authentication code.

Message Long Text :

Cause . . . . . : The sent or received record failed authentication. A Secure Sockets Layer (SSL) record was received from a peer or sent from this application, that had a message authentication code (MAC) which is not valid. This could be due to the failure to establish a session key during handshake processing because of a bad certificate or associated private key, or if the error occurs during the reading and writing of application data, then your session may have been attacked or there is a problem in one of the end point SSL implementations.
Recovery . . . : If this error occurs during SSL handshake processing then check the certificate and private key on both end points to ensure they are valid. If the problem occurs consistently, then this might be a problem with the SSL implementation at one of the end points. If the problem occurs intermittently, then the error could have been caused by an attack of that session. If the error occurs during read or write processing, attempt to connect to the server using a different SSL enabled client or different SSL enabled client application. If the other client can successfully connect using SSL, then try to connect from the original SSL enabled client or application again. If the original client cannot connect then the problem is most likely associated with that original client or application. Investigate any known sources of information for that client or application. For example, do a search on the Internet for SSL problems associated with the client application. If the original client can connect via SSL, then it is possible that the original SSL session had been attacked. There is no way to clearly determine if the SSL session had been attacked. If the alternate client could not connect then the problem is most likely associated with the server end point's SSL implementation or certificate.

Message File : QCPFMSG
Library Message File : QSYS2924


BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by IBM.

Length: 3237 Date: 20240425 Time: 115115     sap01-206 ( 2 ms )