[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet edited comment on JBIDE-24873 at 9/18/17 10:40 AM: --------------------------------------------------------------------- When we compare what is registered for security providers in a test to what is effectively registered in a real JBDS we see this : (quoting [~rob.stryker]) {code:java} When tracing through SecurityProviderSaslClientFactory to locate differences between a working usecase (standalone java app)_ and failing usecase (mvn test suite), I discovered that inside createSaslClient(etc)... Successful standalone test: 1 provider, named WildFlyElytronProvider - 185 services of various names Failing mvn / unit test case: 9 providers: - SUN (30 services) - SunRSASian (9 services) - SunEC (10 services) - SunJSSE (16 services) - SunJCE (131 services) - SunJGSS (2 services) - SunSASL (10 services) - XMLDSIG (13 services) - SunPCSC (1 service) When the initial loop is over, checking clientFactoryList reveals: Successful case: 27 Pair objects (returns LocalUserClient) Failing mvn case: 6 pairs (returns DigestMD5Client) Real life JBDS: 27 Pair objects (returns LocalUserClient) {code} So it seems this is a configuration issue in how the testsuite runs; Please note that the testsuite use artifacts from a maven repo instead of a real JBDS installation. So this doesn't seem to be a real user problem but more a configuration issue in this particular test case which isn't worth investigating further as the current JBDS master is running just fine in the test suite. was (Author: ehugonnet): When we compare what is registered for security providers in a test to what is effectively registered in a real JBDS we see this : (quoting [~rob.stryker]) {code:java} When tracing through SecurityProviderSaslClientFactory to locate differences between a working usecase (standalone java app)_ and failing usecase (mvn test suite), I discovered that inside createSaslClient(etc)... Successful standalone test: 1 provider, named WildFlyElytronProvider - 185 services of various names Failing mvn / unit test case: 9 providers: - SUN (30 services) - SunRSASian (9 services) - SunEC (10 services) - SunJSSE (16 services) - SunJCE (131 services) - SunJGSS (2 services) - SunSASL (10 services) - XMLDSIG (13 services) - SunPCSC (1 service) When the initial loop is over, checking clientFactoryList reveals: Successful case: 27 Pair objects (returns LocalUserClient) Failing mvn case: 6 pairs (returns DigestMD5Client) Real life JBDS: 27 Pair objects (returns LocalUserClient) {code} So it seems this is a configuration issue in how the testsuite runs; Please note that the testsuite use artifacts from a maven repo instead of a real JBDS installation. Maybe it is missing something in startup / config. -- This message was sent by Atlassian JIRA (v7.2.3#72005)