[JBoss JIRA] Created: (JBPORTAL-1740) cms admin portlet checks for hardcoded role named 'admin'
by Tobias Roth (JIRA)
cms admin portlet checks for hardcoded role named 'admin'
---------------------------------------------------------
Key: JBPORTAL-1740
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1740
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.2 Final
Reporter: Tobias Roth
Assigned To: Sohil Shah
See also http://jira.jboss.com/jira/browse/JBPORTAL-1646
I found another hardcoded use of 'admin'. The effect of having this is that even with the change I described above, permissions of cms nodes cannot be changed by users that are not in role called 'admin'.
Why does the security console need to have separate access rights? Aren't the access rights for the CMS admin console enough?
In core-cms/src/main/org/jboss/portal/core/cms/ui/admin/CMSAdminPortlet.java:
private boolean isSecurityConsoleAccessible(PortletRequest portletRequest)
{
try
{
boolean isAccessible = false;
if (portletRequest.getUserPrincipal() != null)
{
User user = this.userModule.findUserByUserName(portletRequest.getUserPrincipal().getName());
Set roles = this.membershipModule.getRoles(user);
if (roles != null)
{
for (Iterator itr = roles.iterator(); itr.hasNext();)
{
Role role = (Role)itr.next();
if (role.getName().equalsIgnoreCase("admin"))
{
isAccessible = true;
break;
}
}
}
}
return isAccessible;
}
catch (Exception e)
{
return false;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Created: (JBMESSAGING-1124) Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
by Tim Fox (JIRA)
Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
-----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1124
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1124
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Minor
Fix For: EAP 4.3 Integration
Get the following exception in logs when shutting down JBoss 4.2.1.GA server with JBM by pressing CTRL-C
Seems benign but annoying.
13:00:12,932 WARN [ConnectionFactory] Stopping failed jboss.messaging.connectionfactory:service=ConnectionFactory
java.lang.IllegalStateException: Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.unregisterConnectionFactory(ConnectionFactoryJNDIMapper.java:274)
at org.jboss.jms.server.connectionfactory.ConnectionFactory.stopService(ConnectionFactory.java:239)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:206)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
at $Proxy0.stop(Unknown Source)
at org.jboss.system.ServiceController.stop(ServiceController.java:508)
at org.jboss.system.ServiceController.stop(ServiceController.java:499)
at org.jboss.system.ServiceController.stop(ServiceController.java:499)
at org.jboss.system.ServiceController.stop(ServiceController.java:499)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.stop(Unknown Source)
at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:336)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy51.stop(Unknown Source)
at org.jboss.deployment.XSLSubDeployer.stop(XSLSubDeployer.java:202)
at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:516)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:1058)
at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:1033)
at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:996)
13:00:12,968 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@c971d55 undeployed
13:00:13,063 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@7451b0af undeployed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Closed: (JBAS-2889) AppClientUnitTestCase doesn't clean up if it fails
by Ryan Campbell (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2889?page=all ]
Ryan Campbell closed JBAS-2889.
-------------------------------
Fix Version/s: (was: JBossAS-5.0.0.Beta3)
Resolution: Out of Date
Assignee: (was: Ryan Campbell)
I logged this issue over a year ago, so it doesn't surprise me that its no longer reproducible.
Thanks for following up on it.
> AppClientUnitTestCase doesn't clean up if it fails
> --------------------------------------------------
>
> Key: JBAS-2889
> URL: http://jira.jboss.com/jira/browse/JBAS-2889
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Ryan Campbell
>
> The org.jboss.test.client.test.AppClientUnitTestCase deploys a bunch of services but fails to clean them.
> If you run a CMP test before the AppClientUnitTest, it passes, but if you run it immediately after, it fails:
> > ./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> one-test:
> [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 6.04 sec
> > ./build.sh one-test -Dtest=org.jboss.test.client.test.AppClientUnitTestCase
> [junit] Running org.jboss.test.client.test.AppClientUnitTestCase
> [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.149 sec
> [junit] Test org.jboss.test.client.test.AppClientUnitTestCase FAILED
> > ./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Tests run: 19, Failures: 0, Errors: 19, Time elapsed: 1.05 sec
> [junit] Test org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase FAILED
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Updated: (JBAS-2889) AppClientUnitTestCase doesn't clean up if it fails
by Shelly McGowan (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2889?page=all ]
Shelly McGowan updated JBAS-2889:
---------------------------------
Assignee: Ryan Campbell (was: Shelly McGowan)
I am unable to reproduce this issue with https://svn.jboss.org/repos/jbossas/trunk, Revision 67446.
Ryan, is there more info that you can provide other than what is in the description? Otherwise, we may want to remove the tests from
being excluded.
./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
Searching for build.xml ...
Buildfile: /NotBackedUp/trunk/testsuite/build.xml
Overriding previous definition of reference to jboss.test.classpath
one-test:
[junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
[junit] Found log4j.xml: file:/NotBackedUp/trunk/testsuite/output/resources/log4j.xml
[junit] Tests run: 23, Failures: 0, Errors: 0, Time elapsed: 18.055 sec
BUILD SUCCESSFUL
Total time: 23 seconds
./build.sh one-test -Dtest=org.jboss.test.client.test.AppClientUnitTestCase
Searching for build.xml ...
Buildfile: /NotBackedUp/trunk/testsuite/build.xml
one-test:
[junit] Running org.jboss.test.client.test.AppClientUnitTestCase
[junit] Found log4j.xml: file:/NotBackedUp/trunk/testsuite/output/resources/log4j.xml
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.52 sec
BUILD SUCCESSFUL
Total time: 13 seconds
./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
Searching for build.xml ...
Buildfile: /NotBackedUp/trunk/testsuite/build.xml
one-test:
[junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
[junit] Found log4j.xml: file:/NotBackedUp/trunk/testsuite/output/resources/log4j.xml
[junit] Tests run: 23, Failures: 0, Errors: 0, Time elapsed: 2.158 sec
BUILD SUCCESSFUL
Total time: 8 seconds
> AppClientUnitTestCase doesn't clean up if it fails
> --------------------------------------------------
>
> Key: JBAS-2889
> URL: http://jira.jboss.com/jira/browse/JBAS-2889
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Ryan Campbell
> Assigned To: Ryan Campbell
> Fix For: JBossAS-5.0.0.Beta3
>
>
> The org.jboss.test.client.test.AppClientUnitTestCase deploys a bunch of services but fails to clean them.
> If you run a CMP test before the AppClientUnitTest, it passes, but if you run it immediately after, it fails:
> > ./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> one-test:
> [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 6.04 sec
> > ./build.sh one-test -Dtest=org.jboss.test.client.test.AppClientUnitTestCase
> [junit] Running org.jboss.test.client.test.AppClientUnitTestCase
> [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.149 sec
> [junit] Test org.jboss.test.client.test.AppClientUnitTestCase FAILED
> > ./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Tests run: 19, Failures: 0, Errors: 19, Time elapsed: 1.05 sec
> [junit] Test org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase FAILED
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
[JBoss JIRA] Resolved: (JBWEB-29) AJP proxy daemon
by Remy Maucherat (JIRA)
[ http://jira.jboss.com/jira/browse/JBWEB-29?page=all ]
Remy Maucherat resolved JBWEB-29.
---------------------------------
Resolution: Won't Fix
No longer un to date with the current development plans.
> AJP proxy daemon
> ----------------
>
> Key: JBWEB-29
> URL: http://jira.jboss.com/jira/browse/JBWEB-29
> Project: JBoss Web
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Remy Maucherat
> Assigned To: Remy Maucherat
>
> Proxy daemon for the AJP protocol, usable as a small front end independent binary. This will be written using JBoss Web's internal API and connectors, and will also have the following capabilities:
> - load balancing
> - caching
> APR will be mandatory, but efficiency may not be maximal compared to other proxy technologies (OTOH, it should be small, JBoss Web friendly, and reasonably stable since based on mature Tomcat components).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 5 months
