> private final TrustManager[] trustManager;
> private final Supplier<Credentials> creds;
>
> @Inject
> - SSLContextWithKeysSupplier(Supplier<KeyStore> keyStore, @Provider
> Supplier<Credentials> creds, HttpUtils utils,
> - TrustAllCerts trustAllCerts) {
> - this.keyStore = keyStore;
> - this.trustManager = utils.trustAllCerts() ? new TrustManager[] {
> trustAllCerts } : null;
> + SSLContextWithKeysSupplier(@Provider Supplier<Credentials> creds,
> TrustAllCerts trustAllCerts) {
> + this.trustManager = new TrustManager[]{trustAllCerts};
Really don't know how to solve that.
>From Docker doc, even if you specify the certs, you may need to run curl
>command with -insecure as the certificates generated for boot2docker are
>self-signed.
I think the equivalent in jclouds of `insecure` is `trustAllCerts` even if you
pass identity and credential. Initially I was using `utils.trustAllCerts()` to
act accordingly but `OkHttpCommandExecutorServiceModule` overrides the
decision taken at level of docker.
I think we should we change `OkHttpCommandExecutorServiceModule`
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/113/files#r21886574
