[
https://issues.apache.org/jira/browse/DIRKRB-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158687#comment-13158687
]
Stefan Seelmann commented on DIRKRB-83:
---------------------------------------
As mentioned on the ML the unlimited strength jurisdiction policy files are
required for AES256. On Jenkins those are installed and tests pass. Also note
that with JDK 1.6 > update 26 the whole test won't work due to changes in the
internal implementation.
I agree that the two test classes are just a hack. But I just wanted to add
those tests because currently there is no other way to test the Kerberos
server. We just don't have a KRB5 client and neither do I have the time nor the
skills of writing one. So IMO those tests are better than no 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
