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
- implements
-
ECA-7216 Dependency issue, Acme*SessionBean should reside in edition-specific-ee module
-
- Closed
-
- is blocked by
-
ECA-7185 ACME persistence: Create ORM scripts AcmeAccountData
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates
-
ECA-7138 Ensure quality in ACME
-
- Closed
-
