[JBoss JIRA] (WFLY-12730) JBossWS tests UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after ugrade to CXF 3.3.x in WFLY
by Jim Ma (Jira)
[ https://issues.jboss.org/browse/WFLY-12730?page=com.atlassian.jira.plugin... ]
Jim Ma updated WFLY-12730:
--------------------------
Description: The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). These failures after CXF upgrades to 3.3.x in WFLY. (was: The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). These failures happens CXF upgrades to 3.3.x. )
> JBossWS tests UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after ugrade to CXF 3.3.x in WFLY
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12730
> URL: https://issues.jboss.org/browse/WFLY-12730
> Project: WildFly
> Issue Type: Enhancement
> Affects Versions: 18.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). These failures after CXF upgrades to 3.3.x in WFLY.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (WFLY-12730) JBossWS tests UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after ugrade to CXF 3.3.x in WFLY
by Jim Ma (Jira)
[ https://issues.jboss.org/browse/WFLY-12730?page=com.atlassian.jira.plugin... ]
Jim Ma updated WFLY-12730:
--------------------------
Summary: JBossWS tests UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after ugrade to CXF 3.3.x in WFLY (was: UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x)
> JBossWS tests UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after ugrade to CXF 3.3.x in WFLY
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12730
> URL: https://issues.jboss.org/browse/WFLY-12730
> Project: WildFly
> Issue Type: Enhancement
> Affects Versions: 18.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). These failures happens CXF upgrades to 3.3.x.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (WFLY-12730) UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x
by Jim Ma (Jira)
[ https://issues.jboss.org/browse/WFLY-12730?page=com.atlassian.jira.plugin... ]
Jim Ma updated WFLY-12730:
--------------------------
Description: The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). These failures happens CXF upgrades to 3.3.x. (was: The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem).
The breaking commit is https://github.com/jbossws/jbossws-cxf/commit/149c0fc8d19e566541d919e73b6...
To reproduce:
{code:java}
# last commit that passes
git checkout fbdbe55e6ff686cad85be6552e1139efb87645f8
mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCaseUsernameAuthorizationDigestTestCase, -DadditionalGroovyScriptSuffix=-elytron
# fails
git checkout 149c0fc8d19e566541d919e73b608ae53ca3fefb
mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase -DadditionalGroovyScriptSuffix=-elytron
# passes without elytron configuration
mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase
{code}
)
> UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12730
> URL: https://issues.jboss.org/browse/WFLY-12730
> Project: WildFly
> Issue Type: Enhancement
> Affects Versions: 18.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Priority: Critical
> Fix For: 19.0.0.Beta1
>
>
> The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). These failures happens CXF upgrades to 3.3.x.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (WFLY-12730) UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x
by Jim Ma (Jira)
[ https://issues.jboss.org/browse/WFLY-12730?page=com.atlassian.jira.plugin... ]
Jim Ma moved JBWS-4195 to WFLY-12730:
-------------------------------------
Project: WildFly (was: JBoss Web Services)
Key: WFLY-12730 (was: JBWS-4195)
Issue Type: Enhancement (was: Bug)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: 18.0.0.Final
(was: jbossws-cxf-5.3.0.Final)
> UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after upgrade to CXF 3.3.x
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12730
> URL: https://issues.jboss.org/browse/WFLY-12730
> Project: WildFly
> Issue Type: Enhancement
> Affects Versions: 18.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Priority: Critical
>
> The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem).
> The breaking commit is https://github.com/jbossws/jbossws-cxf/commit/149c0fc8d19e566541d919e73b6...
> To reproduce:
> {code:java}
> # last commit that passes
> git checkout fbdbe55e6ff686cad85be6552e1139efb87645f8
> mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCaseUsernameAuthorizationDigestTestCase, -DadditionalGroovyScriptSuffix=-elytron
> # fails
> git checkout 149c0fc8d19e566541d919e73b608ae53ca3fefb
> mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase -DadditionalGroovyScriptSuffix=-elytron
> # passes without elytron configuration
> mvn clean verify -Pwildfly1600 -pl :jbossws-cxf-specific-tests -am -Dtest=UsernameAuthorizationTestCase,UsernameAuthorizationDigestTestCase
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (WFLY-11679) Remove org.jboss.metadata module
by Hynek Mlnařík (Jira)
[ https://issues.jboss.org/browse/WFLY-11679?page=com.atlassian.jira.plugin... ]
Hynek Mlnařík commented on WFLY-11679:
--------------------------------------
[~brian.stansberry] [~kabirkhan] Keycloak dependencies have been updated to refer to {{org.jboss.metadata.common}} and {{org.jboss.metadata.web}} directly.
> Remove org.jboss.metadata module
> --------------------------------
>
> Key: WFLY-11679
> URL: https://issues.jboss.org/browse/WFLY-11679
> Project: WildFly
> Issue Type: Sub-task
> Components: Class Loading, Clustering
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Minor
>
> Not urgent, just something I noticed when looking at https://github.com/wildfly/wildfly/pull/12014/.
> The org.jboss.metadata module just depends on and exports a bunch of other ones. It's jboss-api=private and It's only use within Wildfly is org.wildfly.extension.clustering.singleton which could presumably depend directly on what it needs.
> We'd want to check some with dependent projects in case they use it and do any removal fairly early in a release cycle.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (WFLY-12725) ajp huge header
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12725?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-12725:
---------------------------------------
Component/s: Web (Undertow)
Assignee: Flavia Rainone (was: Brian Stansberry)
> ajp huge header
> ---------------
>
> Key: WFLY-12725
> URL: https://issues.jboss.org/browse/WFLY-12725
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 18.0.0.Final
> Environment: windows7
> Reporter: zai xuan
> Assignee: Flavia Rainone
> Priority: Major
> Labels: headers, long
>
> There are long headers in the AJP connection, resulting in errors.
> ++++++++++++++++++++
> 12:44:37,327 ERROR [io.undertow.request] (default I/O-1) UT005001: An exception
> occurred processing the request: java.lang.ArrayIndexOutOfBoundsException: 16
> at io.undertow.server.protocol.ajp.AjpRequestParser.headers(AjpRequestPa
> rser.java:490)
> at io.undertow.server.protocol.ajp.AjpRequestParser.parseString(AjpReque
> stParser.java:536)
> at io.undertow.server.protocol.ajp.AjpRequestParser.parse(AjpRequestPars
> er.java:353)
> at io.undertow.server.protocol.ajp.AjpReadListener.handleEvent(AjpReadLi
> stener.java:169)
> at io.undertow.server.protocol.ajp.AjpReadListener.handleEvent(AjpReadLi
> stener.java:56)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java
> :92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(R
> eadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> ++++++++++++++++++++
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12729) [18.0.x] Session passivation event can deadlock if it attempts write operations on a session
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12729?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12729:
------------------------------------
Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12705)
> [18.0.x] Session passivation event can deadlock if it attempts write operations on a session
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-12729
> URL: https://issues.jboss.org/browse/WFLY-12729
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 18.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 18.0.1.Final
>
>
> Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes.
> In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years