IBM Support

IJ16640: QRADAR DEPLOY FUNCTIONS CAN TIMEOUT WHEN THE CERTIFICATE VALIDATOR FAILS DUE TO EMPTY CERTIFICATES BEING PRESENT

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

  • It has been identified that test_tomcat_connection.sh can take
    a longer than expected time to complete when empty certificates
    are present in /opt/qradar/trusted_certificates/
    When this occurs, the Certificate Validator does not work and
    can lead to QRadar deploy functions timing out.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring:
    [tomcat.tomcat] [localhost-startStop-1]
    java.security.cert.CertificateException: Unable to initialize,
    java.io.IOException: Short read of DER length
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.ibm.crypto.provider.X509Factory.engineGenerateCertificate(Un
    known Source)
    [tomcat.tomcat] [localhost-startStop-1]    at
    java.security.cert.CertificateFactory.generateCertificate(Certif
    icateFactory.java:407)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.CertificateValidator.g
    etCertsFromFile(CertificateValidator.java:444)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.CertificateValidator.g
    etCertsFromFile(CertificateValidator.java:294)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.Q1X509TrustStoreLegacy
    .loadCertificate(Q1X509TrustStoreLegacy.java:378)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.Q1X509TrustStoreLegacy
    .loadTrustedCertificates(Q1X509TrustStoreLegacy.java:337)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.Q1X509TrustStoreLegacy
    .<init>(Q1X509TrustStoreLegacy.java:96)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.CertificateHandlerLega
    cy.<init>(CertificateHandlerLegacy.java:84)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.Q1X509LegacyTrustManag
    er.loadTrustManager(Q1X509LegacyTrustManager.java:151)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.Q1X509LegacyTrustManag
    er.<init>(Q1X509LegacyTrustManager.java:73)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.Q1TrustManagerFactory.
    getTrustManager(Q1TrustManagerFactory.java:57)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.crypto.trustmanager.Q1TrustManagerFactory.
    getTrustManager(Q1TrustManagerFactory.java:81)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.core.FrameworksContext.postInitialization(
    FrameworksContext.java:852)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.core.FrameworksContext.initFrameworks(Fram
    eworksContext.java:269)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.frameworks.core.FrameworksContext.initFrameworks(Fram
    eworksContext.java:171)
    [tomcat.tomcat] [localhost-startStop-1]    at
    com.q1labs.uiframeworks.listener.FrameworksLifeCycle.contextInit
    ialized(FrameworksLifeCycle.java:310)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.core.StandardContext.listenerStart(StandardC
    ontext.java:4792)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.core.StandardContext.startInternal(StandardC
    ontext.java:5256)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:
    150)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.core.ContainerBase.addChildInternal(Containe
    rBase.java:754)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.core.ContainerBase.addChild(ContainerBase.ja
    va:730)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.core.StandardHost.addChild(StandardHost.java
    :734)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.startup.HostConfig.deployDirectory(HostConfi
    g.java:1140)
    [tomcat.tomcat] [localhost-startStop-1]    at
    org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostC
    onfig.java:1875)
    [tomcat.tomcat] [localhost-startStop-1]    at
    java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja
    va:522)
    [tomcat.tomcat] [localhost-startStop-1]    at
    java.util.concurrent.FutureTask.run(FutureTask.java:277)
    [tomcat.tomcat] [localhost-startStop-1]    at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    [tomcat.tomcat] [localhost-startStop-1]    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    [tomcat.tomcat] [localhost-startStop-1]    at
    java.lang.Thread.run(Thread.java:812)
    

Local fix

  • Remove the empty certificates from
    /opt/qradar/trusted_certificates and retry the deploy function.
    Contact Support if assistance is required with this task.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 GA.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 GA.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ16640

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    728

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-06

  • Closed date

    2019-12-06

  • Last modified date

    2019-12-06

  • 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

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"728","Edition":""}]

Document Information

Modified date:
06 December 2019