OpenJDK 6: working ok
OpenJDK 7: working ok
Oracle JDK 6: JCE install required
Oracle JDK 7: ? - did those jce policy files work for anyone in oracle jdk
1.7?
I believe it is not really user-friendly, but acceptable both from legal
(not a lawyer) and usability perspective if we tell the system
ad
Yes, the _content_ of the jar files are different. It is kind of misleading.
On Tue, Nov 12, 2013 at 4:13 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> I had the two JAR files in my /jre/lib/security, as well, and
> the tests were failing. When I replaced them with the ones I downl
The test don't do anything fancy with encryption. They just create a
command object and pass it to the certificate service which does
certificate validation. If the tests are failing because of a JCE
dependency, the management server should also fail when those commands
are sent over the API. S
I had the two JAR files in my /jre/lib/security, as well, and
the tests were failing. When I replaced them with the ones I downloaded
from Oracle, the tests passed.
On Mon, Nov 11, 2013 at 11:05 PM, Koushik Das wrote:
> I see the JCE extensions in jdk 1.7 as well. They are present under
> /jre/l
IMO - having this as a requirement for a build is a bit of an issue.
First, we can't distribute it (obviously). Second, it's a bit of an
esoteric requirement if you are using a JDK that doesn't include it
automatically. This will lead to confusion.
Is there a way that we can re-work the tests to
It seems OpenJDK 6 and 7 are ok. Oracle jdk 6 needs JCE, oracle jdk 7 may
need another extension (the JCE for jdk6 did not work for me).
I would recommend that we @Ignore the failing tests, add some assumption or
move them to a special test group which is not executed by default.
On Tue, Nov 12,
The following tests are failing in my environment even with the JCE extensions.
/* Test7: If no chain is given, the certificate should be self signed.
Else, uploadShould Fail */
runUploadSslCertNoChain();
/* Test8: Chain is given but does not have root certificate */
I see the JCE extensions in jdk 1.7 as well. They are present under
/jre/lib/security. But still I see a test failure. Is there any
other configuration that is required?
Running org.apache.cloudstack.network.lb.CertServiceTest
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.456
My MacOSX 1.6 jdk seems to have the crypto extensions jce builtin and
the build+test works. JDK 1.7 install does not have them though.
The JCE kit seems to carry a BCL which is not ASF friendly [1]. But
this being part of the Java install and not the project it should be
okay IMO if we note it in
Hi,
That is a good question, I do not know for sure, but this package needs to
be signed by oracle, it is not redistributable and has teritorial import
restrictions, so it could be problematic :-( I hope it is not. Guys, can
someone help us here?
On Mon, Nov 11, 2013 at 10:21 PM, Syed Ahmed wro
Hi Laszlo,
The CertService uses BouncyCastle for certificate parsing and
validation. The JCE extension provides the API for using BouncyCastle as
the provider. So, JCE is required. I know that BouncyCastle is added in
CS. Would it be possible to add JCE as a dependency too?
Thanks,
-Syed
On
11 matches
Mail list logo
