Fixes are available
Closed as fixed if next.
When verifying the signature of a request/response, the verify action fails with *Certificate Not Found* error, although the correct signing certificate is uploaded within the domain. This can occur if the signed incoming message uses an X509IssuerSerial reference to identify the certificate that signed the message. For example: <X509IssuerSerial> <X509IssuerName>C=US,O=XYZ,CN=Tree-Sys</X509IssuerName> <X509SerialNumber>123456789123456789</X509SerialNumber> </X509IssuerSerial>
In the Verify Action, set the "Optional Signer Certificate" parameter to the appropriate certificate object name. This forces the Verify Action to find the certificate immediately, instead of searching the domain using the IssuerSerial lookup method.
Fix will be available in a future major release.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels