[JBoss JIRA] (WFLY-2399) org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase fails
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-2399?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-2399:
-------------------------------------
Assignee: Jeff Zhang (was: Stefano Maestri)
> org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase fails
> --------------------------------------------------------------------
>
> Key: WFLY-2399
> URL: https://issues.jboss.org/browse/WFLY-2399
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA, Test Suite
> Affects Versions: 8.0.0.Beta1
> Environment: Solaris SPARC 10, Oracle Java 1.7.0_45
> Reporter: Frank Langelage
> Assignee: Jeff Zhang
> Attachments: org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase-output.txt, org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase.txt
>
>
> Running a build of current sources with complete testsuite this test is failing with
> testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase): expected:<1> but was:<2>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (DROOLS-355) Do not import com.sun.tools.xjc in drools-core and drools-compiler
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-355:
---------------------------------------
Summary: Do not import com.sun.tools.xjc in drools-core and drools-compiler
Key: DROOLS-355
URL: https://issues.jboss.org/browse/DROOLS-355
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Final
Reporter: Geoffrey De Smet
Assignee: Mario Fusco
By importing com.sun.tools.xjc, 3 problems arise:
* OSGi and Karaf trip over it.
{code}
[WARNING] No export found to match com.sun.tools.xjc (imported by mvn:org.drools/drools-core/6.0.0.Final)
{code}
* JDK 9 will break any java app that uses com.sun.* classes. See Mark Reinhold's Jigsaw presentation at devoxxBE 2013.
* IBM JDK's etc don't have com.sun.* classes. Why don't they trip over this?
Why do we have those imports in the first place? Looks like code for old JAXB code - which is hopefully stale now.
Where do we use it?
{code}
Targets
String 'com.sun.tools.xjc'
Found usages (38 usages found)
drools-compiler (7 usages found)
/home/gdesmet/projects/jboss/droolsjbpm/drools/drools-compiler (1 usage found)
pom.xml (1 usage found)
(246: 15) com.sun.tools.xjc.*;resolution:=optional,
org.drools.compiler.builder.impl (1 usage found)
KnowledgeBuilderFactoryServiceImpl.java (1 usage found)
(18: 8) import com.sun.tools.xjc.Options;
org.drools.compiler.runtime.pipeline.impl (5 usages found)
DroolsJaxbHelperProviderImpl.java (5 usages found)
(77: 8) import com.sun.tools.xjc.BadCommandLineException;
(78: 8) import com.sun.tools.xjc.ErrorReceiver;
(79: 8) import com.sun.tools.xjc.ModelLoader;
(80: 8) import com.sun.tools.xjc.Options;
(81: 8) import com.sun.tools.xjc.model.Model;
drools-core (2 usages found)
org.drools.core.builder.conf.impl (2 usages found)
JaxbConfigurationImpl.java (2 usages found)
(28: 8) import com.sun.tools.xjc.Language;
(34: 8) import com.sun.tools.xjc.Options;
kie-internal (6 usages found)
/home/gdesmet/projects/jboss/droolsjbpm/droolsjbpm-knowledge/kie-internal (1 usage found)
pom.xml (1 usage found)
(27: 15) com.sun.tools.xjc;resolution:=optional,
org.kie.internal.builder (3 usages found)
JaxbConfiguration.java (1 usage found)
(23: 8) import com.sun.tools.xjc.Options;
KnowledgeBuilderFactory.java (1 usage found)
(24: 8) import com.sun.tools.xjc.Options;
KnowledgeBuilderFactoryService.java (1 usage found)
(24: 8) import com.sun.tools.xjc.Options;
org.kie.internal.builder.help (2 usages found)
DroolsJaxbHelperProvider.java (1 usage found)
(29: 8) import com.sun.tools.xjc.Options;
KnowledgeBuilderHelper.java (1 usage found)
(30: 8) import com.sun.tools.xjc.Options;
knowledge-api (8 usages found)
org.drools.builder (3 usages found)
JaxbConfiguration.java (1 usage found)
(21: 8) import com.sun.tools.xjc.Options;
KnowledgeBuilderFactory.java (1 usage found)
(24: 8) import com.sun.tools.xjc.Options;
KnowledgeBuilderFactoryService.java (1 usage found)
(24: 8) import com.sun.tools.xjc.Options;
org.drools.builder.help (3 usages found)
DroolsJaxbHelperProvider.java (1 usage found)
(29: 8) import com.sun.tools.xjc.Options;
KnowledgeBuilderHelper.java (2 usages found)
(32: 8) import com.sun.tools.xjc.Language;
(33: 8) import com.sun.tools.xjc.Options;
org.drools.impl (1 usage found)
KnowledgeBuilderFactoryServiceImpl.java (1 usage found)
(16: 8) import com.sun.tools.xjc.Options;
org.drools.impl.adapters (1 usage found)
JaxbConfigurationAdapter.java (1 usage found)
(3: 8) import com.sun.tools.xjc.Options;
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JGRP-1487) AUTH: X509Token Authentication is vulnerable to replay attacks
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/JGRP-1487?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated JGRP-1487:
--------------------------------
Labels: (was: 620)
> AUTH: X509Token Authentication is vulnerable to replay attacks
> --------------------------------------------------------------
>
> Key: JGRP-1487
> URL: https://issues.jboss.org/browse/JGRP-1487
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.0.9
> Reporter: sreenivas chinimilli
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> In the implementation of X509Token Authentication
> The auth_value is enrypted with the certificate within the keystore and
> during verification encrypted auth value is decrypted with the private key
> compared against the orignial auth value.
> This implementation is prone to replay attacks, that is
> any user with out having any knowledge of the auth value can join the group
> by replaying the enrypted auth value captured in earlier sessions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JGRP-1722) Improve performance of ENCRYPT protocol
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/JGRP-1722?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated JGRP-1722:
--------------------------------
Labels: (was: 620)
> Improve performance of ENCRYPT protocol
> ---------------------------------------
>
> Key: JGRP-1722
> URL: https://issues.jboss.org/browse/JGRP-1722
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 3.4
> Reporter: Martin Gencur
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> A stress tests with the following setup showed that performance (reads and writes/sec) is halved when ENCRYPT protocol is enabled:
> Infinispan had distributed sync cache with 2 owners on 4 nodes, no transactions. The stress test used 10 threads on each node accessing 1024 byte entries, no conflicts on keys, 20 % writes, 80 % reads.
> It would be great if we could improve the performance of ENCRYPT protocol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-2586) Deal with IPv6 square brackets in AddressValidator
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-2586?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated WFLY-2586:
----------------------------------
Description:
The AddressValidator added in https://issues.jboss.org/browse/WFLY-2535 makes the server boot fail when it's started with -b=[::1] -bmanagement=[::1] -Djboss.bind.address=[::1] -bunsecure=[::1].
"::1" should actually be passed there instead of "[::1]", but the AddressValidator could for sure be more lenient...
This is causing problems in Narayana CI / testsuite.
was:
The AddressValidator added in https://issues.jboss.org/browse/WFLY-2535 makes the server boot fail when it's started with -b=[::1] -bmanagement=[::1] -Djboss.bind.address=[::1] -bunsecure=[::1].
"::1" should actually be passed there instead of "[::1]", but the AddressValidator could for sure be more lenient...
> Deal with IPv6 square brackets in AddressValidator
> --------------------------------------------------
>
> Key: WFLY-2586
> URL: https://issues.jboss.org/browse/WFLY-2586
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Web Services
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 8.0.0.CR1
>
>
> The AddressValidator added in https://issues.jboss.org/browse/WFLY-2535 makes the server boot fail when it's started with -b=[::1] -bmanagement=[::1] -Djboss.bind.address=[::1] -bunsecure=[::1].
> "::1" should actually be passed there instead of "[::1]", but the AddressValidator could for sure be more lenient...
> This is causing problems in Narayana CI / testsuite.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-2586) Deal with IPv6 square brackets in AddressValidator
by Alessio Soldano (JIRA)
Alessio Soldano created WFLY-2586:
-------------------------------------
Summary: Deal with IPv6 square brackets in AddressValidator
Key: WFLY-2586
URL: https://issues.jboss.org/browse/WFLY-2586
Project: WildFly
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Web Services
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: 8.0.0.CR1
The AddressValidator added in https://issues.jboss.org/browse/WFLY-2535 makes the server boot fail when it's started with -b=[::1] -bmanagement=[::1] -Djboss.bind.address=[::1] -bunsecure=[::1].
"::1" should actually be passed there instead of "[::1]", but the AddressValidator could for sure be more lenient...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-2318) Access control exceptions missing for scoped roles
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2318?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-2318:
----------------------------------------
I believe the console is using POST for everything and not GET with the "operation-header-roles" query parameter. If that is the case, I suspect the console may not be creating the "roles" operation header correctly.
Do this:
ModelNode roles = new ModelNode();
roles.add("main-servers");
roles.add("other-servers");
Don't do this:
ModelNode roles = new ModelNode("main-servers,other-servers");
With the WFLY-2583 fix, the latter should work anyway, but if the console is posting a proper ModelNode anyway it's better to use the correct structure.
With a GET you'd do the same and when building the "operation-header-roles" query parameter you'd call asString() on 'roles' (and then URL encode the string to escape quotes etc).
> Access control exceptions missing for scoped roles
> --------------------------------------------------
>
> Key: WFLY-2318
> URL: https://issues.jboss.org/browse/WFLY-2318
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
>
> The following setup: user with two scoped roles assigned. maintainer for "main-servers", monitor for "other-servers". Requesting the access control meta data for the server group wildcard ]does not include "exceptions".
> Expected result: the access control meta data response contains an "exception" for each server group (main-server-group & other-server-group)
> {code}
> [domain@localhost:9999 /] ./server-group=*:read-resource-description(access-control=trim-descriptions, operations=true){roles=main-servers, other-servers}
> {
> "outcome" => "success",
> "result" => [{
> "address" => [("server-group" => "*")],
> "outcome" => "success",
> "result" => {
> "description" => undefined,
> "attributes" => undefined,
> "operations" => undefined,
> "children" => {
> "deployment" => {"model-description" => undefined},
> "system-property" => {"model-description" => undefined},
> "jvm" => {"model-description" => undefined},
> "deployment-overlay" => {"model-description" => undefined}
> },
> "access-control" => {
> "default" => {
> "read" => true,
> "write" => true,
> "attributes" => {
> "socket-binding-port-offset" => {
> "read" => true,
> "write" => true
> },
> "management-subsystem-endpoint" => {
> "read" => true,
> "write" => false
> },
> "socket-binding-group" => {
> "read" => true,
> "write" => true
> },
> "profile" => {
> "read" => true,
> "write" => true
> }
> },
> "operations" => {
> "read-children-names" => {"execute" => true},
> "read-operation-description" => {"execute" => true},
> "remove" => {"execute" => true},
> "read-resource-description" => {"execute" => true},
> "stop-servers" => {"execute" => true},
> "read-resource" => {"execute" => true},
> "add" => {"execute" => true},
> "read-attribute" => {"execute" => true},
> "whoami" => {"execute" => true},
> "read-children-types" => {"execute" => true},
> "read-operation-names" => {"execute" => true},
> "undefine-attribute" => {"execute" => true},
> "start-servers" => {"execute" => true},
> "read-children-resources" => {"execute" => true},
> "restart-servers" => {"execute" => true},
> "replace-deployment" => {"execute" => true},
> "write-attribute" => {"execute" => true}
> }
> },
> "exceptions" => {}
> }
> }
> }]
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-2583) Support multiple run-as roles from CLI and HTTP clients
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2583?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-2583:
-----------------------------------
Workflow: GIT Pull Request workflow (was: classic default workflow)
Parent: (was: WFLY-490)
Issue Type: Bug (was: Technical task)
Git Pull Request: https://github.com/wildfly/wildfly/pull/5539
> Support multiple run-as roles from CLI and HTTP clients
> -------------------------------------------------------
>
> Key: WFLY-2583
> URL: https://issues.jboss.org/browse/WFLY-2583
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.CR1
>
>
> The "run-as" roles feature with RBAC will only allow multiple role declarations if the caller provides a ModelNode of type LIST. The CLI doesn't do that and clients using the HTTP interface (e.g. web console) cannot do that. This makes doing this largely unsupported except for things like unit tests that create custom clients.
> Fix is to do some more sophisticated parsing in RunAsRolesMapper.getOperationHeaderRoles(...).
> 1) If the trimmed role-list string starts with [ and ends with ] try to use ModelNode.fromString to parse. Return result if no error.
> 2) If not, or there is a parse error in 1), check for "," and use String.split(",")
> 3) Just return the trimmed string in a ModelNode.
> Step 2 makes "," a kind of privileged char in role names. However, in the extremely remote chance users want to include "," in role names and still use this feature, the solution is to use proper DMR syntax for the roles header value, e.g.
> ["yuck,commas","Maintainer"]
> So, in the CLI:
> $ :read-resource{roles=["yuck,commas","Maintainer"]}
> An HTTP client like the console should use proper DMR syntax for the value of the operation-header-roles query parameter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (WFLY-2583) Support multiple run-as roles from CLI and HTTP clients
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2583?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-2583:
-----------------------------------
Issue Type: Technical task (was: Requirement )
> Support multiple run-as roles from CLI and HTTP clients
> -------------------------------------------------------
>
> Key: WFLY-2583
> URL: https://issues.jboss.org/browse/WFLY-2583
> Project: WildFly
> Issue Type: Technical task
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.CR1
>
>
> The "run-as" roles feature with RBAC will only allow multiple role declarations if the caller provides a ModelNode of type LIST. The CLI doesn't do that and clients using the HTTP interface (e.g. web console) cannot do that. This makes doing this largely unsupported except for things like unit tests that create custom clients.
> Fix is to do some more sophisticated parsing in RunAsRolesMapper.getOperationHeaderRoles(...).
> 1) If the trimmed role-list string starts with [ and ends with ] try to use ModelNode.fromString to parse. Return result if no error.
> 2) If not, or there is a parse error in 1), check for "," and use String.split(",")
> 3) Just return the trimmed string in a ModelNode.
> Step 2 makes "," a kind of privileged char in role names. However, in the extremely remote chance users want to include "," in role names and still use this feature, the solution is to use proper DMR syntax for the roles header value, e.g.
> ["yuck,commas","Maintainer"]
> So, in the CLI:
> $ :read-resource{roles=["yuck,commas","Maintainer"]}
> An HTTP client like the console should use proper DMR syntax for the value of the operation-header-roles query parameter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months