> + throw new HttpException("invalid algorithm", e);
> + } catch (InvalidKeyException e) {
> + throw new HttpException("invalid key", e);
> + } catch (SignatureException e) {
> + throw new HttpException("invalid signature", e);
> + } catch (UnsupportedEncodingException e) {
> + throw new HttpException("invalid encoding", e);
> + }
> +
> + return res;
> + }
> +
> + private static KeyPair getKeyPair(String keyPath) throws IOException {
> + BufferedReader br =
> + new BufferedReader(new
> InputStreamReader(JoyentBlobRequestSigner.class.getResourceAsStream(keyPath)));
> + Security.addProvider(new BouncyCastleProvider());
Remove this line. If Boundycastle is a must, the ApiMetadata should be
configured to include the `BouncyCastleCryptoModule` and have the jclouds
bouncycastle driver as a dependency. If it is not mandatory, then just delete
this line and let users add the BouncyCastleModule when creating the context if
they prefer to use that library.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/188/files#r7140962
