[JBoss JIRA] (WFLY-2150) Rethink OperationContextImpl.getBasicAuthorizationResponse
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2150?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-2150:
-----------------------------------
Fix Version/s: 9.0.0.CR1
(was: 8.0.0.CR1)
> Rethink OperationContextImpl.getBasicAuthorizationResponse
> ----------------------------------------------------------
>
> Key: WFLY-2150
> URL: https://issues.jboss.org/browse/WFLY-2150
> Project: WildFly
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 9.0.0.CR1
>
>
> OperationContextImpl.getBasicAuthorizationResponse is designed around the "pass" case. It tests all action effects but discards data if any fail. This is ok in the normal case where things will pass. But in the read-resource-description and recursive read-resource cases, where things may often fail with the failure being recorded as expected (i.e. non-failure) output, this approach is inefficient, because the caller is forced to re-authorize to get the discarded data.
--
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
11 years, 11 months
[JBoss JIRA] (WFLY-1950) Problems with connector 1.7
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-1950?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-1950:
-------------------------------------
Assignee: Jeff Zhang (was: Jesper Pedersen)
> Problems with connector 1.7
> ---------------------------
>
> Key: WFLY-1950
> URL: https://issues.jboss.org/browse/WFLY-1950
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Beta1
> Reporter: Frank Langelage
> Assignee: Jeff Zhang
> Attachments: filesystem-ra.xml.1.6.1.7, filesystem-ra.xml.1.7, filesystem-ra.xml.before
>
>
> Usually I see this when deploying my RA:
> 21:30:53,599 INFO [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "filesystem.rar" (runtime-name: "filesystem.rar")
> 21:30:53,745 INFO [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/Filesystem
> 21:30:53,750 INFO [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-acf9504f544e0a1d/contents/
> 21:30:53,764 INFO [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/Filesystem]
> 21:30:53,822 INFO [org.jboss.as.server#handleResult] JBAS018559: Deployed "filesystem.rar" (runtime-name : "filesystem.rar")
> Because JCA 1.7 was introduced to head at github I changed header of ra.xml to 1.7 version.
> But then I no longer see the line
> 21:30:53,764 INFO [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/Filesystem]
> I did not specify the <outbound-resourceadapter> in ra.xml.
> Another adapter is working fine after version upgrade.
> So I added the <outbound-resourceadapter> also to the now failing one.
> But this gives this now:
> 21:35:57,797 INFO [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "filesystem.rar" (runtime-name: "filesystem.rar")
> 21:35:57,941 ERROR [org.jboss.msc.service.fail#startFailed] MSC000001: Failed to start service jboss.ra.deployment."filesystem.rar_4": org.jboss.msc.service.StartException in service jboss.ra.deployment."filesystem.rar_4": org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:136)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:120)
> ... 5 more
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-c256d8da3c2df580/contents/
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2564)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:197)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:113)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.jca.common.metadata.ra.common.OutboundResourceAdapterImpl.getReauthenticationSupport(OutboundResourceAdapterImpl.java:182)
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2073)
> ... 7 more
> 21:35:57,962 ERROR [org.jboss.as.controller.management-operation#executeStep] JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "filesystem.rar")]) - failure description: {"JBAS014671: Failed services" => {"jboss.ra.deployment.\"filesystem.rar_4\"" => "org.jboss.msc.service.StartException in service jboss.ra.deployment.\"filesystem.rar_4\": org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-c256d8da3c2df580/contents/
> Caused by: java.lang.NullPointerException"}}
> 21:35:57,982 ERROR [org.jboss.as.server#handleResult] JBAS015870: Deploy of deployment "filesystem.rar" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.ra.deployment.\"filesystem.rar_4\"" => "org.jboss.msc.service.StartException in service jboss.ra.deployment.\"filesystem.rar_4\": org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-c256d8da3c2df580/contents/
> Caused by: java.lang.NullPointerException"}}
> 21:35:58,011 INFO [org.jboss.as.server.deployment#stop] JBAS015877: Stopped deployment filesystem.rar (runtime-name: filesystem.rar) in 24ms
> Adding also <reauthentication-support>false</reauthentication-support> solves this NPE, the RA gets deployed and bound to JNDI again.
--
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
11 years, 11 months
[JBoss JIRA] (WFLY-2398) org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase fails
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-2398?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-2398:
-------------------------------------
Assignee: Jeff Zhang (was: Stefano Maestri)
> org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase fails
> ------------------------------------------------------------------------
>
> Key: WFLY-2398
> URL: https://issues.jboss.org/browse/WFLY-2398
> 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.inflow.InflowTestCase-output.txt, org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase.txt
>
>
> Running a build of current sources with complete testsuite this test is failing with
> testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase): 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
11 years, 11 months
[JBoss JIRA] (WFLY-2400) org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-2400?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-2400:
-------------------------------------
Assignee: Jeff Zhang (was: Stefano Maestri)
> org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails
> ---------------------------------------------------------------------
>
> Key: WFLY-2400
> URL: https://issues.jboss.org/browse/WFLY-2400
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Server, 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.mgmt.servermodule.ValidateModelTestCase-output.txt, org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase.txt
>
>
> Running a build of current sources with complete testsuite this test is failing with
> testValidateModel(org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase): The model failed validation
--
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
11 years, 11 months
[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
11 years, 11 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
11 years, 11 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
11 years, 11 months