May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-806) modify pom.xml to exclude JTA lib

by Michael Neale (JIRA)

modify pom.xml to exclude JTA lib --------------------------------- Key: JBRULES-806 URL: http://jira.jboss.com/jira/browse/JBRULES-806 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-650) Login screen + authentication of the service layer, userId needs to be applied in each action for auditing

by Michael Neale (JIRA)

Login screen + authentication of the service layer, userId needs to be applied in each action for auditing ---------------------------------------------------------------------------------------------------------- Key: JBRULES-650 URL: http://jira.jboss.com/jira/browse/JBRULES-650 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 2 months

3
14
0 / 0

[JBoss JIRA] Created: (JBFORUMS-227) Redesign LnF for Attachments displaying on TopicView

by James Cobb (JIRA)

Redesign LnF for Attachments displaying on TopicView ---------------------------------------------------- Key: JBFORUMS-227 URL: http://jira.jboss.com/jira/browse/JBFORUMS-227 Project: JBoss Forums Issue Type: Task Reporter: James Cobb Assigned To: James Cobb Redesign the page view based on the new forums look and feel. Look for usability wins in the process. Attachments displaying on TopicView : http://forums.proto.jboss.com:8080/portal/auth/portal/default/Forum/Forum... -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Closed: (JBAS-2624) Generic AuthorizationManager service

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2624?page=all ] Anil Saldhana closed JBAS-2624. ------------------------------- Resolution: Done > Generic AuthorizationManager service > ------------------------------------ > > Key: JBAS-2624 > URL: http://jira.jboss.com/jira/browse/JBAS-2624 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Anil Saldhana > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta3 > > > For the first pass, the AuthorizationManager interface is defined as follows: > public interface AuthorizationManager > { > //Permission can be of type WebUserDataPermission, > //WebResourcePermission and WebRoleRefPermission > public boolean hasPermission(Permission perm, Principal principal); > public boolean doesUserHaveRole(String roleName); > } -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3576) Unified Security Context

by Anil Saldhana (JIRA)

Unified Security Context ------------------------ Key: JBAS-3576 URL: http://jira.jboss.com/jira/browse/JBAS-3576 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta Currently the roles are an aspect of the Subject that is populated as part of the Jaas Authentication process (in the derivatives of the AbstractServerLoginModule). There is a need for the establishment of a security context to hold the roles, authoriation info etc. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (SECURITY-11) Principal To Role mapping provider

by Anil Saldhana (JIRA)

Principal To Role mapping provider ---------------------------------- Key: SECURITY-11 URL: http://jira.jboss.com/jira/browse/SECURITY-11 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 We need a mechanism that will allow a user to configure a mapping of principal to roles that need to be added to the security context. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-26) Legacy MBeans move back to JBAS/security project for porting

by Anil Saldhana (JIRA)

Legacy MBeans move back to JBAS/security project for porting ------------------------------------------------------------ Key: SECURITY-26 URL: http://jira.jboss.com/jira/browse/SECURITY-26 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 The legacy mbean services like jaassecuritymanagerservice etc need to be retained in the security module of the jbas build for porting customers. This is according to Scott. === The security mbeans really should be back in the jbossas/security as integration code so that the security project is a mc/pojo based set of security aspects. I'm talking about the legacy mbeans which we should keep for porting. === -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-396) Investigate integration with jboss logging

by Kabir Khan (JIRA)

Investigate integration with jboss logging ------------------------------------------ Key: JBAOP-396 URL: http://jira.jboss.com/jira/browse/JBAOP-396 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha5 -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4421) jmx-console does handle glassbox MBeans correctly.

by Jeremy Norris (JIRA)

jmx-console does handle glassbox MBeans correctly. -------------------------------------------------- Key: JBAS-4421 URL: http://jira.jboss.com/jira/browse/JBAS-4421 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Environment: Glassbox 2.0 Beta Reporter: Jeremy Norris Glassbox 2.0 Beta on JBoss 4.0.5. When the jmx-console main page is loaded, it stack traces when visiting many of the glassbox MBeans. ie: java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - For input string: "'"" at java.net.URLDecoder.decode(URLDecoder.java:173) at java.net.URLDecoder.decode(URLDecoder.java:83) ... Problems occur with MBean names that look like this: resource0="jdbc:mysql://<server>:3306/<schema_name>",resource1="SHOW FULL COLUMNS FROM `table_name` FROM `schema_name` LIKE '%'",topic=stats The problem is the '%' character is not being handled correctly by the jmx console. Even though this is a unusual name for an MBean, I think it's legal (This particular MBean name example is coming from some hibernate DDL generation stuff on initialization that glassbox is instrumenting, but this is not important right now). -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-218) Change PreferencesView

by Ryszard Kozmik (JIRA)

Change PreferencesView ---------------------- Key: JBFORUMS-218 URL: http://jira.jboss.com/jira/browse/JBFORUMS-218 Project: JBoss Forums Issue Type: Sub-task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC PreferencesView has to be rewritten to new design. -- 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, 2 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2007