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

Importing CA hierarchies in Configdump not always working

    Details

    • Issue discovered during:
      Another issue
    • Sprint:
      EJBCA Team Bob - 2019 w40, EJBCA Team Bob - 2019 w42

      Description

      When importing a CA hierarchy with Configdump, the issuer must be imported before the subject, but this order is not enforced. Thus you may end up with the error:

      Import failed: (CA with name X) No CA named 'Y' exists.
      

      The solution is to manually import the issuer before the subject by running Configdump twice.

      Configdump should do dependency resolution during import to ensure that the order in the YAML file does not matter. Write utility class which reorders a list of CAs. It should work both for the trivial CA hierarchy Root -> Sub CA, but also for more complex CA hierarchies with multiple levels, cross-signings ect.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bastianf Bastian Fredriksson
              Reporter:
              bastianf Bastian Fredriksson
              Verified by:
              Samuel Lidén Borell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 hours Original Estimate - 3 hours
                  3h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 days, 1 hour, 5 minutes
                  4d 1h 5m