[JBoss JIRA] (ELY-929) AuthenticationConfiguration uniqueness enhancements
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-929?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-929:
---------------------------------
Fix Version/s: 1.1.0.CR4
(was: 1.1.0.CR3)
> AuthenticationConfiguration uniqueness enhancements
> ---------------------------------------------------
>
> Key: ELY-929
> URL: https://issues.jboss.org/browse/ELY-929
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.CR4
>
>
> Apply some enhancements to AuthenticationConfiguration uniqueness.
> * Add admonishing JavaDoc to {{useCallbackHandler}} to point out the importance of per-identity uniqueness of the callback handler
> The following also may be possible and useful:
> * Modify the {{AuthenticationConfiguration}} process to capture instances for {{Supplier}}-driven components at the time the configuration is used via the {{AuthenticationContextConfigurationClient}}
> * Add a variation of {{useCallbackHandler}} which accepts a {{Supplier<CallbackHandler>}}, or a {{Function<T, CallbackHandler}} and a {{T}}, allowing constructor refs to be given
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1301) Pem.parsePemX509Certificate() hangs on IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-1301?page=com.atlassian.jira.plugin.s... ]
Peter Palaga commented on ELY-1301:
-----------------------------------
ELY-1301 perhaps causes ELY-1292
> Pem.parsePemX509Certificate() hangs on IBM JDK
> ----------------------------------------------
>
> Key: ELY-1301
> URL: https://issues.jboss.org/browse/ELY-1301
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Peter Palaga
> Assignee: Darran Lofthouse
>
> Add a test like this to `PemTest`:
> {code}
> @Test
> public void testParsePemX509CertificateCacert() throws Exception {
> URL url = PemTest.class.getResource("/ca/cacert.pem");
> byte[] bytes = Files.readAllBytes(Paths.get(url.toURI()));
> assertNotNull(Pem.parsePemX509Certificate(CodePointIterator.ofUtf8Bytes(bytes)));
> }
> {code}
> Run the test with IBM JDK
> {code}
> export JAVA_HOME=path/to/ibm/java8
>
> $JAVA_HOME/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160915_0912_B318796
> JIT - tr.r14.java.green_20160818_122998
> GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
> J9CL - 20160915_318796)
> JCL - 20160914_01 based on Oracle jdk8u101-b13
> mvn clean test -Dtest=PemTest#testParsePemX509CertificateCacert
> {code}
> Expected: The test should pass on IBM JDK just as it passes on Oracle/OpenJDK
> Actual: The hangs on IBM JDK
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1301) Pem.parsePemX509Certificate() hangs on IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-1301?page=com.atlassian.jira.plugin.s... ]
Peter Palaga updated ELY-1301:
------------------------------
Description:
Add a test like this to `PemTest`:
{code}
@Test
public void testParsePemX509CertificateCacert() throws Exception {
URL url = PemTest.class.getResource("/ca/cacert.pem");
byte[] bytes = Files.readAllBytes(Paths.get(url.toURI()));
assertNotNull(Pem.parsePemX509Certificate(CodePointIterator.ofUtf8Bytes(bytes)));
}
{code}
Run the test with IBM JDK
{code}
export JAVA_HOME=path/to/ibm/java8
$JAVA_HOME/bin/java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160915_0912_B318796
JIT - tr.r14.java.green_20160818_122998
GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
J9CL - 20160915_318796)
JCL - 20160914_01 based on Oracle jdk8u101-b13
mvn clean test -Dtest=PemTest#testParsePemX509CertificateCacert
{code}
Expected: The test should pass on IBM JDK just as it passes on Oracle/OpenJDK
Actual: The test hangs on IBM JDK
was:
Add a test like this to `PemTest`:
{code}
@Test
public void testParsePemX509CertificateCacert() throws Exception {
URL url = PemTest.class.getResource("/ca/cacert.pem");
byte[] bytes = Files.readAllBytes(Paths.get(url.toURI()));
assertNotNull(Pem.parsePemX509Certificate(CodePointIterator.ofUtf8Bytes(bytes)));
}
{code}
Run the test with IBM JDK
{code}
export JAVA_HOME=path/to/ibm/java8
$JAVA_HOME/bin/java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160915_0912_B318796
JIT - tr.r14.java.green_20160818_122998
GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
J9CL - 20160915_318796)
JCL - 20160914_01 based on Oracle jdk8u101-b13
mvn clean test -Dtest=PemTest#testParsePemX509CertificateCacert
{code}
Expected: The test should pass on IBM JDK just as it passes on Oracle/OpenJDK
Actual: The hangs on IBM JDK
> Pem.parsePemX509Certificate() hangs on IBM JDK
> ----------------------------------------------
>
> Key: ELY-1301
> URL: https://issues.jboss.org/browse/ELY-1301
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Peter Palaga
> Assignee: Darran Lofthouse
>
> Add a test like this to `PemTest`:
> {code}
> @Test
> public void testParsePemX509CertificateCacert() throws Exception {
> URL url = PemTest.class.getResource("/ca/cacert.pem");
> byte[] bytes = Files.readAllBytes(Paths.get(url.toURI()));
> assertNotNull(Pem.parsePemX509Certificate(CodePointIterator.ofUtf8Bytes(bytes)));
> }
> {code}
> Run the test with IBM JDK
> {code}
> export JAVA_HOME=path/to/ibm/java8
>
> $JAVA_HOME/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160915_0912_B318796
> JIT - tr.r14.java.green_20160818_122998
> GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
> J9CL - 20160915_318796)
> JCL - 20160914_01 based on Oracle jdk8u101-b13
> mvn clean test -Dtest=PemTest#testParsePemX509CertificateCacert
> {code}
> Expected: The test should pass on IBM JDK just as it passes on Oracle/OpenJDK
> Actual: The test hangs on IBM JDK
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-534) Some tests fail with ExceptionInInitializerError with JMockit 1.22 for IBM JDK
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-534?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse commented on ELY-534:
--------------------------------------
Another one I am not actually working on ;-)
> Some tests fail with ExceptionInInitializerError with JMockit 1.22 for IBM JDK
> ------------------------------------------------------------------------------
>
> Key: ELY-534
> URL: https://issues.jboss.org/browse/ELY-534
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta6
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Minor
>
> Some tests fail with java.lang.ExceptionInInitializerError on IBM JDK.
> Stacktrace (for OAuth2SecurityRealmTest):
> {code}
> java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.ensureError(J9VMInternals.java:137)
> at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:126)
> at org.wildfly.security.auth.realm.oauth2.OAuth2SecurityRealmTest.configureTokenIntrospectionEndpoint(OAuth2SecurityRealmTest.java:198)
> at org.wildfly.security.auth.realm.oauth2.OAuth2SecurityRealmTest.configureReplayTokenIntrospection(OAuth2SecurityRealmTest.java:188)
> at org.wildfly.security.auth.realm.oauth2.OAuth2SecurityRealmTest.testBasicActiveToken(OAuth2SecurityRealmTest.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> Caused by: java.lang.IllegalStateException: To run on IBM J9 VM, add <IBM SDK>/lib/tools.jar to the runtime classpath (before jmockit), or use -javaagent:/mnt/hudson_workspace/workspace/wildfly-elytron-unit-tests/5fe75d5a/maven-repository/org/jmockit/jmockit/1.22/jmockit-1.22.jar
> at mockit.internal.startup.AgentLoader.loadAgent(AgentLoader.java:49)
> at mockit.internal.startup.Startup.verifyInitialization(Startup.java:172)
> at mockit.MockUp.<clinit>(MockUp.java:94)
> ... 27 more
> {code}
> This is probably only test issue.
> Affected tests:
> org.wildfly.security.auth.realm.oauth2.OAuth2SecurityRealmTest
> org.wildfly.security.sasl.digest.CompatibilityClientTest
> org.wildfly.security.sasl.digest.CompatibilityServerTest
> org.wildfly.security.sasl.entity.EntityTest
> org.wildfly.security.sasl.gssapi.compatibility.BasicAuthTest
> org.wildfly.security.sasl.gssapi.compatibility.BasicConfidenceTest
> org.wildfly.security.sasl.gssapi.compatibility.BasicIntegrityTest
> org.wildfly.security.sasl.gssapi.compatibility.NoServerAuthTest
> org.wildfly.security.sasl.otp.OTPTest
> org.wildfly.security.sasl.scram.ScramClientCompatibilityTest
> org.wildfly.security.sasl.scram.ScramServerCompatibilityTest
> It seems that this issue can be fixed by adding -{{javaagent:$\{USED_MAVEN_REPO\}/org/jmockit/jmockit/1.22/jmockit-1.22.jar}} as argLine option for Maven Surefire Plugin.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months