-
Bug
-
Resolution: Fixed
-
Minor
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
Assignee | New: valentina armenise [ varmenise ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Workflow | Original: JNJira [ 173250 ] | New: JNJira + In-Review [ 185825 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Closed [ 6 ] |
Labels | New: lts-candidate |
Labels | Original: lts-candidate | New: 2.19.2-fixed |
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)