[JBoss JIRA] Updated: (JBAS-3143) JACC isUserInRole and isCallerInRole Testcase retrofit
by Anil Saldhana (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3143?page=all ]
Anil Saldhana updated JBAS-3143:
--------------------------------
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.CR1)
> JACC isUserInRole and isCallerInRole Testcase retrofit
> ------------------------------------------------------
>
> Key: JBAS-3143
> URL: http://jira.jboss.com/jira/browse/JBAS-3143
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-4.0.4.CR2
> Reporter: Anil Saldhana
> Assigned To: Anil Saldhana
> Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.6.CR1
>
>
> As described in the forum thread, when jacc is enabled, the behavior that is seen for programmatic security checks made for the Web and the EJB layer is dependent on whether the DD (web.xml and ejb-jar.xml) define the roles (as part of security-role and/or security-role-ref elements) completely or partially.
> The testcases (mainly the UserInRoleUnitTestCase and the CallerInRoleUnitTestCase) should be retrofitted to handle both the cases - one when the DD is partially descibed and the other when it is fully described.
--
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
19 years, 10 months
[JBoss JIRA] Commented: (JBSEAM-216) Add simple URLs to s:link tag
by Dig (JIRA)
[ http://jira.jboss.com/jira/browse/JBSEAM-216?page=comments#action_12340109 ]
Dig commented on JBSEAM-216:
----------------------------
Hi. Have any Seam developers looked at this issue yet? I've very keen to see this feature included in Seam s:link. Feel free to ask any questions if you're not sure what I'm talking about.
Thanks again, Dig.
> Add simple URLs to s:link tag
> -----------------------------
>
> Key: JBSEAM-216
> URL: http://jira.jboss.com/jira/browse/JBSEAM-216
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: JSF
> Reporter: Dig
> Attachments: faces-config.xml, HtmlLink.java
>
>
> The s:link tag does not currently support custom html links but linking to actions and to JSF views is supported. By extending the current s:link implementation Seam can support URL rewriting techniques. This will enable users to hide JSF and Seam URLs behind custom URLs.
> For further background please refer to the forum post linked from this entry.
> I propose to add a new attribute to the s:link tag (named 'link', 'href' or similar). This attribute would contain the desired URL to link to. The s:link tag would process this URL as for other URLs by adding the conversation ID, etc. Here is an example:
> <s:link value="view" link="#{mycomponent.niceUrl}"/>
> The users application would be responsible for creating the URL and for ensuring that a request to that URL can be processed (url rewriting).
> As a proof of concept I have already implemented this feature. Some details of my changes are in the forum post. The modified files are HtmlLink.java and faces-config.xml. I will attempt to attach these files to this entry.
> It would be great if this feature could be added to release 1.0 of Seam as I'm currently using this functionality now! Many thanks in advance.
--
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
19 years, 10 months
[JBoss JIRA] Commented: (JBAS-3183) Integration with WebSphere MQ 5.x
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3183?page=comments#action_12340105 ]
Dimitris Andreadis commented on JBAS-3183:
------------------------------------------
>From Adrian:
This has two parts:
1) Testing and backporting the server session pool changes from head
2) Finding a workaround for the TM_JOIN hang bug within WSMQ.
The problem is exhibited by the following pseudo code:
Transaction tx = transactionManager.begin();
Connection c1 = wsmqConnectionFactory.createXAConnection();
XAResource xar1 = getXAResource(c1); tx.start(xar1, TM_NOFLAGS);
Connection c2 = wsmqConnectionFactory.createXAConnection();
XAResource xar2 = getXAResource(c2); tx.start(xar2, TM_JOIN); // IT
HANGS HERE IN WSMQ CODE!!!!
So the problem is in WSMQ. Any "fix" would be a workaround to an IBM bug.
> Integration with WebSphere MQ 5.x
> ---------------------------------
>
> Key: JBAS-3183
> URL: http://jira.jboss.com/jira/browse/JBAS-3183
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMS service
> Environment: WebSphereMQ 5.3 with Extended TX client
> Reporter: Luc Texier
> Assigned To: Adrian Brock
> Priority: Critical
> Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.1.CR1
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA...
> we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling
--
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
19 years, 10 months
[JBoss JIRA] Created: (JBAS-3418) org.jboss.test.jmx.test.JMXConnectorUnitTestCase ends with errors
by Jaroslaw Kijanowski (JIRA)
org.jboss.test.jmx.test.JMXConnectorUnitTestCase ends with errors
-----------------------------------------------------------------
Key: JBAS-3418
URL: http://jira.jboss.com/jira/browse/JBAS-3418
Project: JBoss Application Server
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.0.0.Beta
Environment: win xp
Reporter: Jaroslaw Kijanowski
org.jboss.test.jmx.test.JMXConnectorUnitTestCase ends with 9 errors, because of an unavailable service. It tries to connect with:
JMXServiceURL url = new JMXServiceURL("service:jmx:rmi://localhost/jndi/rmi://localhost:1090/jmxconnector");
This service is unavailable, because the "all" instance doesn't deploy jmx-remoting.sar (the "default" instance does).
To fix this, i changed the line 134 in build/build-distr.xml:
dest="${install.default}/deploy/jmx-remoting.sar"/>
to:
dest="${install.all}/deploy/jmx-remoting.sar"/>
--
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
19 years, 10 months
[JBoss JIRA] Created: (JBJMX-97) ArrayIndexOutOfBounds exception in getMBeanInfo with a secured jmx-console
by kgilpin (JIRA)
ArrayIndexOutOfBounds exception in getMBeanInfo with a secured jmx-console
--------------------------------------------------------------------------
Key: JBJMX-97
URL: http://jira.jboss.com/jira/browse/JBJMX-97
Project: JBoss JMX
Issue Type: Bug
Environment: JBoss 4.0.4 GA
Reporter: kgilpin
I have secured the jmx-console using JAAS and the standard UsersRolesLoginModule. I am able to authenticat (basic authentication) through the web UI and manage the console.
I am getting a remote connection to the JMX server from an InitialContext that is populated with the user name and password:
env.put(Context.SECURITY_PRINCIPAL, userName);
env.put(Context.SECURITY_CREDENTIALS, password);
Then I look up the MBeanServerConnection and try to get the MBeanInfo
MBeanServerConnection server = lookup("jmx/invoker/RMIAdaptor", MBeanServerConnection.class);
ObjectName name = new ObjectName(theName);
MBeanInfo info = server.getMBeanInfo(name);
At this point the server throws an ArrayIndexOutOfBoundsException from org.jboss.jmx.connector.invoker.AuthorizationInterceptor line 107.
If I try and set an attribute:
server.setAttribute(name, new Attribute("searchText", searchText));
I get instead at the same line:
java.lang.ClassCastException: javax.management.Attribute
at org.jboss.jmx.connector.invoker.AuthorizationInterceptor.invoke(AuthorizationInterceptor.java:107)
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
--
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
19 years, 10 months