river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Firmstone (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-307) KDC (Key Distribution Center) Server for kerberos tests
Date Fri, 08 May 2009 10:23:45 GMT
KDC (Key Distribution Center) Server for kerberos tests

                 Key: RIVER-307
                 URL: https://issues.apache.org/jira/browse/RIVER-307
             Project: River
          Issue Type: Sub-task
          Components: Web site and infrastructure
            Reporter: Peter Firmstone

>From Peter Jones comment:

Another failed assumption of the previous internal Sun environment:
this test is expecting to find a Kerberos KDC at the host name

FAILED: net/jini/jeri/kerberos/UnitTests/runTestEndpoints.sh
FAILED: net/jini/jeri/kerberos/UnitTests/runTestPerformance.sh

These tests failed because they attempt to invoke the JRE's "kinit"
tool using the internal sun.security.krb5.internal.tools.Kinit API,
from which it was available in 1.4.x and 5.0 JRE versions.  The Java
version of this tool was removed from the Solaris and Linux JREs for
version 6 because there is a native kinit on those platforms, although
it remains in the Windows JRE.

Beyond this kinit problem, though, these Kerberos tests would surely
have failed expecting to find a KDC at "jiniautot.east.sun.com" like
the previous two.

FAILED: net/jini/jeri/tcp/localHostExposure/LocalHostExposure.java
FAILED: net/jini/jeri/transport/multihomed/Multihomed.java
FAILED: net/jini/jeri/transport/multihomed/runMultihome.sh

These tests failed during the compilation phase because of this issue
discussed recently here:


What's the best way to implement a KDC for tests?    Your thoughts please?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message