You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2008/10/20 14:55:44 UTC
[jira] Updated: (DIRSERVER-1279) kerberos test failing on IBM JDK
[ https://issues.apache.org/jira/browse/DIRSERVER-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Anstey updated DIRSERVER-1279:
---------------------------------------
Attachment: DIRSERVER-1279.patch
Here's a simple patch to fix the issue. I just removed the hard coded reference to a Sun security provider with a dynamic call. Tested this fix on Linux (with Sun JDK) and AIX (with IBM JDK).
> kerberos test failing on IBM JDK
> --------------------------------
>
> Key: DIRSERVER-1279
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1279
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: kerberos, ldap
> Affects Versions: 1.5.4
> Environment: AIX 5.2
> IBM JDK 1.5.0
> Reporter: Jonathan Anstey
> Fix For: 1.5.5
>
> Attachments: DIRSERVER-1279.patch
>
>
> The following kerberos test fails on the IBM JDK.
> -------------------------------------------------------------------------------
> Test set: org.apache.directory.server.kerberos.kdc.SaslGssapiBindITest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 15.396 sec <<< FAILURE!
> testSaslGssapiBind(org.apache.directory.server.kerberos.kdc.SaslGssapiBindITest) Time elapsed: 15.268 sec <<< ERROR!
> java.lang.RuntimeException: Failed to create KeyManagerFactory
> at org.apache.directory.server.ldap.handlers.extended.StartTlsHandler.setLdapServer(StartTlsHandler.java:164)
> at org.apache.directory.server.ldap.LdapService.startLDAP0(LdapService.java:417)
> at org.apache.directory.server.ldap.LdapService.start(LdapService.java:323)
> at org.apache.directory.server.unit.AbstractServerTest.setUp(AbstractServerTest.java:275)
> at org.apache.directory.server.kerberos.kdc.SaslGssapiBindITest.setUp(SaslGssapiBindITest.java:84)
> at junit.framework.TestCase.runBare(TestCase.java:132)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:618)
> at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.security.NoSuchAlgorithmException: SunX509 KeyManagerFactory not available
> at sun.security.jca.GetInstance.getInstance(GetInstance.java:158)
> at javax.net.ssl.KeyManagerFactory.getInstance(KeyManagerFactory.java:20)
> at org.apache.directory.server.ldap.handlers.extended.StartTlsHandler.setLdapServer(StartTlsHandler.java:160)
> ... 22 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.