Several issues related to Kerberos tests in EAP testsuite were reported. Clean-up is needed to keep the testsuite runs stable. The proved-to-be-buggy environment configurations (Java vendor, version, IP stack) should be skipped during testing.
Kerberos errors occur occasionally across all platforms: javax.security.auth.login.LoginException: Checksum failed Examples of logs: RHEL5 && Oracle JDK 1.6 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-rhel/51/RELEASE=6.4.0,jdk=java16_default,label_exp=eap-sustaining%20&&%20RHEL5%20&&%20x86/testReport/ Solaris10 && Oracle JDK 1.7 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-solaris/41/RELEASE=6.4.0,jdk=java17_default,label_exp=eap-sustaining%20&&%20solaris10%20&&%20x86/testReport/
The problem seems to be related to test execution order (therefor it fails intermittently) and also related to used encryption mechanism. Some test running before the failing Kerberos tests screws up the environment, because if single test (or group e.g. -Dtest=*LoginModuleTestCase) is executed the issue doesn't appear. I personally suspect Bouncy Castle library, but it may be some other magic place too. I will submit patch which reverts encryption mechanisms used in krb5.conf to "des-cbc-md5,des3-cbc-sha1-kd". It helps in my local tests.
Verified on EAP 6.4.0.ER3