Since you got this error, I am assuming that the algorithm while
creating the key manager factory is hardcoded which makes it dependent
on the JVM. You can instead create the key manager factory as below to
avoid this.
KeyManagerFactory kmf = KeyManagerFactory.getInstance(KeyManagerFactory
.getDefaultAlgorithm());
This basically uses the default algorithm specified in the Java
security properties. This approach has worked for me using Sun and IBM
jdks.
thanks,
Srikanth
On 1/8/07, Alex Karasulu <[EMAIL PROTECTED]> wrote:
Trustin,
I got the following error on my mac ppc running Ubuntu which only has
the IBM jvm as an option.
[EMAIL PROTECTED]:~/trunks/apacheds/server-ssl$ cat
target/surefire-reports/org.apache.directory.server.ssl.LdapsITest.txt
-------------------------------------------------------------------------------
Test set: org.apache.directory.server.ssl.LdapsITest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 14.486
sec <<< FAILURE!
testSetUpTearDown(org.apache.directory.server.ssl.LdapsITest) Time
elapsed: 14.241 sec <<< ERROR!
javax.naming.NamingException: Failed to create a SSL context. [Root
exception is java.security.NoSuchAlgorithmException: SunX509
KeyManagerFactory not available]
Is there any way we can use an alternative class in the IBM JDK and
detect the JDK to swap these classes based on the jvm system property?
Alex
