Uploaded image for project: 'EJBCA'
  1. EJBCA
  2. ECA-7686

PublishCertificateMessage.instance should not rely on database.useSeparateCertificateTable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: EJBCA 6.14.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      org.ejbca.peerconnector.publisher.PublishCertificateMessage.instance(...) depends on {CesecoreConfiguration.useBase64CertTable()}} to determine if Base64CertData should be written to the VA instead of copying the state of the CA.

      This works as on the server JVM, but PublishCertificateMessage.instance(...) is also invoked from JUnit tests client JVM where the logic fails unless database.useSeparateCertificateTable is consistent with the setting on the server JVM.

      PublishCertificateMessage.instance(...) should not rely on database.useSeparateCertificateTable since it can change over time, but instead handle the available data as well as it can.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                johan Johan Eklund
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: