February 2007 - jboss-jira - Jboss List Archives

[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-367) Add JBoss EULA to aop 2.0 distribution

by Kabir Khan (JIRA)

Add JBoss EULA to aop 2.0 distribution -------------------------------------- Key: JBAOP-367 URL: http://jira.jboss.com/jira/browse/JBAOP-367 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 -- 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
3
0 / 0

[JBoss JIRA] Created: (JBAOP-312) Package retroed deployer for JBoss 4 on jdk1.4

by Kabir Khan (JIRA)

Package retroed deployer for JBoss 4 on jdk1.4 ---------------------------------------------- Key: JBAOP-312 URL: http://jira.jboss.com/jira/browse/JBAOP-312 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan -- 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: (JBRULES-685) Fine grained ACL based security

by Michael Neale (JIRA)

Fine grained ACL based security ------------------------------- Key: JBRULES-685 URL: http://jira.jboss.com/jira/browse/JBRULES-685 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
1
0 / 0

[JBoss JIRA] Created: (JBRULES-399) add support for authentication / permissions / ownership

by Michael Neale (JIRA)

add support for authentication / permissions / ownership --------------------------------------------------------- Key: JBRULES-399 URL: http://jira.jboss.com/jira/browse/JBRULES-399 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben. This authentication/permissions should be tied to the user context that JAAS established. The only things that need to be programmatic are ideally ACLs on a resource. We may need however to show/hide functionality based on the users roles. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBRULES-705) Editor widgets to honour "read only" flag

by Michael Neale (JIRA)

Editor widgets to honour "read only" flag ----------------------------------------- Key: JBRULES-705 URL: http://jira.jboss.com/jira/browse/JBRULES-705 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

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-856) Rationalize the top-level mbean classes

by Brian Stansberry (JIRA)

Rationalize the top-level mbean classes --------------------------------------- Key: JBCACHE-856 URL: http://jira.jboss.com/jira/browse/JBCACHE-856 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA For the AS 5 beta I've added CacheJmxWrapper and PojoCacheJmxWrapper to meet the needs of the AS. There were existing classes in the jmx packages as well. Need to rationalize this; probably get rid of the old existing classes after any tests that use them are switched to the new ones. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBTM-144) Restructure repository

by Mark Little (JIRA)

Restructure repository ---------------------- Key: JBTM-144 URL: http://jira.jboss.com/jira/browse/JBTM-144 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Release Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little We need to commit the QA tests into the repository, but do it in such a way that they can be checked out independently of the rest of the distribution. -- 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
5
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 February 2007