The CipherPayload implementations were manually instantiating the Cipher to use. Instead of that, now the constructors requires a Crypto instance that can be obtained from the injector, which is already configured with the right JCE provider, for example the one wired up by the Bouncyclastle driver.
This will allow users using the CipherPayloads to use a custom JCE provider configured when creating the context (via specific drivers). You can merge this Pull Request by running: git pull https://github.com/nacx/jclouds cipher-payload Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/428 -- Commit Summary -- * Use the configured JCE provider in the Cipher payloads -- File Changes -- M core/src/main/java/org/jclouds/io/payloads/BaseCipherPayload.java (6) M core/src/main/java/org/jclouds/io/payloads/RSADecryptingPayload.java (7) M core/src/main/java/org/jclouds/io/payloads/RSAEncryptingPayload.java (7) -- Patch Links -- https://github.com/jclouds/jclouds/pull/428.patch https://github.com/jclouds/jclouds/pull/428.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/428
