IBM, failing KeyStoreSuiteChild.testGetCertificateChainBinary ------------------------------------------------------------- Key: ELY-1680 URL: https://issues.jboss.org/browse/ELY-1680 Project: WildFly Elytron Issue Type: Bug Components: Testsuite Affects Versions: 1.6.1.Final Reporter: Martin Choma Fix For: 1.7.0.CR3 {code} [ERROR] testGetCertificateChainBinary(org.wildfly.security.ldap.KeyStoreSuiteChild) Time elapsed: 0.057 s <<< FAILURE! org.junit.ComparisonFailure: expected:<CN=[firefly_binary], OU=Elytron, O=Elyt...> but was:<CN=[localhost], OU=Elytron, O=Elyt...> at org.wildfly.security.ldap.KeyStoreSuiteChild.testGetCertificateChainBinary(KeyStoreSuiteChild.java:136) at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218) {code} If I switch order of certificates in chain, then test passes. {code} diff --git a/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java b/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java index d8095867a..cda635beb 100644 --- a/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java +++ b/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java @@ -133,8 +133,8 @@ public class KeyStoreSuiteChild { Certificate[] chain = keyStore.getCertificateChain("firefly_binary"); Assert.assertNotNull(chain); Assert.assertEquals(2, chain.length); - Assert.assertEquals("CN=firefly_binary, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[0]).getSubjectDN().toString()); - Assert.assertEquals("CN=localhost, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[1]).getSubjectDN().toString()); + Assert.assertEquals("CN=firefly_binary, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[1]).getSubjectDN().toString()); + Assert.assertEquals("CN=localhost, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[0]).getSubjectDN().toString()); } {code} -For some reason I want able to debug code with -Dmaven.surefire.debug (Breakpoint was never hit) to find out which calls switch the order.- It takes long (5min) for debugger to attach to code.