IBM Support

IT29453: ONE OF TWO SIMULTANEOUS INSTANCES OF A JAVATASK FOR OCSP VALIDATION FAILS WITH "CMS SIGNATURE VERIFICATION FAILURE"

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A trading partner sends 2 files at the exact same time, one
    instance of the
    JavaTask for the OCSP request is successful and for other file
    the JavaTask fails with a
    "CMS signature verification failure" (No signature results
    found.
    File was not signed or error verifying signature).
    Only one instance of the OCSP_Request business process is
    executed.
    

Local fix

  • RTC 581625
    none
    

Problem summary

  • Users Affected:
    Customers using B2B Integrator OCSP Certificate validation to
    verify certificates from the Trading Partners.
    
    Problem Description:
    
    Concurrent OCSP Certificate validation of the same certificate
    to the same OCSP provider results in multiple current
    requests to the provider.  This can result in empty OCSP
    Request documents being sent to the provider, or empty OCSP
    Response documents received from the provider.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix is provided.
    Added an OCSP Request Caching to allow a single OCSP Request
    to
    a provider to be used for request valdation. The corresponding
    OCSP Response is then used to validate all concurrent cached
    requests.
    
    
    Delivered In:
    5020603_11
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29453

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    526

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-24

  • Closed date

    2019-08-29

  • Last modified date

    2019-09-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
04 September 2019