Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x509: certificate signed by unknown authority #1

Closed
PhilipSchmid opened this issue May 15, 2018 · 2 comments
Closed

x509: certificate signed by unknown authority #1

PhilipSchmid opened this issue May 15, 2018 · 2 comments

Comments

@PhilipSchmid
Copy link

Hi there,

Description

I just noticed that butler fails to import jobs, when Jenkins runs behind a self signed TLS certificate:

macbookpro:jenkins phil$ butler jobs import --server jenkins.example.com --username admin --password <my-secret> 
Import job: Git_Sync
Get https://jenkins.example.com:443/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb): x509: certificate signed by unknown authority

Related Issue

None

Changes proposed

Would it be possible to add an argument --skip-tls-check or something similar do disable the check if the TLS certificate is officially signed?

Screenshots

None

Thanks

Regards,
Philip
mlabouardy pushed a commit that referenced this issue Dec 3, 2018
@icereed
Merge pull request #1 from kentrikos/feature/credential-mover
6f1b1a7 
This enables migration of credentials between Jenkins instances.

Butler will get the XML config of any folder and will ingest
the encrypted secrets. The encrypted secrets are then decrypted
via a Groovy script executed on Jenkins master. This needs
most of the times admin privileges.

In a second step you can pipe in the decrypted credentials
and apply them to another folder or even instance.
Also a Groovy script is leveraged in order to achieve this.
@digitalfredy
Copy link

Related or same as #10

@PhilipSchmid
Copy link
Author

Closing this issue since this tool is not needed anymore by my current company and nobody responded within 2 years.

Regards,
Philip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@digitalfredy @PhilipSchmid