directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRKRB-83) Fix test failures due to lack of AES256 on default Ubuntu JVM and remove @Ignores in tests
Date Tue, 29 Nov 2011 00:23:40 GMT

    [ https://issues.apache.org/jira/browse/DIRKRB-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158965#comment-13158965
] 

Emmanuel Lecharny commented on DIRKRB-83:
-----------------------------------------

The tests are working with JDK 1.6 update 26 : I fixed them.

Is there a way to check that AES256 is present before starting the tests ?
                
> Fix test failures due to lack of AES256 on default Ubuntu JVM and remove @Ignores in
tests
> ------------------------------------------------------------------------------------------
>
>                 Key: DIRKRB-83
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-83
>             Project: Directory Kerberos
>          Issue Type: Bug
>    Affects Versions: 2.0.0-RC2
>         Environment: Linux stein 3.0.0-13-generic #22-Ubuntu SMP Wed Nov 2 13:27:26 UTC
2011 x86_64 x86_64 x86_64 GNU/Linux
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=11.10
> DISTRIB_CODENAME=oneiric
> DISTRIB_DESCRIPTION="Ubuntu 11.10"
> Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
> Maven home: /opt/tools/maven/default
> Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.0.0-13-generic", arch: "amd64", family: "unix"
>            Reporter: Alex Karasulu
>            Priority: Minor
>
> Kerberos tests failing for AES256 encryption with the following errors:
> javax.security.auth.login.LoginException: No supported encryption types listed in default_tkt_enctypes
> Temporarily will ignore the following failing tests in these files until we can figure
out exactly what's causing this issue. PAM and I tried a few things with the Krb5.conf file
but that did nothing and now this will cause issues for us on this platform until we have
a reliable solution. This jira issue is to get back to a fix and revert these changes with
a real solution to this problem.  
> kerberos-test/src/test/java/org/apache/directory/server/kerberos/kdc/KerberosTcpITest.java
>   testObtainTickets_AES256() 
> kerberos-test/src/test/java/org/apache/directory/server/kerberos/kdc/KerberosUdpITest.java
>   testObtainTickets_AES256() 
> IMHO we should just stop using the login module because it's a hack. We need a real KRB5
client API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message