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

Stop writing complete stack traces for expected validation failures

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EJBCA 6.10.0
    • Component/s: None
    • Labels:

      Description

      We currently put out a full stacktrace for what can essentially be a pretty standard problem, such as a domain not passing a CAA check:

      aused by: org.cesecore.keys.validation.ValidationException: CAA Validator 'CAA Validator' failed issuance of certificates to issuer letsencrypt.org, with messages: [Not allowed to issue certificate for dnsName portal.seebacher.net. Result type was: DNSSEC validation failed. Parameters: {} Message: DNSSEC validation failed. Response code was SERVFAIL. Additional output: NSEC3s proved no DS. Message Header was not authenticated. ].
      	at org.cesecore.keys.validation.KeyValidatorSessionBean.performValidationFailedActions(KeyValidatorSessionBean.java:536) [cesecore-ejb.jar:]
      	at org.cesecore.keys.validation.KeyValidatorSessionBean.validateDnsNames(KeyValidatorSessionBean.java:423) [cesecore-ejb.jar:]
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0-u40-b27]
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0-u40-b27]
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0-u40-b27]
      
      

      ...we should stop doing that...

        Attachments

          Activity

            People

            • Assignee:
              hsunmark Henrik Sunmark
              Reporter:
              mikek Mike Agrenius Kushner
              Verified by:
              Mike Agrenius Kushner
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 hours
                3h
                Remaining:
                Time Spent - 1 hour, 15 minutes Remaining Estimate - 1 hour, 45 minutes
                1h 45m
                Logged:
                Time Spent - 1 hour, 15 minutes Remaining Estimate - 1 hour, 45 minutes
                1h 15m