Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Won't Do
-
Component/s: jenkins.io, mirrors.jenkins.io, update-center
-
Labels:
-
Similar Issues:
Description
Hi Team,
We want to use our on-premise update center instead of the default update center for jenkins, for that we have created a mirror to Jenkins plugin repo on our Artifactory and used the https://github.com/ikedam/backend-update-center2 to create our own update-center.json with required plugins that we use.
Upon updating the default update site url with our internal Artifactory update-center.json url we are getting the signature not verified error.I have added the internal ca certificate to the java cacerts as well but still getting the same error.
Is there a way we can use the internal update center for the Jenkins plugins instead of the default one?
I have attached the error details to this ticket.
Thanks
Kushal
Attachments
Activity
Andrew Bayer Can you help me this issue >??
Hi kushal Reddy, kindly reminder that INFRA project is not a support site and this tool is used to track issues related to the jenkins infra structure project like jenkins Jira, Confluence, Jenkins.io, not others people infrastructure. Another important element is that most of the people who work in this project are volunteers who work on their freetime 
You may reach more people by using the user mailing list https://jenkins.io/mailing-lists/#jenkinsci-usersgooglegroups-com which is design for that
Regarding your issue, it's difficult to tell with only your debug file, but it seems to be related to your ca.crt. Are you using a self signed certificate? letsencrypt?
Does this command work for you ? `certtool --verify --infile <your_cert> --load-ca-certificate ca.crt
Is Anybody there to take care of this issue, it's a blocker for me.