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

Make OCSP Archive cutoff configurable in the CA UI, for all OCSP responses, and with (optional) static date (CA notBefore)

    Details

    • Provenance:
      Ordered by Customer
    • Issue discovered during:
      Jenkins
    • Sprint:
      EJBCA Team Alice - 2019 w31, EJBCA Team Alice - 2019 w34

      Description

      This is a compliance issue for eIDAS TSPs. They need to be able to configure ArchiveCutoff in EJBCA. Today you can do it globally using a properties file. 

      • Implement persistence and UI changes
      • Add new logic to OCSP responder
      • Write/update tests
      • Check Statedump output
      • Write upgrade code and an upgrade note
      • Deprecate the property file
      • Update Configdump to include the new properties

      CLI functionality will not be added to this ticket since extensions cannot be edited at all through the CLI at the moment. The changes would be quite substantial enough to deserve its own ticket.

      Updated Documentation:
      OCSP Management: https://doc.primekey.com/ejbca730/ejbca-operations/ejbca-operations-guide/ca-operations-guide/ocsp-management
      Release notes: https://doc.primekey.com/ejbca730/ejbca-release-information/ejbca-release-notes/ejbca-7-3-release-notes
      Upgrade notes: https://doc.primekey.com/ejbca730/ejbca-release-information/ejbca-upgrade-notes/ejbca-7-3-upgrade-notes
      Archive Cutoff: https://doc.primekey.com/ejbca730/ejbca-operations/ejbca-ca-concept-guide/protocols/ocsp/ocsp-response-extensions/archive-cutoff

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bastianf Bastian Fredriksson
              Reporter:
              mikek Mike Agrenius Kushner
              Verified by:
              Bastian Fredriksson, Samuel Lidén Borell, Tomas Gustavsson
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 days Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 days, 3 hours, 58 minutes
                  4d 3h 58m