February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9817) JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file, seems that Elytron uses JSON-P stuff too early

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9817?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9817: ------------------------------------- I think the solution will be for core to temporarily provide it's own JSON-P module that Elytron, or other core components, can rely on. > JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file, seems that Elytron uses JSON-P stuff too early > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9817 > URL: https://issues.jboss.org/browse/WFLY-9817 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Rostislav Svoboda > Assignee: James Perkins > Priority: Critical > > JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file. > Early investigation done by James and Stuart indicates that Elytron uses JSON-P stuff too early and it prevents JSON-P 1.1 activation when ee8.preview.mode property is defined in standalone.xml file. > CCing [~jamezp] [~swd847] [~jason.greene] [~kabirkhan] [~brian.stansberry] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9817) JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file, seems that Elytron uses JSON-P stuff too early

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9817?page=com.atlassian.jira.plugin.... ] James Perkins reassigned WFLY-9817: ----------------------------------- Assignee: James Perkins (was: Jason Greene) > JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file, seems that Elytron uses JSON-P stuff too early > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9817 > URL: https://issues.jboss.org/browse/WFLY-9817 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Rostislav Svoboda > Assignee: James Perkins > Priority: Critical > > JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file. > Early investigation done by James and Stuart indicates that Elytron uses JSON-P stuff too early and it prevents JSON-P 1.1 activation when ee8.preview.mode property is defined in standalone.xml file. > CCing [~jamezp] [~swd847] [~jason.greene] [~kabirkhan] [~brian.stansberry] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9731) The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS

by Petr Jurak (JIRA)

[ https://issues.jboss.org/browse/WFLY-9731?page=com.atlassian.jira.plugin.... ] Petr Jurak updated WFLY-9731: ----------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10829 (was: https://github.com/wildfly/wildfly/pull/10790) > The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9731 > URL: https://issues.jboss.org/browse/WFLY-9731 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Petr Jurak > Assignee: Petr Jurak > > Web service with STS (Picketlink) returns wrong subject with PolicyContext("javax.security.auth.subject.container"). > It seems that configured login modules are not called since SecurityContext was created by SAML2Handler for the same security domain and are skipped because of WFLY-4625. > Reproducer is attached in BZ-1352418. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9788) EJB over HTTP fails with Arrays in Request

by Heiko Lettmann (JIRA)

[ https://issues.jboss.org/browse/WFLY-9788?page=com.atlassian.jira.plugin.... ] Heiko Lettmann commented on WFLY-9788: -------------------------------------- Sorry to say that it still does'nt work. Also tried with wildfly master now. Stack trace here is a little different: Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:129) at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:131) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:203) at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:127) ... 5 more Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:179) ... 6 more How would I submit a test case that ist actually usable by you? Although all I am doing here is to call this: @Stateful @Remote(RemoteCounter.class) public class CounterBean implements RemoteCounter { public List<String> test2(String[] s1, String[] s2) { System.out.println("Hello!"); return null; } } > EJB over HTTP fails with Arrays in Request > ------------------------------------------ > > Key: WFLY-9788 > URL: https://issues.jboss.org/browse/WFLY-9788 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Heiko Lettmann > Attachments: Test.zip > > > I stumbled over the issue WFLY-9573. Then I updated to wildfly-http-client-1.0.9.Final which made a few invocations work. There I discovered another issue. I attached a modified Quickstart version to demonstrate it! > Exception is on the client side: > Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String > at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:128) > at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:130) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String > at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:204) > at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:126) > ... 4 more > Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String > at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:178) > ... 5 more -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3599) Upgrade WildFly Elytron to 1.2.0.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3599: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.2.0.Final Key: WFCORE-3599 URL: https://issues.jboss.org/browse/WFCORE-3599 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 4.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9820) JavaMail 1.6 Support

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9820?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9820: ----------------------------- Parent: (was: WFLY-6455) Issue Type: Feature Request (was: Sub-task) > JavaMail 1.6 Support > -------------------- > > Key: WFLY-9820 > URL: https://issues.jboss.org/browse/WFLY-9820 > Project: WildFly > Issue Type: Feature Request > Components: Mail > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 7.2.0.EL12 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9820) JavaMail 1.6 Support

by Kabir Khan (JIRA)

Kabir Khan created WFLY-9820: -------------------------------- Summary: JavaMail 1.6 Support Key: WFLY-9820 URL: https://issues.jboss.org/browse/WFLY-9820 Project: WildFly Issue Type: Sub-task Components: Mail Reporter: David Lloyd Assignee: Tomaz Cerar Fix For: 12.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1510) Bearer authentication sends 401 to unprotected resources when no auth in progress

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/ELY-1510?page=com.atlassian.jira.plugin.s... ] Martin Mazanek updated ELY-1510: -------------------------------- Summary: Bearer authentication sends 401 to unprotected resources when no auth in progress (was: Bearer authentication sends 401 to unportected resources when no auth in progress) > Bearer authentication sends 401 to unprotected resources when no auth in progress > --------------------------------------------------------------------------------- > > Key: ELY-1510 > URL: https://issues.jboss.org/browse/ELY-1510 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Mazanek > Assignee: Martin Mazanek > > If you try to access unprotected resource with no Authorization header, BearerTokenAuthenticationMechanism sees it as a failed authentication so 401 is sent. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1514) Release WildFly Elytron 1.2.0.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1514: ------------------------------------- Summary: Release WildFly Elytron 1.2.0.Final Key: ELY-1514 URL: https://issues.jboss.org/browse/ELY-1514 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta13 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1513) Verify public API signatures during build.

by Ilia Vassilev (JIRA)

Ilia Vassilev created ELY-1513: ---------------------------------- Summary: Verify public API signatures during build. Key: ELY-1513 URL: https://issues.jboss.org/browse/ELY-1513 Project: WildFly Elytron Issue Type: Enhancement Components: Build Reporter: Ilia Vassilev Fix For: 2.0.0.Alpha1 This task will involve adding the ability to generate a signature for a specific version and verify them during the build - we only want this to apply to packages identified as public API. Animal Sniffer seems a good candidate http://www.mojohaus.org/animal-sniffer/ Generation of a signature we can likely make on-demand as we only really need that at the point we tag a release. We would definitely want checking to run for CI PR processing but can decide if all builds should be checking with an option to disable or all disabled with an option to enable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018