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

Order of log entries in async CAA lookup

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Since ECA-6138, each CAA lookup for a certificate SAN is made in parallel. This will probably cause the log entries written with log4j to appear "huller om buller" making the log output harder to read.

      Instead of sending a log entry to log4j directly, we should queue them in for example a ConcurrentHashMap<String, LinkedList<String>> which maps a particular domain name to a list of log messages for that domain, and then print this map before exiting the CAA validator.
      There is already a 'log' method in CaaDnsLookup we can use.

      To make debugging of our customers' issues easier and avoid confusing them, this should probably be fixed before we release EJBCA 6.10.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bastianf Bastian Fredriksson
              Reporter:
              bastianf Bastian Fredriksson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 hours
                  3h
                  Remaining:
                  Remaining Estimate - 3 hours
                  3h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified