You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jclouds.apache.org by Andrew Phillips <an...@apache.org> on 2015/09/05 18:20:01 UTC

Re: ec2 authorization issue after upgrading to 1.9.1

[moving this to user@...]

> What is the correct procedure to pass certificate for every public
> clouds through jclouds? if I have to ship the application to any
> remote machine ?

In terms of trusting certificates, jclouds doesn't behave any 
differently than any other Java application. The first question for me 
would be why the certificate is being rejected in the first place - the 
public cloud providers should all have certificates that are signed by 
trusted CAs, and so should be accepted by the JVM without any changes.

Are they endpoints you're connecting to using self-signed certs, or is 
there any other obvious reason (hostname mismatches, expired certs etc.) 
why they would be rejected? Or are the JVMs you're running on using a 
different set of trusted CAs?

Regards

ap

Re: ec2 authorization issue after upgrading to 1.9.1

Posted by Andrew Phillips <an...@apache.org>.
> After upgrading to 1.9.1 it's starts happening. Any idea ?

What was the previous version you were using? Were there any other 
changes you made to your setup, e.g. the JVM type of version?

This is not something we've had anyone else report so far, so at this 
point it seems more likely to be an interplay between jclouds and other 
parts of the environment.

Regards

ap