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

GDPR Adapt the Legacy VA Publisher

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EJBCA 6.15.1
    • Component/s: None
    • Labels:
      None
    • Sprint:
      EJBCA Sprint 21 Team Alice, EJBCA Team Alice - 2018 w45

      Description

      A customer has lifted a urgent request that we implement GDPR-adaption of the legacy (direct database) VA Publisher. This should be implemented in the UI identically to how it looks for the Peer VA Publisher:

      Implementation wise it should be easier: if the box is checked, then only issuer, serial number and status should be published to the VA. Other info can be published as well if required for the VA to function, but specifically not any identifying information about the certificate holder. Any corner cases should be noted in the documentation. 

      Naturally care should be taken to add OCSP tests with this format as well, to verify that the responder still works with just this info available (it should). 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              hsunmark Henrik Sunmark
              Reporter:
              mikek Mike Agrenius Kushner
              Verified by:
              Mike Agrenius Kushner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 days
                  3d
                  Remaining:
                  Time Spent - 1 day, 4 hours Remaining Estimate - 1 day, 4 hours
                  1d 4h
                  Logged:
                  Time Spent - 1 day, 4 hours Remaining Estimate - 1 day, 4 hours
                  1d 4h