[JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3801:
-----------------------------------------------
Fedor Gavrilov <fgavrilo(a)redhat.com> changed the Status of [bug 1136054|https://bugzilla.redhat.com/show_bug.cgi?id=1136054] from POST to MODIFIED
> Wrong Transaction behaviour for EJBs if JTS is enabled
> ------------------------------------------------------
>
> Key: WFLY-3801
> URL: https://issues.jboss.org/browse/WFLY-3801
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Environment: standalone-full profile with JTS enabled
> Reporter: Wolf-Dieter Fink
> Assignee: David Lloyd
> Attachments: 456a624-withDestroy.log, 8d49872-error.log, enableJTS.cli, reproducer.zip, server.log
>
>
> If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation:
> WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
> This is only the case if other resources are involved, i.e. a DB via JPA.
> If a simple bean is used (like ejb-remote quickstart) this warning is not shown.
> It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-3062) Access constraints are not displayed for value types contained in ObjectTypeAttributeDefinition
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3062?page=com.atlassian.jira.plugi... ]
Stefan Guilhen updated WFCORE-3062:
-----------------------------------
Description:
When reading the description of attributes of type OBJECT, the access constraints of the value types contained in the object attribute are not displayed.
Example: In BaseHttpInterfaceResourceDefinition we have an http-upgrade attribute of type OBJECT that contains the sasl-authentication-factory attribute, which is a simple attribute with an access constraint.
When running /core-service=management/management-interface=http-interface:read-resource-description(recursive=true) in the CLI the constraint is not displayed for the attribute:
{noformat}
"http-upgrade" => {
"type" => OBJECT,
"description" => "HTTP Upgrade specific configuration",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"value-type" => {
"enabled" => {
"type" => BOOLEAN,
"description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
},
"sasl-authentication-factory" => {
"type" => STRING,
"description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"capability-reference" => "org.wildfly.security.sasl-authentication-factory",
"min-length" => 1L,
"max-length" => 2147483647L,
}
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
}
{noformat}
was:
When reading the description of attributes of type OBJECT, the access constraints of the value types contained in the object attribute are not displayed.
Example: In BaseHttpInterfaceResourceDefinition we have an http-upgrade attribute of type OBJECT that contains the sasl-authentication-factory attribute, which is a simple attribute with an access constraint.
When running /core-service=management/management-interface=http-interface:read-resource-description(recursive=true) in the CLI the constraint is not displayed for the attribute:
"http-upgrade" => {
"type" => OBJECT,
"description" => "HTTP Upgrade specific configuration",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"value-type" => {
"enabled" => {
"type" => BOOLEAN,
"description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
},
"sasl-authentication-factory" => {
"type" => STRING,
"description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"capability-reference" => "org.wildfly.security.sasl-authentication-factory",
"min-length" => 1L,
"max-length" => 2147483647L,
}
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
}
> Access constraints are not displayed for value types contained in ObjectTypeAttributeDefinition
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-3062
> URL: https://issues.jboss.org/browse/WFCORE-3062
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta28
> Reporter: Stefan Guilhen
>
> When reading the description of attributes of type OBJECT, the access constraints of the value types contained in the object attribute are not displayed.
> Example: In BaseHttpInterfaceResourceDefinition we have an http-upgrade attribute of type OBJECT that contains the sasl-authentication-factory attribute, which is a simple attribute with an access constraint.
> When running /core-service=management/management-interface=http-interface:read-resource-description(recursive=true) in the CLI the constraint is not displayed for the attribute:
> {noformat}
> "http-upgrade" => {
> "type" => OBJECT,
> "description" => "HTTP Upgrade specific configuration",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "value-type" => {
> "enabled" => {
> "type" => BOOLEAN,
> "description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "default" => false
> },
> "sasl-authentication-factory" => {
> "type" => STRING,
> "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "capability-reference" => "org.wildfly.security.sasl-authentication-factory",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> }
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-3062) Access constraints are not displayed for value types contained in ObjectTypeAttributeDefinition
by Stefan Guilhen (JIRA)
Stefan Guilhen created WFCORE-3062:
--------------------------------------
Summary: Access constraints are not displayed for value types contained in ObjectTypeAttributeDefinition
Key: WFCORE-3062
URL: https://issues.jboss.org/browse/WFCORE-3062
Project: WildFly Core
Issue Type: Bug
Affects Versions: 3.0.0.Beta28
Reporter: Stefan Guilhen
When reading the description of attributes of type OBJECT, the access constraints of the value types contained in the object attribute are not displayed.
Example: In BaseHttpInterfaceResourceDefinition we have an http-upgrade attribute of type OBJECT that contains the sasl-authentication-factory attribute, which is a simple attribute with an access constraint.
When running /core-service=management/management-interface=http-interface:read-resource-description(recursive=true) in the CLI the constraint is not displayed for the attribute:
{quote}
"http-upgrade" => {
"type" => OBJECT,
"description" => "HTTP Upgrade specific configuration",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"value-type" => {
"enabled" => {
"type" => BOOLEAN,
"description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
},
"sasl-authentication-factory" => {
"type" => STRING,
"description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"capability-reference" => "org.wildfly.security.sasl-authentication-factory",
"min-length" => 1L,
"max-length" => 2147483647L,
}
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-3062) Access constraints are not displayed for value types contained in ObjectTypeAttributeDefinition
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3062?page=com.atlassian.jira.plugi... ]
Stefan Guilhen updated WFCORE-3062:
-----------------------------------
Description:
When reading the description of attributes of type OBJECT, the access constraints of the value types contained in the object attribute are not displayed.
Example: In BaseHttpInterfaceResourceDefinition we have an http-upgrade attribute of type OBJECT that contains the sasl-authentication-factory attribute, which is a simple attribute with an access constraint.
When running /core-service=management/management-interface=http-interface:read-resource-description(recursive=true) in the CLI the constraint is not displayed for the attribute:
"http-upgrade" => {
"type" => OBJECT,
"description" => "HTTP Upgrade specific configuration",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"value-type" => {
"enabled" => {
"type" => BOOLEAN,
"description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
},
"sasl-authentication-factory" => {
"type" => STRING,
"description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"capability-reference" => "org.wildfly.security.sasl-authentication-factory",
"min-length" => 1L,
"max-length" => 2147483647L,
}
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
}
was:
When reading the description of attributes of type OBJECT, the access constraints of the value types contained in the object attribute are not displayed.
Example: In BaseHttpInterfaceResourceDefinition we have an http-upgrade attribute of type OBJECT that contains the sasl-authentication-factory attribute, which is a simple attribute with an access constraint.
When running /core-service=management/management-interface=http-interface:read-resource-description(recursive=true) in the CLI the constraint is not displayed for the attribute:
{quote}
"http-upgrade" => {
"type" => OBJECT,
"description" => "HTTP Upgrade specific configuration",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"value-type" => {
"enabled" => {
"type" => BOOLEAN,
"description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
},
"sasl-authentication-factory" => {
"type" => STRING,
"description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"capability-reference" => "org.wildfly.security.sasl-authentication-factory",
"min-length" => 1L,
"max-length" => 2147483647L,
}
},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
{quote}
> Access constraints are not displayed for value types contained in ObjectTypeAttributeDefinition
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-3062
> URL: https://issues.jboss.org/browse/WFCORE-3062
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta28
> Reporter: Stefan Guilhen
>
> When reading the description of attributes of type OBJECT, the access constraints of the value types contained in the object attribute are not displayed.
> Example: In BaseHttpInterfaceResourceDefinition we have an http-upgrade attribute of type OBJECT that contains the sasl-authentication-factory attribute, which is a simple attribute with an access constraint.
> When running /core-service=management/management-interface=http-interface:read-resource-description(recursive=true) in the CLI the constraint is not displayed for the attribute:
> "http-upgrade" => {
> "type" => OBJECT,
> "description" => "HTTP Upgrade specific configuration",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "value-type" => {
> "enabled" => {
> "type" => BOOLEAN,
> "description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "default" => false
> },
> "sasl-authentication-factory" => {
> "type" => STRING,
> "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "capability-reference" => "org.wildfly.security.sasl-authentication-factory",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> }
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1281) SecurityDomain.authenticate() propagates credentials inappropriately
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-1281?page=com.atlassian.jira.plugin.s... ]
Pedro Igor reassigned ELY-1281:
-------------------------------
Assignee: Pedro Igor
> SecurityDomain.authenticate() propagates credentials inappropriately
> --------------------------------------------------------------------
>
> Key: ELY-1281
> URL: https://issues.jboss.org/browse/ELY-1281
> Project: WildFly Elytron
> Issue Type: Bug
> Components: API / SPI, Authentication Server
> Reporter: David Lloyd
> Assignee: Pedro Igor
> Priority: Blocker
>
> The SecurityDomain.authenticate() method creates a SecurityIdentity that inherits its credentials from the calling identity.
> The usage of ServerAuthenticationContext is correct (it inherits the current identity as the captured identity). Capturing the identity is necessary to perform run-as authorizations without an authentication step. However the credentials should probably not be propagated from the captured identity in any case.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the testsuite
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-7309:
-----------------------------------------------
Fedor Gavrilov <fgavrilo(a)redhat.com> changed the Status of [bug 1384542|https://bugzilla.redhat.com/show_bug.cgi?id=1384542] from POST to MODIFIED
> Make the authentication configurable in the testsuite
> ------------------------------------------------------
>
> Key: WFLY-7309
> URL: https://issues.jboss.org/browse/WFLY-7309
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.1.0.Final
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
> Fix For: 11.0.0.Alpha1
>
>
> Actually some tests cases fails when running against a remote eap instance.
> In this specific case instances running on Openshift v3.
> In order to get those tests working we have to modify some classes to configure the authentication.
> Example:
> org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
> return connector.getMBeanServerConnection();
> }
> {code}
> To:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
> String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
> propEnv.put(JMXConnector.CREDENTIALS, credentials);
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
> return connector.getMBeanServerConnection();
> }
> {code}
> Could these kind of authentication being configurable?
> It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9079) maven-checkstyle-plugin should not run on generated sources
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9079?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9079:
--------------------------------------
For reference the problem is that the default value for the directories that checkstyle runs on..
https://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo....
> maven-checkstyle-plugin should not run on generated sources
> -----------------------------------------------------------
>
> Key: WFLY-9079
> URL: https://issues.jboss.org/browse/WFLY-9079
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Quickstarts
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Blocker
> Fix For: 11.0.0.Beta1
>
>
> {noformat}
> [INFO] --- maven-checkstyle-plugin:2.17:checkstyle (check-style) @ batch-processing ---
> [INFO] Starting audit...
> [ERROR] /Users/rhusar/git/wildfly-quickstarts/batch-processing/target/generated-sources/annotations/org/jboss/as/quickstarts/batch/model/Contact_.java:11:1: Line contains a tab character. [FileTabCharacter]
> [ERROR] /Users/rhusar/git/wildfly-quickstarts/batch-processing/target/generated-sources/annotations/org/jboss/as/quickstarts/batch/model/Contact_.java:12:1: Line contains a tab character. [FileTabCharacter]
> [ERROR] /Users/rhusar/git/wildfly-quickstarts/batch-processing/target/generated-sources/annotations/org/jboss/as/quickstarts/batch/model/Contact_.java:13:1: Line contains a tab character. [FileTabCharacter]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months