March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2654) The run-as identity does NOT apply to the timeout callback method of an enterprise bean

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-2654?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned WFLY-2654: ------------------------------------ Assignee: Tomasz Adamski (was: Stuart Douglas) > The run-as identity does NOT apply to the timeout callback method of an enterprise bean > --------------------------------------------------------------------------------------- > > Key: WFLY-2654 > URL: https://issues.jboss.org/browse/WFLY-2654 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Matus Abaffy > Assignee: Tomasz Adamski > > EJB 3.2 spec., 12.3.4.1 Run-as: > bq. The run-as identity applies ... to the timeout callback methods of an enterprise bean; > Assume the following classes: > {code} > @Stateless > @RunAs("alarm") > public class Alarm { > @EJB > private Bell bell; > // some more logic > @Timeout > public void ejbTimeout(Timer timer) { > bell.ring(); > } > } > {code} > {code} > @Stateless > @RolesAllowed("alarm") > public class Bell { > public void ring() {} > } > {code} > When the Alarm's timeout callback method is invoked due to timer expiration, bell.ring(); results in > {code}ERROR [org.jboss.as.ejb3.invocation] (EJB default - 1) JBAS014134: EJB Invocation failed on component Bell for method public void org.jboss.as.test.integration.ejb.security.timeout.Bell.ring(): javax.ejb.EJBAccessException: JBAS014502: Invocation on method: public void org.jboss.as.test.integration.ejb.security.timeout.Bell.ring() of bean: Bell is not allowed {code} > Calling bell.ring(); from Alarm's business methods works as expected (no error). > Simple test case available at: https://github.com/bafco/wildfly/tree/timeoutSecurity -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2669) ConcurrentModificationException releasing JSF factories

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-2669?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-2669: ---------------------------------- JAVASERVERFACES-3202 has now been resolved. The fix will be included in the Mojarra 2.2.7 release. > ConcurrentModificationException releasing JSF factories > ------------------------------------------------------- > > Key: WFLY-2669 > URL: https://issues.jboss.org/browse/WFLY-2669 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.Beta1 > Reporter: Jozef Hartinger > Assignee: Farah Juma > > Saw this happen once. Probably a thread-safety problem in JSF API: > {code} > 5:04:37,876 ERROR [io.undertow.servlet.request] (MSC service thread 1-4) UT015005: Error invoking method contextDestroyed on listener class com.sun.faces.config.ConfigureListener: java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926) [rt.jar:1.7.0_45] > at java.util.HashMap$ValueIterator.next(HashMap.java:954) [rt.jar:1.7.0_45] > at javax.faces.FactoryFinder.releaseFactories(FactoryFinder.java:440) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4] > at com.sun.faces.config.ConfigManager.releaseFactories(ConfigManager.java:808) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.config.ConfigManager.destroy(ConfigManager.java:474) [jsf-impl-2.2.4-jbossorg-1.jar:] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:329) [jsf-impl-2.2.4-jbossorg-1.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Beta27.jar:1.0.0.Beta27] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Beta27.jar:1.0.0.Beta27] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:523) [undertow-servlet-1.0.0.Beta27.jar:1.0.0.Beta27] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > {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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2509) Method invocation of a non serializable remote EJB

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-2509?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned WFLY-2509: ------------------------------------ Assignee: Tomasz Adamski (was: David Lloyd) > Method invocation of a non serializable remote EJB > --------------------------------------------------- > > Key: WFLY-2509 > URL: https://issues.jboss.org/browse/WFLY-2509 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: EJB > Reporter: omar al kababji > Assignee: Tomasz Adamski > Priority: Optional > > If you have a remote EJB that is not Serializable (i.e. does not implement the interface Serializable) you can lookup such class from a remote EJB client however when you execute a method you get an error as follows: > java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling > The enhancement is to give an error or warning message when the EJB is deployed notifying the developer that he is deploying a Remote EJB that is not implementing the Serializable interface. > The same thing happens if you deploy an EJB marked with the annotation @Remote but with no @Stateless nor @Statefull annotations. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3053) BootstrapImpl#bootstrap result is inherently racy

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFLY-3053?page=com.atlassian.jira.plugin.... ] Richard Opalka reassigned WFLY-3053: ------------------------------------ Assignee: Richard Opalka (was: Jason Greene) > BootstrapImpl#bootstrap result is inherently racy > ------------------------------------------------- > > Key: WFLY-3053 > URL: https://issues.jboss.org/browse/WFLY-3053 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Reporter: David Lloyd > Assignee: Richard Opalka > Fix For: 8.0.1.Final > > > The boostrap code presently installs a stability monitor and awaits stability before returning. It then probes the state of the root service. There is a window of time in which the root service may be stopped or removed, resulting in big exception traces being logged. To atomically get the result of the operation, the service container must somehow be frozen until the root service is completely read. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-850) @TransactionTimeout ignored if method ist not public

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-850?page=com.atlassian.jira.plugin.s... ] Tomasz Adamski edited comment on WFLY-850 at 3/25/14 10:24 AM: --------------------------------------------------------------- Information about transaction timeout wasn't propagated to @Timeout methods. Public methods got this information accidentally as all public methods are part of no-interface bean view. Added fix and a test. was (Author: tomekadamski): Information about transaction timeout wasn't propagated to @Timeout methods. Added fix and a test. > @TransactionTimeout ignored if method ist not public > ---------------------------------------------------- > > Key: WFLY-850 > URL: https://issues.jboss.org/browse/WFLY-850 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Frank Langelage > Assignee: Tomasz Adamski > Priority: Minor > > The annotation @TransactionTimeout is not honored, when the method has other than public access. > @Timeout methods invoked by the container are allowed to have "public, private, protected, or package level access". > So the annotation should work also if method is not public. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-850) @TransactionTimeout ignored if method ist not public

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-850?page=com.atlassian.jira.plugin.s... ] Tomasz Adamski edited comment on WFLY-850 at 3/25/14 10:23 AM: --------------------------------------------------------------- Information about transaction timeout wasn't propagated to @Timeout methods. Added fix and a test. was (Author: tomekadamski): Information about transaction timeout wasn't propagated to @Timeout methods. Added fix and test. > @TransactionTimeout ignored if method ist not public > ---------------------------------------------------- > > Key: WFLY-850 > URL: https://issues.jboss.org/browse/WFLY-850 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Frank Langelage > Assignee: Tomasz Adamski > Priority: Minor > > The annotation @TransactionTimeout is not honored, when the method has other than public access. > @Timeout methods invoked by the container are allowed to have "public, private, protected, or package level access". > So the annotation should work also if method is not public. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-146) jboss-el-api_2.2_spec 1.0.2.Final cannot access public methods from non-public classes

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/JBEE-146?page=com.atlassian.jira.plugin.s... ] Farah Juma commented on JBEE-146: --------------------------------- Good catch, Tomaz. It looks like the upstream fix was made right around the same time this workaround was added so we weren't aware of it at the time. > jboss-el-api_2.2_spec 1.0.2.Final cannot access public methods from non-public classes > -------------------------------------------------------------------------------------- > > Key: JBEE-146 > URL: https://issues.jboss.org/browse/JBEE-146 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: jboss-el-api_2.2_spec-1.0.3.Final, jboss-el-api_3.0_spec-1.0.0.Final > > > When accessing a public method of a non-public class via EL that implements a public interface or has a public superclass, the following exception occurs: > {code}java.lang.IllegalAccessException: Class javax.el.BeanELResolver can not access a member of class X with modifiers "public" > {code} > See https://bugzilla.redhat.com/show_bug.cgi?id=1029387 for more details. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2610) Add the ability to take an external based password to the Vault tool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2610?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2610: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1080466 > Add the ability to take an external based password to the Vault tool > -------------------------------------------------------------------- > > Key: WFLY-2610 > URL: https://issues.jboss.org/browse/WFLY-2610 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Final > > > At the moment the Vault tool only supports plain text password as a parameter. With SECURITY-770 committed in it is also possible to configure the Vault to take an external password. Thus the Vault tool needs to support it too. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2610) Add the ability to take an external based password to the Vault tool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2610?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2610: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1080466|https://bugzilla.redhat.com/show_bug.cgi?id=1080466] from NEW to ASSIGNED > Add the ability to take an external based password to the Vault tool > -------------------------------------------------------------------- > > Key: WFLY-2610 > URL: https://issues.jboss.org/browse/WFLY-2610 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Final > > > At the moment the Vault tool only supports plain text password as a parameter. With SECURITY-770 committed in it is also possible to configure the Vault to take an external password. Thus the Vault tool needs to support it too. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3069) slaves cannot reconnect to a restarted master if RBAC is enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3069?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3069: ----------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1072949|https://bugzilla.redhat.com/show_bug.cgi?id=1072949] from NEW to POST > slaves cannot reconnect to a restarted master if RBAC is enabled > ---------------------------------------------------------------- > > Key: WFLY-3069 > URL: https://issues.jboss.org/browse/WFLY-3069 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 8.0.1.Final > > > Enable RBAC in an Wilfly domain setup. "reload --host=master" and the slaves will no longer be connected to the master -- 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

10 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014