Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36537

UpdateNow function on metadata should consider a custom json signature validator

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core

      the getJsonSignatureValidator was added in UpdateSite to give the possibility to UpdateSite subclasses to define a custom JsonSignatureValidator. However the updateNow function on metadata does not using it . This results in `signature validations exceptions` on signature checks.

          [JENKINS-36537] UpdateNow function on metadata should consider a custom json signature validator

          Code changed in jenkins
          User: valentina
          Path:
          core/src/main/java/hudson/model/DownloadService.java
          core/src/main/java/hudson/model/UpdateSite.java
          http://jenkins-ci.org/commit/jenkins/8acc12ff7933774dd92c37d3ca5ac1c77f217b39
          Log:
          [FIXED JENKINS-36537] Allow the use of custom json signature validator for metadata signature check (#2442)

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: valentina Path: core/src/main/java/hudson/model/DownloadService.java core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/8acc12ff7933774dd92c37d3ca5ac1c77f217b39 Log: [FIXED JENKINS-36537] Allow the use of custom json signature validator for metadata signature check (#2442)

          Backporting this with the restriction intentionally.

          Oliver Gondža added a comment - Backporting this with the restriction intentionally.

            varmenise valentina armenise
            varmenise valentina armenise
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: