Allow self-signed certificates for content-package plugin

Description

Currently the content-package Plugin only works with SSL if the Certificate is trusted.
This brings up some problems with self-signed certificates used on several testing system.s
It would be helpful to have an (optional) parameter to also allow self-signed certificates.

The code-changes would involve the getHttpClient() method and an optional parameter.

1 2 3 SSLContext sslContext = new SSLContextBuilder().loadTrustMaterial(null, new TrustSelfSignedStrategy()).build(); SSLConnectionSocketFactory sslsf = new SSLConnectionSocketFactory(sslContext); return HttpClients.custom().setSSLSocketFactory(sslsf)...

If you could provide a fitting parameter name, I'd be happy to create a pull-request for this. How about: vault.trustSelfSigned ?

Environment

None

Status

Assignee

Unassigned

Reporter

Alexander Muthmann

Labels

None

Components

Fix versions

Affects versions

Content Package Maven Plugin 1.1.0

Priority

Major
Configure