[JBoss JIRA] (WFLY-13057) Unexpected status of WSBACoordinator when using IBM JDK and SecurityManager
by Stefan Guilhen (Jira)
[ https://issues.redhat.com/browse/WFLY-13057?page=com.atlassian.jira.plugi... ]
Stefan Guilhen reassigned WFLY-13057:
-------------------------------------
Assignee: (was: Stefan Guilhen)
> 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
> 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)
4 years, 4 months
[JBoss JIRA] (WFLY-9129) Setting env var SECMGR=true no longer works
by Stefan Guilhen (Jira)
[ https://issues.redhat.com/browse/WFLY-9129?page=com.atlassian.jira.plugin... ]
Stefan Guilhen reassigned WFLY-9129:
------------------------------------
Assignee: (was: Stefan Guilhen)
> Setting env var SECMGR=true no longer works
> -------------------------------------------
>
> Key: WFLY-9129
> URL: https://issues.redhat.com/browse/WFLY-9129
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager
> Affects Versions: 10.0.0.Final, 10.1.0.Final, 11.0.0.Alpha1
> Reporter: r searls
> Priority: Major
>
> Setting env var SECMGR=true is suppose to enable the security manager.
> It is not working. I've tried the following and none of them enable
> the security manager.
> export SECMGR=true;
> on the cmd-line -DSECMGR=true
> edit bin/standalone.conf and uncomment line SECMGR="true"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months
[JBoss JIRA] (WFLY-13059) org.apache.ws.security exports Jasypt
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13059?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-13059:
-----------------------------------------
[~jim.ma] I'm passing this one over to you as this module only seems relevant to Webservices.
The difficulty I see here is the org.apache.ws.security module is not a private one so removing resources from it is a breaking API change.
The org.jboss.as.webservices.server.integration module also depends on and exports org.apache.ws.security, so if jasypt was no longer available via that module that would also be a breaking change. That module is private though so that only matters if projects that can layer on top of WildFly like keycloak would care. (That module could also export any new jasypt module if that is what happens.)
> org.apache.ws.security exports Jasypt
> -------------------------------------
>
> Key: WFLY-13059
> URL: https://issues.redhat.com/browse/WFLY-13059
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Reporter: Philippe Marschall
> Assignee: Jim Ma
> Priority: Major
>
> 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)
4 years, 4 months
[JBoss JIRA] (WFLY-13059) org.apache.ws.security exports Jasypt
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13059?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-13059:
---------------------------------------
Component/s: Web Services
(was: XML Frameworks)
Assignee: Jim Ma (was: Brian Stansberry)
> org.apache.ws.security exports Jasypt
> -------------------------------------
>
> Key: WFLY-13059
> URL: https://issues.redhat.com/browse/WFLY-13059
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Reporter: Philippe Marschall
> Assignee: Jim Ma
> Priority: Major
>
> 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)
4 years, 4 months
[JBoss JIRA] (DROOLS-5005) [DMN Designer] Code Completion - Esc doesn't work properly when there's no content in the literal expression
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5005?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-5005:
------------------------------------
Description:
Esc doesn't work properly when there's no content in the literal expression.
*Steps to reproduce:*
- Open the literal expression editor
- Start the edit mode
- Press Ctrl+Space
- See the suggestions
- Press Esc - *actual: suggestions don't disappear* / *expected: suggestions disappears*
was:
Esc doesn't work properly when there's no content in the literal expression.
*Steps to reproduce:*
- Open the literal expression editor
- Start the edit mode
- Press Ctrl+Space
- See the suggestions
- Press Esc - suggestions don't disappear / expected: suggestions disappears
> [DMN Designer] Code Completion - Esc doesn't work properly when there's no content in the literal expression
> ------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5005
> URL: https://issues.redhat.com/browse/DROOLS-5005
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Esc doesn't work properly when there's no content in the literal expression.
> *Steps to reproduce:*
> - Open the literal expression editor
> - Start the edit mode
> - Press Ctrl+Space
> - See the suggestions
> - Press Esc - *actual: suggestions don't disappear* / *expected: suggestions disappears*
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months