You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Firmstone (JIRA)" <ji...@apache.org> on 2009/08/27 13:20:59 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=12748337#action_12748337 ] 

Peter Firmstone commented on RIVER-307:
---------------------------------------

Anyone on the list got Kerberos KDC admin experience? 

    [ https://issues.apache.org/jira/browse/INFRA-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Maurer resolved INFRA-2098.
----------------------------------

    Resolution: Fixed

zone was created and details sent to peter...

> > Zone for Apache River Kerberos KDC Server for Testing
> > -----------------------------------------------------
> >
> >                 Key: INFRA-2098
> >                 URL: https://issues.apache.org/jira/browse/INFRA-2098
> >             Project: Infrastructure
> >          Issue Type: Task
> >      Security Level: public(Regular issues) 
> >          Components: Zones
> >         Environment: Solaris 10 Zone with MIT Kerberos V
> >            Reporter: Peter Firmstone
> >            Assignee: Norman Maurer
> >
> > A Kerberos KDC server is required for running the Kerberos Unit, Integration and Regression Tests found in the Test suites for Apache River, it is desireable to have these tests confirmed before the AR2 Release of Apache River

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

> 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.