Repository navigation
[JENKINS-36537] UpdateNow function on metadata should consider a custom json signature validator #17315
Description
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.
Originally reported by varmenise, imported from: UpdateNow function on metadata should consider a custom json signature validator
- assignee: varmenise
- status: Closed
- priority: Minor
- component(s): core
- label(s): 2.19.2-fixed
- resolution: Fixed
- resolved: 2016-09-16T07:38:36+00:00
- votes: 0
- watchers: 3
- imported: 2025-11-24
Raw content of original issue
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.
Activity
jenkins-infra-bot commentedon Aug 23, 2016
Raw content of original 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)
jenkins-infra-bot commentedon Oct 10, 2016
Raw content of original comment:
Backporting this with the restriction intentionally.