[RIVER-307] KDC (Key Distribution Center) Server for kerberos tests

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Web site and infrastructure
• Assignee: Unassigned
• Reporter: Peter Firmstone
• Created: 08/May/09 10:22
• Updated: 15/Sep/10 20:54

Description

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
"jiniautot.east.sun.com".

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:

http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200904.mbox/%3C20090421151237.GA19950@east%3E

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

Issue Links

• is depended upon by: RIVER-301 Move the QA framework donated by Sun inside the jtsk trunk and integrate into build process