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

Implement Certificate/CRL Reader implementation

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EJBCA 6.15.1
    • Component/s: None
    • Labels:
      None
    • Epic Link:
    • Sprint:
      EJBCA Sprint 21 Team Bob, EJBCA Team Bob - 2018 w45

      Description

      In order to integrate with the old waterfall implementation, we need the complementary reader as well. This should be implemented as a custom service which periodically scans a local directory and inserts any new certificates contained therein into the database for VA use. I would suggest that read certificates are archived in a separate directory once read and scanned in. 

      This reader should be implemented as an EE feature, so thus should be places in the plugins-ee module. Naturally, system tests and a proper documentation page are required =) 

      For reference, I've uploaded the legacy implementation to DeathStar - it should not be used as a guide (because it's rubbish), but can be used to double check the requirements. The CRL parts of the reader are already fulfilled by the existing CRL reader. 

      Important: Note that the certificate/CRL files may (but don't have to be) be signed by a CA,  see PushToDataBase.getAndVerifySignedData(byte[], List<X509Certificate>) in the original implementation. Use a certificate sample from the SCP Publisher (the test can be used to produce a sample) to verify. 

      Documentation Link: http://confluence.primekey.com/display/EJBCADS/.Services+v6.15.1#id-.Servicesv6.15.1-CertificateandCRLReaderService

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mikek Mike Agrenius Kushner
              Reporter:
              mikek Mike Agrenius Kushner
              Verified by:
              Ulf Undmark
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 days Original Estimate - 3 days
                  3d
                  Remaining:
                  Remaining Estimate - 3 days
                  3d
                  Logged:
                  Remaining Estimate - 3 days
                  4m