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

Upgrade of CAA Validator not triggered when ValidatorBase changed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EJBCA 6.11.0
    • Component/s: None
    • Labels:
      None
    • Issue discovered during:
      Ad Hoc
    • Sprint:
      EJBCA Sprint 5

      Description

      Updates in ECA-6051 exposed an existing issue with upgrades of CaaValidators (it wasn't relevant before since there were no validator upgrades before).
      When ValidatorBase was upgraded (in this case with the PHASE keyword) all validators that read the "latest version" from ValidatorBase was upgrade nicely (Key and Blacklist Validators), hoever CaaValidator was not upgraded which results in a NPE when clicking an older CaaValidator in the GUI (when the PHASE key is read which is null when upgrade was not done).
      All validators should read the "latest version" from ValidatorBase during load so that their UpgradeableDataHashMaps are upgraded when the LATEST_VERSION in ValidatorBase is changed.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tomas Tomas Gustavsson
                Reporter:
                tomas Tomas Gustavsson
                Verified by:
                Mike Agrenius Kushner
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: