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

ACME persistence: CRUD for AcmeAccountData

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EJBCA 6.15.0
    • Component/s: None
    • Labels:
      None
    • Epic Link:
    • Sprint:
      EJBCA Sprint 18

      Description

      In order to support parallel requests and avoid awkward object-in-object serialization, we should split out the objects now stored under the AcmeAccountData.

      Todos:

      • ORM
      • Update/create CRUD SSB
      • Add index recommendations if needed (based on get-methods in CRUD SSBs)

      Considerations:

      • Do not use foreign keys, but do reference the object(s) and object belongs to.
      • After UI design, we might want to add additional meta-data columns in order to allow admins to search for this data quickly.
      AcmeConfiguration 1-* AcmeAccountData 1-* AcmeOrderData
                                             |        1
                                             |        |
                                             |        *
                                             -* AcmeAuthorizationData 1-* AcmeChallengeData 1-1 AcmeIdentifier
      

      This ticket could be split into several non-parallel smaller tickets going right-to-left in the diagram above (AcmeIdentifier is just informative but probably needs to be searchable columns in AcmeChallengeData.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mikek Mike Agrenius Kushner
              Reporter:
              johan Johan Eklund
              Verified by:
              Bastian Fredriksson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 days
                  3d
                  Remaining:
                  Time Spent - 30 minutes Remaining Estimate - 2 days, 7 hours, 30 minutes
                  2d 7h 30m
                  Logged:
                  Time Spent - 30 minutes Remaining Estimate - 2 days, 7 hours, 30 minutes
                  30m