The environment or SSL handle specified on a System SSL function call is not valid.
Call the gsk_environment_open() function to create an environment handle or the gsk_secure_socket_open() function to create an SSL handle.
The System SSL runtime library detected an internal processing error.
Retry the operation. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
The System SSL runtime library is unable to obtain storage for an internal control block.
Increase the storage available to the application and then retry the failing operation.
The SSL handle is in the incorrect state for the requested operation.
Correct the application to request SSL functions in the proper sequence.
The requested key label is not found in the key database, PKCS #12 file, SAF key ring, or z/OS PKCS #11 token. When using a PKCS #12 file, this error can also occur when the file is being processed during the establishment of the SSL/TLS environment when a certificate is encountered where there is no friendly name PKCS #12 attribute and the certificate's subject distinguished name is empty.
Specify a label that exists in the key database, PKCS #12 file, SAF key ring, or z/OS PKCS #11 token. If encountered when establishing an SSL/TLS environment using a PKCS #12 file, verify any certificate that has no subject distinguished name is assigned a PKCS #12 friendly name attribute.
If using RACF key rings, certificates that are marked as not trusted in the RACF
database are not retrieved from the key ring. Ensure that the certificates needed to build the
certificate’s trust chain are available.
If using RACF key rings and the DIGTCERT and DIGTRING classes are RACLIST'ed, issue
the SETROPTS RACLIST (DIGTCERT, DIGTRING) REFRESH command to refresh the profiles to ensure that the
latest changes are available.
If generic profiling checking was enabled for the DIGTCERT class when the
certificate was created or added and its issuer's distinguished name contains any generic characters
(*, & and %), a generic certificate profile was created. This generic profile processing may
cause the certificate not to be read from the key ring. This certificate will need to be removed and
added back after turning off generic profile checking for DIGTCERT class. The SEARCH CLASS(DIGTCERT)
command can be used to determine if the certificate’s profile is generic. A (G) indicates
generic.
The key database, PKCS #12 file, SAF key ring, or z/OS PKCS #11 token does not contain any certificates, or the SSL client application does not have a certificate available when authentication is requested by the server.
Check for available certificates and add the user certificate and any necessary certification authority certificates to the key database, SAF key ring, or z/OS PKCS #11 token if necessary.
If using a PKCS #12 file, ensure that the file contains the necessary certificates.
If using RACF key rings, certificates that are marked as not trusted in the RACF
database are not retrieved from the key ring. Ensure that the certificates needed to build the
certificate’s trust chain are available.
If using RACF key rings and the DIGTCERT and DIGTRING classes are RACLIST'ed, issue the SETROPTS RACLIST (DIGTCERT, DIGTRING) REFRESH command to refresh the profiles to ensure that the latest changes are available. Specify a certificate for the client application to use.
If generic profiling checking was enabled for the DIGTCERT class when the
certificate was created or added and its issuer's distinguished name contains any generic characters
(*, & and %), a generic certificate profile was created. This generic profile processing may
cause the certificate not to be read from the key ring. This certificate will need to be removed and
added back after turning off generic profile checking for DIGTCERT class. The SEARCH CLASS(DIGTCERT)
command can be used to determine if the certificate’s profile is generic. A (G) indicates
generic.
If using RACF key rings, certificates that are marked as not trusted in the RACF
database are not retrieved from the key ring. Ensure that the certificates needed to build the
certificate’s trust chain are available.If generic profiling checking was enabled for the DIGTCERT class when the
certificate was created or added and its issuer's distinguished name contains any generic characters
(*, & and %), a generic certificate profile was created. This generic profile processing may
cause the certificate not to be read from the key ring. This certificate will need to be removed and
added back after turning off generic profile checking for DIGTCERT class. The SEARCH CLASS(DIGTCERT)
command can be used to determine if the certificate’s profile is generic. A (G) indicates
generic.Collect a System SSL trace that contains the error and then contact your service representative if the problem persists.
An error is detected by a cryptographic function. This error might also occur
while running in FIPS mode when negotiating a secure connection in the following cases:If the error occurred while executing in FIPS mode, check that only FIPS key
sizes or elliptic curves are used. If the error occurred during the
establishment of a secure connection in FIPS mode using a triple DES cipher, retry the
connection. If the problem persists, collect a System SSL trace containing the error and then
contact your service representative.
For more information about FIPS key sizes, see System SSL and FIPS 140-2 and see Cipher suite definitions for information about supported ciphers.
An error is detected while processing a certificate field. This error can also occur when a TLS client or server received a message containing a TLS extension that was not correctly formed. The TLS extension data may contain a length field that has an incorrect value.
If using TLS extensions, ensure that the TLS extension data is correct for both the TLS server and client. If the error persists, collect a System SSL trace containing the error and then contact your service representative.
An error is detected while setting up the LDAP environment or retrieving an LDAP directory entry.
Ensure that the LDAP server is running and that there are no network errors. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
An unexpected error is detected by the System SSL run time.
Collect a System SSL trace containing the error and then contact your service representative.
The value of the size field in the structure indicates that the size of the structure is insufficient.
Ensure that the size field in the structure that is being used is initialized to the size of structure.
A gsk_all_cipher_suites structure required by the API was not supplied on the function call.
Ensure that all parameters required by the API are specified on the function call
An error is detected while reading the key database, the PKCS #12 file, or retrieving entries from the SAF key ring or z/OS PKCS #11 token.
If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
The record format for a key database entry is not correct. This error can occur if the name of a request database is provided instead of the name of a key database.
Ensure that the correct database name is used. Collect a System SSL trace containing a dump of the keyfile entry and then contact your service representative if the error persists.
The System SSL run time is unable to decrypt a key database entry. Either the supplied database password is incorrect or the database is damaged.
Ensure that the correct key database password is used. Re-create the database if the error persists.
The key database, SAF key ring, or z/OS PKCS #11 token does not contain any valid certification authority certificates. The SSL run time needs at least one CA or self-signed certificate to perform client authentication.
Add the necessary certificates to the key database, SAF key ring, or z/OS PKCS #11 token and ensure that existing certificates are valid, have not expired, and are marked as trusted certificates.
If using RACF key rings, certificates that are marked as not trusted in the RACF
database are not retrieved from the key ring. Ensure that the certificates needed to build the
certificate’s trust chain are available.
If using RACF key rings and the DIGTCERT and DIGTRING classes are RACLIST'ed, issue the SETROPTS RACLIST (DIGTCERT, DIGTRING) REFRESH command to refresh the profiles to ensure that the latest changes are available.
If generic profiling checking was enabled for the DIGTCERT class when the
certificate was created or added and its issuer's distinguished name contains any generic characters
(*, & and %), a generic certificate profile was created. This generic profile processing may
cause the certificate not to be read from the key ring. This certificate will need to be removed and
added back after turning off generic profile checking for DIGTCERT class. The SEARCH CLASS(DIGTCERT)
command can be used to determine if the certificate’s profile is generic. A (G) indicates
generic.
A password stash file is specified but the SSL run time is unable to read the password from the stash file.
Verify that the password stash file exists and both the file and directory path are accessible to the application. Re-create the password stash file if the error persists.
An error is detected while opening the key database, PKCS #12 file, SAF key ring, or z/OS PKCS #11 token. This error can occur if no name is supplied or the database, PKCS #12 file, key ring, or token does not exist. When using a PKCS #12 file, the file name cannot end with .kdb, .rdb or .sth.
Verify that the key database, PKCS #12 file, SAF key ring, or z/OS PKCS #11 token exists and is accessible by the application. This value is case-sensitive. Ensure that the case is preserved with your request. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
An error is detected while generating a temporary key pair.
Collect a System SSL trace containing the error and then contact your service representative.
The key database password is expired.
Use the gskkyman utility to assign a new password for the key database.
An SSL secure connection operation cannot be completed because of an active request for the connection.
Retry the failing request when the currently active request completed.
The current time is either before the certificate start time or after the certificate end time.
Obtain a new certificate if the certificate is expired or wait until the certificate becomes valid if it is not valid yet.
Using protocol TLS V1.0, TLS V1.1, or TLS V1.2, any specified ephemeral elliptic
curve (ECDHE) cipher suite is ignored if the client and server do not have a supported elliptic
curve in common.The remote partner indicated a handshake failure which is a generic error that is
encountered during the handshake. This can occur for various reasons such as (but not limited to)
the following:Ensure that the client and the server have at least one cipher specification and protocol in common. Verify that specified session identifier is correct, not expired, that the cache is large enough to hold the cached session entry, and that maximum connection has not been reached.
If an ephemeral elliptic curve (ECDHE) cipher is expected to be used, ensure that
the client and server have a supported elliptic curve or group specification in common. The client
provides its list of supported elliptic curves as part of the TLS handshake. If the server does not
support at least one elliptic curve supported by the client, TLS_ECDHE cipher suites cannot be used.
TLS_ECDHE_ECDSA cipher suites cannot be used if the server’s certificate does not match one of the
client’s supported elliptic curves. A z/OS System SSL client specifies the list of supported
elliptic curves through the GSK_CLIENT_ECURVE_LIST setting. An empty client list means all elliptic
curves supported can be used. The FIPS setting may further restrict what elliptic curves can be
used. A z/OS System SSL server specifies the list of supported elliptic curves through the
GSK_SERVER_ALLOWED_KEX_ECURVES setting. See Table 5 for supported
curves or groups.Ensure that the GSK_TLS_CERT_SIG_ALG_PAIRS or GSK_TLS_SIG_ALG_PAIRS setting is
defined to include all of the signature algorithm pairs that are both supported by the local
application and expected from the remote peer.
The required certificate was not received from the communication partner.
Ensure that the remote application is sending the certificate. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
The certificate received from the communication partner is not supported during the negotiated SSL or TLS protocol handshake.
If an ECC certificate is received from the communication partner during a TLS V1.0, TLS V1.1, or
TLS V1.2 handshake, the certificate's elliptic curve must be specified in the GSK_CLIENT_ECURVE_LIST
environment variable or attribute type. System SSL does not support x25519 and
x448 certificates. If the communication partner’s certificate is either x25519 or x448, a different
certificate must be provided.
If a TLS V1.3 handshake is attempted, DSA, Diffie-Hellman, and elliptic curve
x25519 or x448 certificates are not allowed to be received from the communication partner.
There are limitations on the key type and sizes that are allowed for TLS V1.3. See gsk_secure_socket_init()'s usage section for more information. The
communication partner will need to provide a different certificate.
If the problem persists, collect a System SSL trace that contains a dump with the unsupported certificate and then contact your service representative.
An I/O error was reported while the System SSL run time was reading or writing data.
Ensure that there are no network errors. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
The supplied label or the default key is not found in the key database or the certificate is not trusted or the certificate uses algorithms or key sizes that are not supported while executing in FIPS mode. If using a PKCS #12 file as the certificate database, the label is either the certificate's friendly name or the subject's distinguished name.
Supply a valid label or define a default key in the key database or specify a label for a certificate that uses FIPS algorithms or key sizes if executing in FIPS mode. If using a PKCS #12 file, use the gskkyman command line option -dc or -dcv to display the contents of the PKCS #12 file. The friendly name or subject distinguished name values is displayed in the label field.
For more information about FIPS, see System SSL and FIPS 140-2.
If using RACF key rings, certificates that are marked as not trusted in the RACF
database are not retrieved from the key ring. Ensure that the certificates needed to build the
certificate’s trust chain are available.
If using RACF key rings and the DIGTCERT and DIGTRING classes are RACLIST'ed, issue
the SETROPTS RACLIST (DIGTCERT, DIGTRING) REFRESH command to refresh the profiles to ensure that the
latest changes are available.
If generic profiling checking was enabled for the DIGTCERT class when the
certificate was created or added and its issuer's distinguished name contains any generic characters
(*, & and %), a generic certificate profile was created. This generic profile processing may
cause the certificate not to be read from the key ring. This certificate will need to be removed and
added back after turning off generic profile checking for DIGTCERT class. The SEARCH CLASS(DIGTCERT)
command can be used to determine if the certificate’s profile is generic. A (G) indicates
generic.
The System SSL run time is unable to decrypt a keyfile entry. Either the supplied keyfile password is incorrect or the keyfile is damaged.
Ensure that the correct keyfile password is used. Re-create the keyfile if the error persists.
An incorrectly formatted SSL message is received from the communication partner.
Collect a System SSL trace containing a dump of the SSL message and then contact your service representative.
The message authentication code (MAC) for a message is not correct. This indicates that the message was modified during transmission.
Collect a System SSL trace containing a dump of the message and then contact your service representative if the error persists.
The SSL handshake is not successful because of an unsupported protocol or certificate type. This
error can occur if there is no enabled SSL protocol shared by both the client and the server. When
executing in FIPS mode, specifying the SSL V2 or SSL V3 protocol is ignored. When
enabled for TLS V1.3, SSL V2 and SSL V3 are not supported and are ignored.
Ensure that the SSL protocol you want is enabled on both the client and the server. Collect a System SSL trace containing a dump of the failing handshake and then contact your service representative if the problem persists.
The certificate signature is not correct for a certificate received from the communication partner.
Ensure that a valid certificate is being sent by the communication partner. Collect a System SSL trace containing a dump of the incorrect certificate and then contact your service representative if the error persists.
Either the local certificate or the certificate received from the peer is not valid.
Ensure that a valid certificate is being sent by the communication partner. If a TLS V1.3 handshake is being attempted, the communication partner may have sent a DSA certificate, an RSA certificate with signature algorithms MD2, MD5, or SHA-224, a Brainpool certificate, or an ECC certificate with signature algorithms SHA-1 or SHA-224. These certificates are not supported with TLS V1.3. Collect a System SSL trace containing a dump of the incorrect certificate and then contact your service representative if the error persists.
The communication partner violated the SSL protocol by sending a message out of sequence or by omitting a required field from a message.
Collect a System SSL trace and then contact your service representative.
The System SSL run time is unable to access a file or system facility.
Ensure that the application is authorized to access the file or facility.
For key database files, ensure that the application user ID has read access to the file.
For z/OS PKCS #11 tokens, ensure that the application user ID has READ access to resource USER.tokenname in the CRYPTOZ class.
If the error persists, collect a System SSL trace and then contact your service representative.
A self-signed certificate cannot be validated because it is not in the key database, PKCS #12 file, SAF key ring, or z/OS PKCS #11 token.
Add the self-signed certificate to the key database, PKCS #12 file, SAF key ring, or z/OS PKCS #11 token.
If using RACF key rings, certificates that are marked as not trusted in the RACF
database are not retrieved from the key ring. Ensure that the certificates needed to build the
certificate’s trust chain are available.
If using RACF key rings and the DIGTCERT and DIGTRING classes are RACLIST'ed, issue the SETROPTS RACLIST (DIGTCERT, DIGTRING) REFRESH command to refresh the profiles to ensure that the latest changes are available.
If generic profiling checking was enabled for the DIGTCERT class when the
certificate was created or added and its issuer's distinguished name contains any generic characters
(*, & and %), a generic certificate profile was created. This generic profile processing may
cause the certificate not to be read from the key ring. This certificate will need to be removed and
added back after turning off generic profile checking for DIGTCERT class. The SEARCH CLASS(DIGTCERT)
command can be used to determine if the certificate’s profile is generic. A (G) indicates
generic.
The remote partner closed the socket. This error is also reported if the remote partner sent a close notification alert.
None.
The SSL V2 cipher is not valid.
The SSL V3 cipher is not valid.
The System SSL run time is unable to access the LDAP server.
Ensure that the LDAP server is running and that there are no network problems. Collect a System SSL trace and then contact your service representative if the error persists.
The key entry does not contain a private key or the private key is not usable. This error can also occur if the private key is stored in ICSF and ICSF services are not available, if using a SAF key ring that is owned by another user, if the private key size is greater than the supported configuration limit or the application is executing in FIPS mode. Certificates that are meant to represent a server or client must be connected to a SAF key ring with a USAGE value of PERSONAL and either be owned by the user ID of the application or be SITE certificates. This error can occur when using z/OS PKCS #11 tokens if the user ID of the application does not have appropriate access to the CRYPTOZ class. This error can occur when using private keys associated with user certificates in a SAF key ring that is owned by another user if the user ID of the application does not have appropriate access to the ringOwner.ringName.LST resource in the RDATALIB class.
Ensure that the ICSF started task is started before the application if the private key is stored in ICSF. When using z/OS PKCS #11 tokens, ensure that the user ID has appropriate access to the CRYPTOZ class.
If executing in FIPS mode, ensure that the certificate that is being used does not have its private key stored in ICSF.
The received message does not start with a valid SSL V2 header. This error can occur if an SSL V3 client attempts to establish a secure connection with an SSL V2 server.
Enable the SSL V2 protocol on the client and then retry the request.
The certificate is revoked by the certification authority.
Obtain a new certificate.
An attempt to renegotiate the session parameters for an active connection is rejected. This code occurs if renegotiation is disabled, or if the client or server rejects the renegotiation. If using the TLS protocol, and a no renegotiation alert is sent to the peer or received from the peer, then SSL processing continues using the current session parameters. If using the TLS or the SSL V3 protocol, and a handshake failure alert is sent to the peer or received from the peer, then the SSL connection is closed.
If the session parameters are expected to be successfully reset, then the connection must be closed.
The key size that is used for an export cipher suite exceeds the allowable maximum size. For RSA and DSA keys, the maximum export key size is 512 bits. If the certificate key is larger than 512 bits, the SSL run time uses a temporary 512-bit key for the connection.
Collect a System SSL trace and then contact your service representative.
The certificate key is not compatible with the negotiated cipher suite. The negotiated cipher suite is dependent on the type of algorithms used by the server certificate (RSA, DSA, or Diffie-Hellman) and those available for the client to use. This error can also occur if the client certificate uses an algorithm that is incompatible with the server certificate.
Specify a certificate with the appropriate key type.
The key database does not contain a certificate for the certification authority.
Obtain the certificate for the certification authority and add it to the key database. When using a SAF key ring, the CA certificate must be TRUSTed.
If using RACF key rings, certificates that are marked as not trusted in the RACF
database are not retrieved from the key ring. Ensure that the certificates needed to build the
certificate’s trust chain are available.
If using RACF key rings and the DIGTCERT and DIGTRING classes are RACLIST'ed, issue the SETROPTS RACLIST (DIGTCERT, DIGTRING) REFRESH command to refresh the profiles to ensure that the latest changes are available.
If generic profiling checking was enabled for the DIGTCERT class when the
certificate was created or added and its issuer's distinguished name contains any generic characters
(*, & and %), a generic certificate profile was created. This generic profile processing may
cause the certificate not to be read from the key ring. This certificate will need to be removed and
added back after turning off generic profile checking for DIGTCERT class. The SEARCH CLASS(DIGTCERT)
command can be used to determine if the certificate’s profile is generic. A (G) indicates
generic.
The required certificate revocation list (CRL) cannot be found in the specified LDAP server when the gsk_crl_security_level is set to MEDIUM or HIGH or the CRL cannot be found in the HTTP server indicated in the CRL distribution points extension and the GSK_REVOCATION_SECURITY_LEVEL is set to MEDIUM or HIGH.
If contacting an LDAP server to retrieve the CRL, verify that the CRL is present in the LDAP entry being searched and is valid. Verify that the certificate's issuer is the same as the CRL issuer. Contact the certification authority and obtain the required CRL.
If contacting an HTTP server to retrieve the CRL, verify that the CRL is present on the HTTP server. Contact the HTTP server administrator to verify that the CRL is present on the server. If there are crlIssuers present in the CRL distribution point extension, verify that there is at least one match between those and the CRL issuer. If a match cannot be found in the crlIssuers in the CRL distribution point extension or there are no crlIssuers present, verify that the certificate's issuer is the same as the CRL issuer. The HTTP server administrator may need to contact the certification authority to obtain the required CRL.
Collect a System SSL trace containing the error and then contact your service representative if the problem persists.
For gsk_secure_socket_read(), a close notification is received from the peer application. For gsk_secure_socket_write(), a close notification is sent to the peer application. A close notification is sent when the gsk_secure_socket_shutdown() routine is called or when a close notification is received from the peer application. Additional data may not be sent by the application after the close notification is sent to the peer application.
None
The peer application detected an internal error while performing an SSL operation and sent an alert to close the secure connection.
Check the error log for the remote application to determine the nature of the processing error.
The peer application sent an alert message that is not recognized by the System SSL run time.
Collect a System SSL trace and then contact your service representative.
Specify a certificate with the appropriate key usage.
If the gskkyman utility was used to create either the client (user) or server end-entity certificate, ensure that the appropriate option was selected from the Certificate Usage menu to create a client (user) or server certificate. The Certificate Usage menu consists of options for creating certificate authority and client (user) / server end-entity certificates.
The server requires the client to send its certificate during the TLS handshake, but a certificate was not received.
Verify that the client has access to a valid certificate that can be sent to the server.
Access of certificate/key from label could not be resolved because multiple certificates/keys exist with the label.
Correct certificate/key store so that label specifies a unique record.
If using a PKCS #12 file, use the gskkyman command line option -dc or -dcv to display the contents of the PKCS #12 file. The friendly name or subject distinguished name value is displayed as the label. Ensure the specified label is unique in the PKCS #12 file.
Access of key from default status could not be resolved because multiple keys are marked as the default key.
Correct the certificate/key store so that only one key is marked as the default key.
The SSL/TLS handshake encountered an error while generating random bytes.
Retry the secure connection. Contact your service representative if the error persists.
While executing in FIPS mode, an attempt was made to open a key database that does not meet FIPS criteria.
Specify a key database that meets FIPS criteria if running in FIPS mode.
The TLS client received a message from the TLS server containing a TLS extension that was not requested. The TLS server must only respond to an extension that was sent by the TLS client.
Ensure that the TLS server is operating correctly. If the problem persists, collect a System SSL trace and contact your service representative.
The TLS server or client encountered a communicating partner that does not support a TLS extension that is defined as required.
Ensure that the TLS extension data is correctly defined, and that both the TLS server and client support the required extension. If the problem persists collect a System SSL trace and contact your service representative.
The TLS server is unable to match the server names that are supplied in a "Server Name Indication" type TLS extension, and either the TLS server or TLS client determined this scenario to be fatal.
Ensure that the TLS extension data is correct for both the TLS server and client.
The TLS server received a Maximum Fragment Length TLS extension request from the TLS client that specifies an unsupported maximum fragment length. Supported maximum fragment lengths are 512 bytes, 1024 bytes, 2048 bytes, and 4096 bytes.
Ensure that the TLS extension data is correct for the TLS server and the communicating partner. If the problem persists collect a System SSL trace and contact your service representative.
The TLS client or server received a message containing a TLS extension that was not correctly formed. The TLS extension data contains a length field that has an incorrect value.
Ensure that the TLS extension data is correct for both the TLS server and client. If the problem persists collect a System SSL trace and contact your service representative.
The EC domain parameters that are defined for the elliptic curve public or private key are not supported.
Ensure the elliptic curve public/private key pair uses a supported elliptic curve. See Using cryptographic features with System SSL for the list of elliptic curves that are supported by System SSL.
A gsk_buffer structure containing the EC domain parameters was not supplied on the call.
Supply a gsk_buffer structure containing the EC domain parameters on the function call.
A gsk_buffer structure containing the signature was not supplied on the call.
Supply a gsk_buffer structure containing the signature on the function call.
The EC domain parameters that are defined for the elliptic curve public or private key are not valid. Either no parameters could be found or the parameters could not be successfully decoded.
Ensure the elliptic curve public/private key pair uses a valid elliptic curve.
A cryptographic process cannot be completed because of ICSF callable services being unavailable. This error might also occur when attempting to use a cipher suite that uses ICSF to perform a United States only encryption algorithm (such as AES-GCM) when ICSF is only able to use US export restricted encryption algorithms.
Ensure that ICSF is running and operating correctly. If ICSF is running correctly, ensure that ICSF is able to use United States only encryption algorithms.
An ICSF callable service that is employed to facilitate a cryptographic process returned an error condition. This error can occur if the user ID of the application does not have appropriate access to the RACF CSFSERV class resource profiles.
While running in FIPS mode, an attempt was made to use ICSF PKCS #11 services, which were not operating in FIPS mode.
Ensure that ICSF is configured to run in FIPS mode.
The SSL V3 4-character cipher is not valid.
The EC domain parameters that are defined for the elliptic curve public or private key are not approved in FIPS mode.
Ensure the elliptic curve for the public or private key is valid in FIPS mode. See System SSL and FIPS 140-2 for a list of elliptic curves that are supported by System SSL when running in FIPS mode.
TLS Renegotiation Indication was not received on the initial handshake with peer as required by the GSK_EXTENDED_RENEGOTIATION_INDICATOR environment variable or the gsk_attribute_set_enum enumeration ID GSK_EXTENDED_RENEGOTIATION_INDICATOR. If a server receives this code, then the GSK_EXTENDED_RENEGOTIATION_INDICATOR is set to either SERVER or BOTH and the client did not signal TLS Renegotiation Indication on the initial client hello. If a client receives this code, then the GSK_EXTENDED_RENEGOTIATION_INDICATOR is set to either CLIENT or BOTH and the server did not signal TLS Renegotiation Indication on the initial server hello.
Ensure that the peer is configured to signal TLS Renegotiation Indication. If the peer does not support TLS Renegotiation Indication, and connection is required, then adjust the local setting of the environment variable GSK_EXTENDED_RENEGOTIATION_INDICATOR to “OPTIONAL” or the gsk_attribute_set_enum enumeration ID GSK_EXTENDED_RENEGOTIATION_INDICATOR to GSK_EXTENDED_RENEGOTIATION_INDICATOR_ OPTIONAL.
The server key exchange message contains an elliptic curve parameter format or named curve specification that is not supported
For ephemeral ECDH cipher suites, ensure that only the named curve EC domain parameter format is used in the server key exchange message, with a named curve that is supported by System SSL.
The elliptic curve public value is specified using an EC point format that is not supported.
Ensure the elliptic curve public value is specified using a supported EC point format. System SSL supports only the uncompressed EC points format.
A call requiring cryptographic hardware was made to ICSF. The current installation hardware does not support the service or algorithm that is being used.
Ensure that the correct protocol is in use for your installation, and that the cryptographic hardware required for this service or algorithm is available to ICSF.
The supported elliptic curve list is not formatted correctly or when running in
FIPS mode, the removal of unsupported elliptic curves resulted in an empty list.
GSK_CLIENT_ECURVE_LIST or
GSK_SERVER_ALLOWED_KEX_ECURVES contains only entries for elliptic curves that are supported by
System SSL. See Table 5 for a list of supported elliptic curve
definitions. Ensure that each entry uses 4 decimal digits.If enabled for FIPS mode, elliptic curves x25519 and x448 are not supported. The specified list may also be tailored to meet the requirements of the FIPS level being utilized. For information about FIPS mode level support, see System SSL and FIPS 140-2.
An attempt was made to use ICSF PKCS #11 services, which are disabled because of an ICSF FIPS self-test failure.
Stop and restart ICSF. System SSL might need restarting to regain the full hardware benefit from ICSF. Contact your service representative if the error persists.
The supported signature algorithm pairs list is not correctly formatted.
A signature algorithm that is used to sign a local or peer certificate is not included in the signature algorithm pairs list or the certificate signature algorithm pairs list. The server certificate chain must use signature algorithms included in the signature algorithm pairs or the certificate signature algorithm pairs that are presented by the client during the TLS handshake. The client certificate chain must use signature algorithms included in the signature algorithm pairs or the certificate signature algorithm pairs that are presented by the server during the TLS handshake. If remote partner specifies the signature algorithm pairs and the certificate signature algorithm pairs, the specified certificate signature algorithm pairs take precedence over the signature algorithm pairs. For TLS V1.2 handshakes, the GSK_TLS_CERT_SIG_ALG_PAIRS setting is only used on the client side to indicate the signature algorithms that the client supports in the server’s certificate chain.
The certificate key algorithm of the local certificate cannot be used to generate digital signatures as it is not included in the signature algorithm pairs list. The server certificate must use a key algorithm included in the signature algorithm pairs list that is presented by the client during the TLS handshake and the server's supported signature algorithm pairs list. The client certificate must use a key algorithm included in the signature algorithm pairs list that is presented by the server during the TLS handshake and the client's supported signature algorithm pairs list.
One or more PKCS #11 attributes or parameters for a key are missing or incorrect for a requested function that is being performed. For example, a signing operation requires that for the key that is being used, the PKCS #11 sign attribute is to be TRUE. Verify that the correct key is being used for the requested function, and that all required attributes are set for that key. If you are using gsk_make_enveloped_private_key_msg(), ensure that a recipient certificate's RSA public key is valid.
Verify that a certificate's PKCS #11 key attributes are correct for the function that is being performed.
The certificate in use does not meet the requirements for the Suite B profile that is selected for the environment.
Ensure that the certificate used for the connection satisfies the requirements for the chosen Suite B profile. See Suite B cryptography support for more information about Suite B certificate requirements.
A handshake attempted to perform an ECDH key exchange. The certificate's private key is a label that is pointing to a secure key. This is not a supported operation.
Choose a certificate that does not have a secure private key or a cipher that does not perform an ECDH key exchange.
Unable to generate clear keys or PKCS #11 objects because of the caller's RACF access to CRYPTOZ class resource CLEARKEY.SYSTOK-SESSION-ONLY does not allow the generation of non-secure (clear) PKCS #11 keys.
Ensure that the user ID of the application has appropriate access to the RACF CRYPTOZ class resource CLEARKEY.SYSTOK-SESSION-ONLY.
The OCSP responder contacted for certificate validation requires that all OCSP requests be signed.
Enable OCSP request signing by specifying the label of the signing certificate (GSK_OCSP_REQUEST_SIGKEYLABEL) and the signature algorithm (GSK_OCSP_REQUEST_SIGALG).
The HTTP response received was not properly formatted or contents are not valid. The HTTP response received must be an HTTP/1.0 or HTTP/1.1 response.
Ensure that the HTTP server is running, that there are no network errors, and the HTTP server sends its responses using HTTP/1.0 or HTTP/1.1 protocols. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
The OCSP ASN.1 encoded response received from the OCSP responder was not properly formatted or its contents are not valid.
Ensure that the OCSP responder server is properly encoding the OCSP response, that it is running, and that there are no network errors. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
For a client application, the session identifier or a session ticket specified by GSK_PEER_ID does not exist or has expired. If a client application has set GSK_REQ_CACHE_SESSION to ON, the required cached session entry could not be located. For a client application, the maximum number of SSL environment connections has been reached by a client application so new GSK_PEER_IDs cannot be stored in the session cache.
For a server application, the session identifier specified by GSK_SID_VALUE does not exist or has expired. If a server application has set GSK_SID_VALUE, the required cached session entry could not be located when the session is using an SSL V3 through TLS V1.2 handshake or the session ticket sent by the client does not contain the correct session identifier while attempting a TLS V1.3 handshake resumption.
Verify that the specified session identifier is correct, is not expired, the cache is large enough to hold the cached session entry, and the maximum client connections has not been reached.
For SSL V3 through TLS V1.2 handshakes, the server failed the connection request because the session identifier provided by the client through the client hello does not match the server GSK_SID_VALUE that was specified by gsk_attribute_set_buffer().
or ticket identifier in the session ticket through the
client hello does not match the server GSK_SID_VALUE that was specified by
gsk_attribute_set_buffer().If sysplex session ticket caching is not enabled
(GSK_SYSPLEX_SESSION_TICKET_CACHE option is set to OFF), the server is unable to decrypt the
session ticket because the encryption key is not available.Verify that the specified session identifier is correct.
If attempting to resume a TLS V1.3 connection, ensure that the
GSK_SESSION_TICKET_SERVER_TIMEOUT and GSK_SESSION_TICKET_SERVER_KEY_REFRESH settings are appropriate
to allow for the session ticket sent from the client to be used. The
GSK_SESSION_TICKET_SERVER_KEY_REFRESH setting is only relevant when sysplex session ticket caching
is not enabled and GSK_SESSION_TICKET_SERVER_ENABLE is set to ON. If the session ticket is
expired or the key used to encrypt the session ticket is not available, session reuse will fail.
Client application attributes GSK_ENABLE_CLIENT_SET_PEERID, GSK_REQ_CACHED_SESSION, GSK_V3_SIDCACHE_SIZE, GSK_V3_SESSION_TIMEOUT, and GSK_SESSION_TICKET_CLIENT_ENABLE conflict.
Verify that the settings for GSK_ENABLE_CLIENT_SET_PEERID, GSK_REQ_CACHED_SESSION, GSK_V3_SIDCACHE_SIZE, GSK_V3_SESSION_TIMEOUT, and GSK_SESSION_TICKET_CLIENT_ENABLE are in agreement.
Attribute conflicts may cause the application to not behave as desired and may result in handshake failures. SID cache reuse requires that the cache be defined and active.
A user-supplied GSK_SID_VALUE was encountered that is not valid in the gsk_secure_socket_init() routine.
An application should only set GSK_SID_VALUE for a new connection if cache reuse is desired. The System SSL generated value can only be retrieved from SSL using gsk_attribute_get_buffer(). The buffer that is returned belongs to an active System SSL connection and should not be modified or the storage freed by the application. If the connection that provided the GSK_SID_VALUE buffer has closed, the data pointed to by the buffer cannot be determined. An application must copy this data into the application's own storage in order to continue reusing a particular cached session prior to closing the originating connection.
A user-supplied GSK_PEER_ID was encountered that is not valid in the gsk_secure_socket_init() routine.
An application should only set GSK_PEER_ID for a new connection if cache reuse is desired. The System SSL generated value can only be retrieved from SSL using gsk_attribute_get_buffer(). The buffer that is returned belongs to an active System SSL connection and should not be modified or the storage freed by the application. If the connection that provided the GSK_PEER_ID buffer has closed, the data pointed to by the buffer cannot be determined. An application must copy this data into the application's own storage in order to continue reusing a particular cached session.
The OCSP responder contacted for certificate validation returned an internal error.
Ensure that the OCSP responder server is running and that there are no network errors. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
The current time is after the OCSP response expiration time.
If using the dedicated OCSP responder, ensure that the OCSP responder server is using the most recent revocation information available from the certification authority. If certificate revocation through the AIA extension is enabled, ensure that the OCSP responder servers referenced in the certificate chain are using the most recent revocation information available. Collect a System SSL trace containing the error and then contact your service representative if the error persists.
An internal error was encountered while creating the OCSP request to send to an OCSP responder.
If OCSP request signing is enabled, verify that the signing certificate resides in the SAF key ring, SSL key database, PKCS#11 token, or PKCS#12 file and the signing certificate is valid (start time is before the current time and is not yet expired) and contains a private key. The key repository is provided through the GSK_KEYRING_FILE environment variable or attribute. The OCSP signing certificate is provided through the GSK_OCSP_REQUEST_SIGKEYLABEL environment variable or attribute.
Collect a System SSL trace containing the error and then contact your service representative if the error persists.
When attempting to retrieve revocation information, the HTTP response exceeded the maximum configured response size for either an OCSP response or a HTTP CRL. The response size is provided through either GSK_HTTP_CDP_MAX_RESPONSE_SIZE or GSK_OCSP_MAX_RESPONSE_SIZE environment variables or attributes.
Ensure that the HTTP response maximum size is adequate for the size of the CRLs or OCSP responses that are being retrieved. If necessary, increase the maximum response size until an adequate size is provided to handle the CRLs or OCSP responses that are being retrieved. If unable to determine an adequate size, collect a System SSL trace containing the error and then contact your service representative.
Unable to establish a connection to contact the HTTP server or the OCSP responder to retrieve certificate revocation information.
If enabled for OCSP and a dedicated OCSP responder is enabled, ensure that the responder is running and can be accessed.
If enabled for OCSP responders identified in the certificate AIA extension, ensure that the OCSP responders specified in the extension are running and can be accessed.
If HTTP CRL support is enabled, ensure that the HTTP server specified in the CRL Distribution Point extension is running and can be accessed.
If there is a firewall in place and either an HTTP proxy server or port or an OCSP proxy server or port has been identified, ensure that the servers and ports settings are correct and the servers can be accessed. The HTTP proxy server and port are specified through the GSK_HTTP_CDP_PROXY_SERVER_NAME and GSK_HTTP_CDP_PROXY_SERVER_PORT attributes or environment variables. The OCSP proxy server and port are specified through the GSK_OCSP_PROXY_SERVER_NAME and GSK_OCSP_PROXY_SERVER_PORT attributes or environment variables.
Collect a System SSL trace containing the error and then contact your service representative if the error persists.
When validating the nonce in the OCSP response, the value did not match the value sent in the OCSP request.
If OCSP is enabled for the dedicated OCSP responder (GSK_OCSP_URL), ensure that the OCSP responder server is configured to send a nonce in OCSP responses.
Ensure that nonce checking is required. If not required, set GSK_OCSP_NONCE_CHECK_ENABLE to off.
Collect a System SSL trace containing the error and then contact your service representative if the error persists.
The time limit indicated in the value for GSK_OCSP_RESPONSE_TIMEOUT has been exceeded.
Ensure that the HTTP server where the OCSP responder resides is available and able to process OCSP requests. Verify that the value for GSK_OCSP_RESPONSE_TIMEOUT is sufficient to receive a complete response from the HTTP server containing the OCSP responder.
The current time is earlier than the validity period of the revocation information provided though either an OCSP response or CRL.
Ensure that the system time is configured correctly. Collect a System SSL trace containing the error and then contact your service representative if the problem persists.
The URI value in the AIA extension or the CDP extension is not in the correct format or cannot be resolved by the Domain Name Service (DNS). The correct URI format is http://hostname[:portNumber].
If the GSK_OCSP_ENABLE parameter is enabled, verify that the certificate being verified has a URI value in the AIA extension that is properly formatted and can be resolved by the DNS. It may be necessary to obtain a new certificate or to specify the GSK_OCSP_PROXY_SERVER_NAME and GSK_OCSP_PROXY_SERVER_PORT parameters if there is a need to pass through a firewall. If the GSK_OCSP_URL or GSK_OCSP_PROXY_SERVER_NAME parameters are specified, verify that the host name and the IP address is properly formatted and can be resolved by the DNS.
If the GSK_HTTP_CDP_ENABLE parameter is enabled, verify that the certificate being verified has a URI value in the CDP extension that is properly formatted and can be resolved by the DNS. It may be necessary to obtain a new certificate or to specify the GSK_HTTP_CDP_PROXY_SERVER_NAME and GSK_HTTP_CDP_PROXY_SERVER_PORT parameters if there is a need to pass through a firewall.
When processing the PKCS #12 file, a format error was detected. This can occur if the file is not properly ASN.1 encoded, been modified if transferred, or the PKCS #12 file is not a Version 3 binary file. PKCS #12 Version 1 files and files in Base64 format are not supported.
If the current file is either a PKCS #12 Version 1 file or a Base64 encoded file, it must be replaced with a PKCS #12 Version 3 file. If transferring the file, be sure to transfer the file in binary format. Correct the PKCS #12 file or obtain a new PKCS #12 file. If the problem persists, collect a System SSL Trace containing the error and then contact your service representative.
During the establishment of an SSL/TLS secure connection (gsk_secure_socket_init() or gsk_secure_soc_init() API) with certificate validation processing set to mode ANY or 2459, an intermediate CA certificate was encountered outside of a trusted certificate source (for example, key database file, PKCS #12 file, SAF key ring, or PKCS #11 token), which does not have a basic constraints extension.
Contact the connection partner to determine the certificates being utilized. Once the certificates are identified, either new valid Version 3 certificates can be obtained to replace the intermediate CA certificate or certificates causing the error, or if the usage of the intermediate CA certificates is deemed to be acceptable, a version of the CA certificate or certificates needs to be added to the application's trusted certificate source (for example, key database file, PKCS #12 file, SAF key ring, or PKCS #11 token).
If the error persists after adding the certificates, or if the certificates can not be readily obtained, collect a System SSL trace containing the error and then contact your service representative.
The number of locations allowed by either GSK_MAX_SOURCE_REV_EXT_LOC_VALUES or GSK_MAX_VALIDATION_REV_EXT_LOC_VALUES has been exceeded. The locations for revocation information are specified by the accessLocation in the AIA certificate extension for OCSP and the distributionPoint in the CDP extension for HTTP CRLs.
Use the values in the certificate chain being validated to determine the proper value for GSK_MAX_SOURCE_REV_EXT_LOC_VALUES, GSK_MAX_VALIDATION_REV_EXT_LOC_VALUES, or both. The value for GSK_MAX_SOURCE_REV_EXT_LOC_VALUES must be greater than or equal to the maximum number of location values in a CDP or AIA extension used in the certificate chain being validated. The value for GSK_MAX_VALIDATION_REV_EXT_LOC_VALUES must be greater than or equal to the total number of location values in all CDP and AIA extensions used in the certificate chain being validated. Collect a System SSL trace containing the error and then contact your service representative if the problem persists.
The time limit indicated in the value for GSK_HTTP_CDP_RESPONSE_TIMEOUT has been exceeded.
Ensure that the HTTP server is available and able to process HTTP CRL requests. Verify that the value for GSK_HTTP_CDP_RESPONSE_TIMEOUT is sufficient to receive a complete response from the HTTP server
The time limit indicated in the value for GSK_LDAP_RESPONSE_TIMEOUT has been exceeded.
Ensure that the LDAP server is available and able to process LDAP CRL requests. Verify that the value for GSK_LDAP_RESPONSE_TIMEOUT is sufficient to receive a complete response from the LDAP server.
The OCSP responder is unable to currently process the OCSP request.
Contact the OCSP responder administrator to verify that the OCSP responder is working properly. Then retry the OCSP request at a later time.
The OCSP response was signed with an algorithm that was not specified in the OCSP response signature algorithm pairs list.
Correct the OCSP request signing algorithm that is specified in the GSK_OCSP_REQUEST_SIGALG environment variable or attribute type in gsk_attribute_set_buffer().
The OCSP response from the OCSP responder does not contain the requested certificate status.
Contact the OCSP responder administrator to verify that the OCSP responder is operating as expected. If the error persists, collect a System SSL trace containing the error and then contact your service representative.
The OCSP response from the OCSP responder contains duplicate certificate statuses and it is not possible to determine revocation status of the requested certificate.
Contact the OCSP responder administrator to verify that the OCSP responder is operating as expected. If the error persists, collect a System SSL trace containing the error and then contact your service representative.
During the negotiation of a secure connection utilizing a triple DES cipher with unique key enforcement enabled, the generated triple DES key did not meet the requirement of each key part being unique. The three key parts are checked for uniqueness in a non-FIPS mode environment when attribute GSK_3DES_KEYCHECK has been set to GSK_3DES_KEYCHECK_ON. Triple DES key part uniqueness checking always takes place in FIPS mode.
Try the connection again.
The socket buffer or buffer size is not valid.
Specify a valid buffer and buffer size.
The socket is in non-blocking mode and the socket request returned the EWOULDBLOCK error.
Retry the gsk_secure_socket_read() or gsk_secure_socket_write() request when the socket is ready to send or receive data.
A socket read request that is issued as part of an SSL handshake returned the EWOULDBLOCK error.
Retry the failing request when the socket is ready to receive data.
A socket write request that is issued as part of an SSL handshake return the EWOULDBLOCK error.
Retry the failing request when the socket is ready to send data.
An SSL protocol record has a plain text record length greater than 16384 or an encrypted text record length greater than 18432.
Ensure that data is not being corrupted during transmission. Obtain a System SSL trace containing a dump of the failing record and contact your service representative if the error persists.
An X.509 end-entity certificate being utilized by the peer did not meet the minimum allowed System SSL X.509 certificate version.
Ensure that the peer’s certificate version is at least equal to the minimum
supported version. The minimum version value can be modified using GSK_PEER_CERT_MIN_VERSION. If a
TLS V1.3 connection is being negotiated, the certificate must be version 3.
During the negotiation of a secure connection, the peer's X.509 end-entity certificate contains a RSA, DSA, DH, or ECC key that is smaller than the minimum size allowed.
Ensure that the key sizes are at least equal to the minimum supported key sizes. The minimum key size value can be modified using attributes GSK_PEER_RSA_MIN_KEY_SIZE, GSK_PEER_DSA_MIN_KEY_SIZE, GSK_PEER_DH_MIN_KEY_SIZE, and GSK_PEER_ECC_MIN_KEY_SIZE.
Ensure that the key label list is valid.
When using the attribute GSK_SERVER_KEYRING_LABEL_LIST, none of the certificates supported the protocol, ciphers (TLS V1.2 and earlier), or the session attributes defined for an SSL connection. Certificates that are either expired or not yet valid are ignored.
Ensure that at least one of the certificates defined by attribute GSK_SERVER_KEYRING_LABEL_LIST supports the requested protocol, cipher (TLS V1.2 and earlier), and session attributes of an SSL connection. Collect a System SSL trace containing the error and contact your service representative if the error persists.
OCSP stapling on the System SSL server application requires either the GSK_OCSP_URL to be specified or the GSK_OCSP_ENABLE option to be set to ON.
Ensure that GSK_OCSP_URL is specified or the GSK_OCSP_ENABLE option is set to ON when OCSP stapling on the server is enabled. Otherwise, turn off OCSP stapling by setting the GSK_SERVER_OCSP_STAPLING environment variable to OFF or by calling the gsk_attribute_set_enum() routine with the GSK_SERVER_OCSP_STAPLING attribute type set to GSK_SERVER_OCSP_STAPLING_OFF.
System SSL is configured for server OCSP stapling. If the negotiated protocol is TLS V1.2 and earlier, the TLS server has sent a CERTIFICATE-STATUS response message that the TLS client does not understand. If the negotiated protocol is TLS V1.3, the TLS server has sent a Certificate Status Request extension containing the OCSP response that the TLS client does not understand. The TLS handshake is aborted.
If the negotiated protocol is TLS V1.2 and earlier, the OCSP responder that System SSL has contacted may have provided an improperly formatted OCSP response that System SSL has included in the CERTIFICATE-STATUS message. Verify that the TLS client is able to handle the OCSP responses that reside in the CERTIFICATE-STATUS message.
If the negotiated protocol is TLS V1.3, the OCSP responder that System SSL has contacted may have provided an improperly formatted OCSP response that System SSL has included in the Certificate Status Request extension. Verify that the TLS client is able to handle the OCSP responses that reside within the Certificate Status Request extension in the server’s CERTIFICATE message.
If the error persists, collect a System SSL trace containing the error and then contact your service representative.
The server is enabled for the Signaling Cipher Suite Value (SCSV) support by setting the GSK_SERVER_FALLBACK_SCSV attribute type on gsk_attribute_set_enum() to GSK_SERVER_FALLBACK_SCSV_ON or the GSK_SERVER_FALLBACK_SCSV environment variable to ON. When the SCSV is present in the client's supported cipher list during a handshake, it indicates that the client is attempting a fallback handshake with an earlier SSL or TLS protocol. If the server's highest supported TLS or SSL protocol level is greater than the client's SSL or TLS protocol level, the handshake fails with this error.
If the server is configured appropriately with the GSK_SERVER_FALLBACK_SCSV attribute type or environment variable enabled, no action is required as the server is appropriately rejecting a client's attempt to do a handshake at an earlier TLS or SSL protocol level.
Ensure that the client is properly enabled for the highest SSL or TLS protocol level supported by the server and retry the initial handshake without sending the SCSV to the server.
The remote partner did not send a required TLS extension during the TLS handshake process. The TLS handshake cannot continue.
Ensure that the remote partner is specifying the required TLS extensions that are required for the secure TLS connection. If a TLS V1.3 handshake is attempted, ensure that the remote partner is including the signature algorithms, key share, and supported groups extensions. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
The specified key share list is not configured or set, not formatted correctly, or contains groups that are not supported by TLS V1.3.
The client and server key share groups do not contain at least one value in common.
Check with the remote partner to determine the key share groups that are to be used and supported by both sides.
If running as a server application, ensure that there is at least one key share group specified in the GSK_SERVER_TLS_KEY_SHARES that is also supported by the remote client partner.
If running as a client application, the remote server partner has selected a key share group that has not been specified in the GSK_CLIENT_TLS_KEY_SHARES list. It may be necessary to update the client’s GSK_CLIENT_TLS_KEY_SHARES and GSK_CLIENT_ECURVE_LIST settings to include the server’s selected key share group. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
On the client side when TLS V1.3 is enabled, System SSL uses the
GSK_CLIENT_ECURVE_LIST setting to specify the elliptic curves or supported groups that are sent to
the server. The GSK_CLIENT_TLS_KEY_SHARES setting specifies the key share groups and it must contain
at least one of the groups in the GSK_CLIENT_ECURVE_LIST setting.
On the server side, System SSL has selected TLS V1.3 for the handshake
and has determined that the client has sent the elliptic curves or supported groups in a
different order than the key share groups.
If running as a client application, update the GSK_CLIENT_ECURVE_LIST or the
GSK_CLIENT_TLS_KEY_SHARES to include at least one group that is in common between the two lists. The
GSK_CLIENT_TLS_KEY_SHARES list should be a subset of the groups that are specified in the
GSK_CLIENT_ECURVE_LIST. Verify that the GSK_CLIENT_ECURVE_LIST is not empty (NULL).
If running as a server application, contact the remote client partner to verify the elliptic curves or supported groups and the key shares are properly configured. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
An alert has been received from the remote partner that is supported by the protocol, but is not expected by System SSL.
Contact the remote partner and verify that it is sending the appropriate alert in this scenario. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
If TLS V1.3 is enabled, 4-character cipher specifications must be used.
The application must call gsk_attribute_set_enum() and set the enumeration identifier GSK_V3_CIPHERS to have a value of GSK_V3_CIPHERS_CHAR4. Once enabled for 4-character cipher specifications, the application uses the GSK_V3_CIPHER_SPECS_EXPANDED setting for the cipher specifications.
An unexpected protocol fallback to an earlier TLS protocol has been detected by the client.
A fallback to an earlier TLS protocol has been detected by the client although the server supports a later TLS protocol. Verify that the application is communicating with the expected remote partner. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
The remote partner used an incorrect or an unexpected signature algorithm during the TLS V1.3 handshake. The remote partner signed its TLS V1.3 handshake messages with a signature algorithm that was not included in its local signature algorithm list (GSK_TLS_SIG_ALG_PAIRS) or one that is not allowed to be used with TLS V1.3.
Contact the remote partner and verify that it is using the correct signature
algorithm for the TLS V1.3 handshake. The remote partner may use a signature algorithm that is not
supported by the local application to sign TLS handshake messages. If communicating with a z/OS
System SSL remote partner, it may use a preferred signature algorithm if there are no signature
algorithms in common. See Signature and hash algorithms for more information. In these
cases, the local GSK_TLS_SIG_ALG_PAIRS setting should be updated to support the remote partner’s
certificate chain.If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
There are more groups present in the client’s key share group list (GSK_CLIENT_TLS_KEY_SHARES) than there are present in the client’s elliptic curve or supported groups list (GSK_CLIENT_ECURVE_LIST). The groups specified in the client’s key share list should be a subset of the groups specified in the client’s elliptic curve or supported groups list.
The remote partner has indicated that the local partner did not send a required TLS extension during the TLS handshake process. The TLS handshake cannot continue.
Ensure that this application is specifying the required extensions by the communicating partner. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
The remote partner has sent a key share list that is not valid. The key share list contains duplicate key share groups. The TLS handshake cannot continue.
Ensure that the remote partner is sending a valid key share list. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
The remote server partner did not send the required signature algorithm extension in the certificate request.
Ensure that the remote server partner has sent a certificate request and that it contains a required signature algorithm extension. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
An X.509 certificate being utilized locally did not meet the minimum allowed System SSL X.509 certificate version. TLS V1.3 requires certificates to be X.509 version 3 certificates.
Ensure that the version of the locally selected certificate is valid.
The local X.509 certificate contains an RSA or ECC key that is smaller than the minimum size allowed. TLS V1.3 requires that RSA keys have a minimum size of at least 2048 bits, and ECC keys must have a minimum size of at least 256 bits.
Ensure that the key sizes are at least equal to the minimum supported key sizes for the protocol.
The certificate key algorithm is not valid for the selected protocol. If the selected protocol is TLS V1.2 and earlier, the server certificate can use either RSA, DSA, Diffie-Hellman, or ECC as the public/private key algorithm. If the selected protocol is TLS V1.3, the server certificate can use either RSA or ECC as the public/private key algorithm.
Specify a certificate with the appropriate key type.
A TLS handshake message from the remote partner contained an extension that is not allowed or supported. The remote partner did not correctly encode the TLS handshake message.
Ensure that the remote partner is correctly encoding the TLS handshake message. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
A TLS handshake message contains an incorrect compression field. The compression field must be a single byte set to 0.
Ensure that the remote partner is correctly encoding the TLS handshake message. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
A TLS handshake message from the remote partner contains a Session ID value that is different from the Session ID that was sent to the remote partner. The Session ID value in the TLS handshake message from the remote partner must be the same. The attempted TLS handshake fails.
Ensure that the remote partner is correctly encoding the TLS handshake message. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
The remote partner has indicated that it does not support the certificate that has been sent to it or the remote partner's own certificate is not supported.
Ensure that the remote partner is correctly configured to receive the configured certificate and the remote partner's own certificate is supported. The remote partner may need to update its supported signature list to allow the certificate’s signature to be used. If the remote partner is another System SSL application, the GSK_TLS_SIG_ALG_PAIRS or GSK_TLS_CERT_SIG_ALG_PAIRS settings may need to be updated. The remote partner may require a minimum key certificate key size. If the remote partner is another System SSL application, the GSK_PEER_RSA_MIN_KEY_SIZE, GSK_PEER_ECC_MIN_KEY_SIZE, GSK_PEER_DSA_MIN_KEY_SIZE, or GSK_PEER_DH_MIN_KEY_SIZE settings may need to be adjusted on the remote partner. If the remote partner is configured correctly, it may be necessary to update the local certificate to one that is supported by the remote application.
If a TLS V1.3 handshake is attempted, there are limitations on the key type and sizes that are allowed for TLS V1.3. See gsk_secure_socket_init() 's usage section for more information.
If the remote partner supports the certificate sent to it, the remote partner's own certificate may need to be updated. If the remote partner is another System SSL application running in FIPS mode, ensure that the remote partner's certificate is supported. See Algorithms and key sizes for more information about the supported certificates in FIPS mode.
If the problem persists, contact the remote partner application to collect additional diagnostic data to determine why the sent certificate or the remote partner's own certificate is not supported.
The client attempted a TLS V1.3 session resumption with only one session ticket present in its pre-shared key extension. The server responded with an unexpected index value present in its pre-shared key extension response.
Ensure that the remote server partner is operating correctly and supports TLS V1.3 session resumption. If the problem persists, contact the vendor of the remote server partner.
System SSL supports only PSK with (EC)DHE key establishment for TLS V1.3 resumption. The remote partner has not indicated its support of PSK with (EC)DHE.
Ensure that the remote partner supports and is specifying support for PSK with (EC)DHE key establishment for TLS V1.3 resumption. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
If the remote partner is another SSL/TLS provider, contact the vendor of that product.
The server can no longer send or accept session tickets because the number of seconds since the initial handshake has exceeded the server timeout value.
The server cannot send or receive session tickets until the remote partner has requested a new connection and a full TLS V1.3 handshake has been negotiated. If the problem persists, the GSK_SESSION_TICKET_SERVER_TIMEOUT setting may need to be increased.
The client detected that the server selected an incompatible cipher specification on the TLS V1.3 resumption handshake attempt. Servers supporting TLS V1.3 resumptions may use a different cipher specification on the resumed handshake as long as the hash algorithm associated with the two ciphers are compatible. If the initial handshake used cipher 1301 and the server selected cipher 1303 on the resumed handshake, this is not allowed as cipher 1301 uses a hash algorithm of SHA-256 while cipher 1303 uses a hash algorithm of SHA-384. The resumption handshake attempt fails.
Contact the remote server partner to determine why they allowed a TLS V1.3 resumption to occur with an incompatible cipher specification. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
If the remote partner is another SSL/TLS provider, contact the vendor of that product.
The provided buffer does not contain valid data for the function being performed.
Provide valid data in the buffer.
TLS V1.3 protocol is not supported in FIPS mode.
Currently, the TLS V1.3 protocol is not supported in FIPS mode and is only supported in non-FIPS mode. If the TLS V1.3 protocol is to be enabled, it must be done in non-FIPS mode. Once FIPS mode is disabled in the application, TLS V1.3 can be enabled by setting the GSK_PROTOCOL_TLSV1_3 environment variable or attribute type in gsk_attribute_set_enum().
The certificate sent to the remote partner during the handshake was not acceptable to the remote partner.
Ensure that the remote partner application is correctly configured to accept the locally configured certificate. The remote partner may be missing a root CA certificate or does not support the locally configured certificate that has been sent to it. If the remote partner is a System SSL application, collect traces of the failure on both sides and then contact your service representative if the error persists. If the remote partner is another SSL/TLS provider, contact the vendor of that product.
The remote partner indicated a handshake failure which is a generic error that is
encountered during the handshake. This can occur for various reasons such as (but not limited to)
the following:Ensure that the client and the server have at least one cipher specification. If the problem persists, collect a System SSL trace and contact the remote partner to obtain the necessary diagnostics or traces to determine why the handshake failed.
Ensure that the GSK_TLS_CERT_SIG_ALG_PAIRS or GSK_TLS_SIG_ALG_PAIRS setting is
defined to include all of the signature algorithm pairs that are both supported by the local
application and expected from the remote peer.
The remote partner has indicated that a TLS message sent from the local application is not valid.
Ensure that the remote partner is correctly parsing the sent TLS message. If the problem persists, collect a System SSL trace and contact the remote partner to obtain the necessary diagnostics or traces to determine why the TLS message is not valid.
The TLS server or client encountered a communicating partner that does not support the extended master secret extension. The TLS extended master secret extension is specified as required locally and the communicating partner did not send or provide the extension during the TLS V1.0, TLS V1.1, or TLS V1.2 handshake.
If running as a client application, the GSK_CLIENT_EXTENDED_MASTER_SECRET option has been set to REQUIRED; however, the remote server partner did not include the extended master secret extension during the TLS V1.0, TLS V1.1, or TLS V1.2 handshake. Ensure that the GSK_CLIENT_EXTENDED_MASTER_SECRET option is set appropriately for the remote server partners that are being contacted. If the server partner is a z/OS System SSL application, ensure that the GSK_SERVER_EXTENDED_MASTER_SECRET option is set to ON or REQUIRED and it must be running z/OS V2R3 or later and have PTFs for APAR OA60105 (z/OS V2R3 and V2R4) applied and active. If the remote server partner is another SSL/TLS provider, contact the remote server partner vendor to enable support for the extended master secret extension.
If running as a server application, the GSK_SERVER_EXTENDED_MASTER_SECRET option has been set to REQUIRED; however, the remote client partner did not include the extended master secret extension during the TLS V1.0, TLS V1.1, or TLS V1.2 handshake. Ensure that the GSK_SERVER_EXTENDED_MASTER_SECRET option is set appropriately for the remote client partners that are communicating with this server. If the client partner is a z/OS System SSL application, ensure that the GSK_CLIENT_EXTENDED_MASTER_SECRET option is set to ON or REQUIRED and it must be running z/OS V2R3 or later and have PTFs for APAR OA60105 (z/OS V2R3 and V2R4) applied and active. If the remote client partner is another SSL/TLS provider, contact the remote client partner vendor to enable support for the extended master secret extension.
The TLS client attempted to use a previously negotiated session with the server that did not originally negotiate the extended master secret extension. On the cached handshake attempt, the remote server indicated that it was able to successfully use the cached session; however, it included the extended master secret extension which is not allowed.
Contact the remote server partner to determine why it is sending the extended master secret extension on a cached TLS handshake. If the problem persists, collect a System SSL trace containing the error and then contact your service representative.
Specify a certificate with the appropriate extended key usage.
When trying to cache updated session ticket information prior to sending a TLS V1.3 session ticket, the System SSL started task, GSKSRVR, could not be contacted. The session ticket is not sent by the System SSL server application.
Verify that the System SSL started task, GSKSRVR, is running when GSK_SYSPLEX_SESSION_TICKET_CACHE is enabled. If sysplex ticket caching is not required, disable GSK_SYSPLEX_SESSION_TICKET_CACHE in the server application. If the problem persists, contact the service representative.
The reference list provided was not valid and server domain-based validation failed. This error might occur if:
Ensure that the reference ID list required is appropriately set to match the server that the client is attempting to connect to.
To validate the server’s certificate with a subject alternative name DNS, set GSK_REFERENCE_ID_DNS with a list of DNS name values. A list can be set with GSK_REFERENCE_ID_CN to compare against the server certificate’s DN common name when no subject alternative name DNS is present in the server certificate.
The requested function requires the SSL V3, TLS V1.0, TLS V1.1, TLS V1.2, or TLS V1.3 protocol.
Ensure that the correct protocol is in use before issuing the request.
The function identifier that is specified for gsk_secure_socket_misc() is not valid.
Specify a valid function identifier.
The value that is specified is not a value that is enumerated as a function for the API.
Ensure that the correct function enumerator is coded for the function.
While using TLS V1.1 or higher protocol, the send sequence number is near the maximum value before which it wraps. For TLS V1.1 and higher, an SSL handshake must occur to reset the send sequence number before the sequence number wrapping. System SSL is unable to automatically initiate a handshake on the current function call. This code is not returned again until after a handshake for the connection resets the send sequence number and the send sequence number is again near the maximum value.
The caller should initiate a handshake by calling gsk_secure_socket_misc, specifying GSK_RESET_CIPHER.When the handshake is initiated, the previous function call that returned this code can be called again.
The gsk_secure_socket_misc() functional identifier is not supported by the protocol version.
The functional identifier is not supported by the connection protocol. GSK_RESET_WRITE_CIPHER is only supported by TLS V1.3 connections.
The attribute identifier is not valid.
Specify a valid attribute identifier.
The attribute length is not valid.
Specify a valid attribute length.
The enumeration value is not valid.
Specify a valid enumeration value.
The session identifier cache callback values are not valid. All callback routines must be provided to use an application session identifier cache.
Specify valid session identifier cache callback values.
The numeric value is not valid.
Specify a valid numeric value.
The attribute parameter value is not valid.
Specify a valid attribute parameter value.
The TLS extension type is not valid or not supported.
Specify a valid or supported TLS extension type value.
TLS extension data that is submitted to the SSL environment or connection is incorrectly defined.
Ensure that the TLS extension data is correctly defined. If the problem persists collect a System SSL trace and contact your service representative.