You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jonathan Costers (JIRA)" <ji...@apache.org> on 2010/08/27 13:32:53 UTC

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

    [ https://issues.apache.org/jira/browse/RIVER-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903375#action_12903375 ] 

Jonathan Costers commented on RIVER-307:
----------------------------------------

What needs to be done to get this infrastructure setup:

1. Check whether the Solaris zone Hudson runs in has the necessary client side Kerberos packages installed
- is kinit available?
- is /etc/krb5/krb5.conf available?
if not, find out whether we can get these packages installed
-> for this, we will need root access to the Hudson zone ...

2. Setup a KDC and admin server in the zone that was created upon Peter's request
- install necessary packages
- configure the KDC (setup a realm)
- create principals in our realm that are needed for our tests
- create keytab files for tests that need them and commit them to svn
-> for this, we will need root access to the kdc zone (believe Peter has that?)

3. Point the Hudson zone to the KDC/realm we created
- modify /etc/krb5/krb5.conf
-> for this, we will need root access to the Hudson zone ...

Not sure whether all this is feasible though ...
Also, I am not really familiar with Solaris administration, so help here would be very welcome

> 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
> "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?

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