[JBoss JIRA] (WFLY-13059) org.apache.ws.security exports Jasypt
by Philippe Marschall (Jira)
Philippe Marschall created WFLY-13059:
-----------------------------------------
Summary: org.apache.ws.security exports Jasypt
Key: WFLY-13059
URL: https://issues.redhat.com/browse/WFLY-13059
Project: WildFly
Issue Type: Bug
Components: XML Frameworks
Reporter: Philippe Marschall
Assignee: Brian Stansberry
The {{org.apache.ws.security}} module contains the Jasypt JAR and exports it. Jasypt is only used internally by {{org.apache.wss4j.common.crypto.JasyptPasswordEncryptor}} and not used externally.
Our application has a dependency on {{org.jboss.ws.cxf.jbossws-cxf-client}} which has an exported dependency on {{org.apache.ws.security}} which exports Jasypt. As a consequence the Jasypt from the {{org.apache.ws.security}} module is used instead of the Jasypt from our application.
We would be willing to work on a patch. We see two possible options:
# Introduce a dedicated Jasypt module and make {{org.apache.ws.security}} depend on it without exporting it
# Add a resource filter to the {{org.apache.ws.security}} module like this {code}
<exports>
<exclude path="org/jasypt/**"/>
</exports>
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-13056) Unexpected Error instead of SOAPFaultException when using IBM JDK and SecurityManager
by Francesco Marchioni (Jira)
[ https://issues.redhat.com/browse/WFLY-13056?page=com.atlassian.jira.plugi... ]
Francesco Marchioni updated WFLY-13056:
---------------------------------------
Attachment: surefire-reports.zip
> Unexpected Error instead of SOAPFaultException when using IBM JDK and SecurityManager
> -------------------------------------------------------------------------------------
>
> Key: WFLY-13056
> URL: https://issues.redhat.com/browse/WFLY-13056
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager, Test Suite
> Affects Versions: 19.0.0.Beta1
> Reporter: Francesco Marchioni
> Priority: Major
> Attachments: surefire-reports.zip
>
>
> When using IBM JDK with SecurityManager option, a programmatic Fault returns a different Exception than a SOAPFaultException
> {code:java}
> @Test
> public void testHelloError() {
> try {
> proxy.helloError("Fault for test purpose");
> Assert.fail("This should throw a SOAPFaultException");
> } catch (SOAPFaultException ex) {
> SOAPFault fault = ex.getFault();
> Assert.assertEquals("Fault for test purpose", fault.getFaultString());
> //....
> }
> }
> {code}
> Exception:
> {code:java}
> org.junit.ComparisonFailure: expected:<[Fault for test purpose]> but was:<[WFLYEJB0442: Unexpected Error]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.as.test.integration.ws.basic.BasicTests.testHelloError(BasicTests.java:69)
> {code}
> Affected Test in the AS Testsuite:
> org/jboss/as/test/integration/ws/basic/EJBEndpointTestCase
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-5004) Select first cell of Test Scenario
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5004:
-----------------------------------
Summary: Select first cell of Test Scenario
Key: DROOLS-5004
URL: https://issues.redhat.com/browse/DROOLS-5004
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Affects Versions: 7.33.0.Final
Reporter: Jozef Marko
Assignee: Yeser Amer
Once a Test Scenario file is opened, user is not able to use keyboard to navigate trough the grid. We should fix this by selecting the:
- First description cell in case of the Model tab
- First data cell in case of Background tab
The behavior described above will align behavior of Test Scenario and DMN editors.
h3. Acceptance criteria
- User can use keyboard right afterwards opening Test Scenario without need to click to canvas
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-13056) Unexpected Error instead of SOAPFaultException when using IBM JDK and SecurityManager
by Francesco Marchioni (Jira)
[ https://issues.redhat.com/browse/WFLY-13056?page=com.atlassian.jira.plugi... ]
Francesco Marchioni updated WFLY-13056:
---------------------------------------
Description:
When using IBM JDK with SecurityManager option, a programmatic Fault returns a different Exception than a SOAPFaultException
{code:java}
@Test
public void testHelloError() {
try {
proxy.helloError("Fault for test purpose");
Assert.fail("This should throw a SOAPFaultException");
} catch (SOAPFaultException ex) {
SOAPFault fault = ex.getFault();
Assert.assertEquals("Fault for test purpose", fault.getFaultString());
//....
}
}
{code}
Exception:
{code:java}
org.junit.ComparisonFailure: expected:<[Fault for test purpose]> but was:<[WFLYEJB0442: Unexpected Error]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jboss.as.test.integration.ws.basic.BasicTests.testHelloError(BasicTests.java:69)
{code}
Affected Test in the AS Testsuite:
org/jboss/as/test/integration/ws/basic/EJBEndpointTestCase
was:
When using IBM JDK with SecurityManager option, a programmatic Fault returns a different Exception than a SOAPFaultException
{code:java}
@Test
public void testHelloError() {
try {
proxy.helloError("Fault for test purpose");
Assert.fail("This should throw a SOAPFaultException");
} catch (SOAPFaultException ex) {
SOAPFault fault = ex.getFault();
Assert.assertEquals("Fault for test purpose", fault.getFaultString());
//....
}
}
{code}
Exception:
{code:java}
org.junit.ComparisonFailure: expected:<[Fault for test purpose]> but was:<[WFLYEJB0442: Unexpected Error]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jboss.as.test.integration.ws.basic.BasicTests.testHelloError(BasicTests.java:69)
{code}
Affected Test in the AS Testsuite:
org.jboss.as.test.integration.ws.basic.BasicTests.testHelloError
> Unexpected Error instead of SOAPFaultException when using IBM JDK and SecurityManager
> -------------------------------------------------------------------------------------
>
> Key: WFLY-13056
> URL: https://issues.redhat.com/browse/WFLY-13056
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager, Test Suite
> Affects Versions: 19.0.0.Beta1
> Reporter: Francesco Marchioni
> Priority: Major
> Attachments: surefire-reports.zip
>
>
> When using IBM JDK with SecurityManager option, a programmatic Fault returns a different Exception than a SOAPFaultException
> {code:java}
> @Test
> public void testHelloError() {
> try {
> proxy.helloError("Fault for test purpose");
> Assert.fail("This should throw a SOAPFaultException");
> } catch (SOAPFaultException ex) {
> SOAPFault fault = ex.getFault();
> Assert.assertEquals("Fault for test purpose", fault.getFaultString());
> //....
> }
> }
> {code}
> Exception:
> {code:java}
> org.junit.ComparisonFailure: expected:<[Fault for test purpose]> but was:<[WFLYEJB0442: Unexpected Error]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.as.test.integration.ws.basic.BasicTests.testHelloError(BasicTests.java:69)
> {code}
> Affected Test in the AS Testsuite:
> org/jboss/as/test/integration/ws/basic/EJBEndpointTestCase
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-13057) Unexpected status of WSBACoordinator when using IBM JDK and SecurityManager
by Francesco Marchioni (Jira)
[ https://issues.redhat.com/browse/WFLY-13057?page=com.atlassian.jira.plugi... ]
Francesco Marchioni updated WFLY-13057:
---------------------------------------
Attachment: surefire-reports.zip
> Unexpected status of WSBACoordinator when using IBM JDK and SecurityManager
> ---------------------------------------------------------------------------
>
> Key: WFLY-13057
> URL: https://issues.redhat.com/browse/WFLY-13057
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager, Test Suite
> Affects Versions: 19.0.0.Beta1
> Reporter: Francesco Marchioni
> Assignee: Stefan Guilhen
> Priority: Major
> Attachments: surefire-reports.zip
>
>
> An unexpected status of WSBACoordinator causes failures in the following tests when using IBM JDK 1.8 and Security Manager
> {code:java}
> [ERROR] Failures:
> [ERROR] BACoordinatorCompletionTestCase.testWSBACoordinatorCannotComplete:133->assertEventLogClient1:193->BaseFunctionalTest.assertEventLog:85 Another status order expected for the bacoordinator_completition_service1 expected:<[CANCEL]> but was:<null>
> [ERROR] BACoordinatorCompletionTestCase.testWSBACoordinatorCompletionFailToComplete:184->assertEventLogClient1:193->BaseFunctionalTest.assertEventLog:85 Another status order expected for the bacoordinator_completition_service1 expected:<[COMPLETE, CONFIRM_COMPLETED, COMPENSATE]> but was:<null>
> {code}
> Affected Tests in the AS Testsuite:
> org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase#testWSBACoordinatorCannotComplete
> org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase#testWSBACoordinatorCompletionFailToComplete
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-13058) JAXBEncoderDecoder failure when using IBM JDK and SecurityManager
by Francesco Marchioni (Jira)
[ https://issues.redhat.com/browse/WFLY-13058?page=com.atlassian.jira.plugi... ]
Francesco Marchioni updated WFLY-13058:
---------------------------------------
Attachment: surefire-reports.zip
> JAXBEncoderDecoder failure when using IBM JDK and SecurityManager
> -----------------------------------------------------------------
>
> Key: WFLY-13058
> URL: https://issues.redhat.com/browse/WFLY-13058
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager, Test Suite
> Affects Versions: 19.0.0.Beta1
> Reporter: Francesco Marchioni
> Priority: Major
> Attachments: surefire-reports.zip
>
>
> When running the org.jboss.as.test.xts.suspend.wsba.BusinessActivitySuspendTestCase with IBM JDK 1.8 with Security Manager, an issue is raised by the JAXBEncoderDecoder:
> {code:java}
> [INFO] Running org.jboss.as.test.xts.suspend.wsba.BusinessActivitySuspendTestCase
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.351 s <<< FAILURE! - in org.jboss.as.test.xts.suspend.wsba.BusinessActivitySuspendTestCase
> [ERROR] testCommitAfterSuspend(org.jboss.as.test.xts.suspend.wsba.BusinessActivitySuspendTestCase) Time elapsed: 2.313 s <<< ERROR!
> java.lang.Exception: ARJUNA045061: No termination context!
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:83)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:437)
> at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshallException(JAXBEncoderDecoder.java:545)
> at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:689)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-13055) Permission check failed when using SecurityManager with IBM JDK
by Francesco Marchioni (Jira)
[ https://issues.redhat.com/browse/WFLY-13055?page=com.atlassian.jira.plugi... ]
Francesco Marchioni updated WFLY-13055:
---------------------------------------
Attachment: surefire-reports.zip
> Permission check failed when using SecurityManager with IBM JDK
> ---------------------------------------------------------------
>
> Key: WFLY-13055
> URL: https://issues.redhat.com/browse/WFLY-13055
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager, Test Suite
> Affects Versions: 19.0.0.Beta1
> Reporter: Francesco Marchioni
> Priority: Major
> Attachments: surefire-reports.zip
>
>
> When using IBM JDK in combination with SecurityManager a Permission check fails for classes using packages com.sun.org.apache.xerces.internal.jaxp
> {code:java}
> INFO] Running org.jboss.as.test.integration.ws.basic.PojoEndpointTestCase
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.002 s <<< FAILURE! - in org.jboss.as.test.integration.ws.basic.PojoEndpointTestCase
> [ERROR] testHelloError(org.jboss.as.test.integration.ws.basic.PojoEndpointTestCase) Time elapsed: 0.188 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[Fault for test purpose]> but was:<[Provider com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl could not be instantiated: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "accessClassInPackage.com.sun.org.apache.xerces.internal.jaxp")" in code source "(vfs:/content/jaxws-basic-pojo.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.jaxws-basic-pojo.war" from Service Module Loader")]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.as.test.integration.ws.basic.BasicTests.testHelloError(BasicTests.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> {code}
> Affected Tests in the AS Testsuite:
> org.jboss.as.test.integration.ws.basic.PojoEndpointTestCase#testHelloError
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATVoteReadOnly
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATClientRollback
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATVoteRollback
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATApplicationException
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATSimple
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATSingleSimple
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATVoteRollbackPrePrepare
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATApplicationExceptionCommit
> org.jboss.as.test.xts.wsat.client.ATTestCase#testWSATRollbackOnly
> org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase#testWSBACoordinatorSimple
> org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase#testWSBACoordinatorSingle
> org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase#testWSBACoordinatorApplicationException
> org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase#testWSBACoordinatorClientCancel
> org.jboss.as.test.txbridge.fromjta.BridgeFromJTATestCase#testRollback
> org.jboss.as.test.txbridge.fromjta.BridgeFromJTATestCase#testCommit
> org.jboss.as.test.xts.suspend.wsat.AtomicTransactionSuspendTestCase#testRollbackAfterSuspend
> org.jboss.as.test.xts.suspend.wsat.AtomicTransactionSuspendTestCase#testRemoteServiceAfterSuspend
> org.jboss.as.test.xts.suspend.wsat.AtomicTransactionSuspendTestCase#testCommitAfterSuspend
> org.jboss.as.test.xts.annotation.client.CompensatableTestCase#testNoTransaction
> org.jboss.as.test.xts.annotation.client.CompensatableTestCase#testActiveTransaction
> org.jboss.as.test.xts.annotation.client.TransactionalTestCase#testNoTransaction
> org.jboss.as.test.xts.annotation.client.TransactionalTestCase#testActiveTransaction
> org.jboss.as.test.xts.suspend.wsba.BusinessActivitySuspendTestCase#testRemoteServiceAfterSuspend
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months