July 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3019) Add support for CRL validation to the certificate based login modules

by Anil Saldhana (JIRA)

[ https://jira.jboss.org/browse/JBAS-3019?page=com.atlassian.jira.plugin.sy... ] Anil Saldhana updated JBAS-3019: -------------------------------- Fix Version/s: 6.0.0.M4 > Add support for CRL validation to the certificate based login modules > --------------------------------------------------------------------- > > Key: JBAS-3019 > URL: https://jira.jboss.org/browse/JBAS-3019 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Reporter: Scott M Stark > Assignee: Marcus Moyses > Fix For: 6.0.0.M4 > > > We need to add support for validating certificates against certificate revocation lists (CRLs). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8126) CNFE Exceptions due to the wrong classloader being used

by Stelios Koussouris (JIRA)

CNFE Exceptions due to the wrong classloader being used ------------------------------------------------------- Key: JBAS-8126 URL: https://jira.jboss.org/browse/JBAS-8126 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.1.0.GA Reporter: Stelios Koussouris Assignee: Alexey Loubyansky The unified classloader is used loading an interface from another jar archive in the /deploy when that interface is called from within a scoped EAR rather than the interface included in the EAR itself. Our tests show when an interface is in a jar in the deploy directory and also in the scoped my.ear Once passivate gets called from a class within the EAR, that calls that interface, then it throws a ClassCastException on ClassLocal myEJB = ClassLocal.class.cast(obj); However it is actually a ClassNotFound, looking in the debugger. We see that instead of using the context of the ejb which would be the EAR classloader, the unified classloader is used instead and hence the resulting exception -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2479) Character encoding incorrect with CASAuthenticationValve enabled

by Martin Putz (JIRA)

Character encoding incorrect with CASAuthenticationValve enabled ---------------------------------------------------------------- Key: JBPORTAL-2479 URL: https://jira.jboss.org/browse/JBPORTAL-2479 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.7.2 Final, Identity-1.1 Reporter: Martin Putz With CASAuthenticationValve enabled, data inserted is returned garbled. In the invoke() method, the parameters are retrieved from the request object. This parses the parameters before any character encoding has been set, but it sets the parameters parsed flag to true. Therefore the encoding will never get set. To get around this, request.setCharacterEncoding(..) needs to be called before any request parameters are retrieved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2565) Support for process node metadata

by Kris Verlaenen (JIRA)

Support for process node metadata --------------------------------- Key: JBRULES-2565 URL: https://jira.jboss.org/browse/JBRULES-2565 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.1.0.CR1 While meta-data is supported at the model level, it also needs to be supported - at the XML level, so the meta-data is stored as part of the process XML definition - at the editor level, so people can add their own meta-data -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8129) Consolidate Security Service Configuration

by Anil Saldhana (JIRA)

Consolidate Security Service Configuration ------------------------------------------ Key: JBAS-8129 URL: https://jira.jboss.org/browse/JBAS-8129 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: 6.0.0.M3 Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 6.0.0.M4 We need a security.xml in the bootstrap folder of JBAS to basically define the beans that the JaasSecurityManagerService and other POJO security configuration beans can rely on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8147) Upgrade to jboss-metadata-ejb 2.0.0-alpha-17

by Carlo de Wolf (JIRA)

Upgrade to jboss-metadata-ejb 2.0.0-alpha-17 -------------------------------------------- Key: JBAS-8147 URL: https://jira.jboss.org/browse/JBAS-8147 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-52) Release jboss-ejb-api_3.1_spec 1.0.0.CR1

by Shelly McGowan (JIRA)

Release jboss-ejb-api_3.1_spec 1.0.0.CR1 ---------------------------------------- Key: JBEE-52 URL: https://jira.jboss.org/browse/JBEE-52 Project: JBoss JavaEE APIs Issue Type: Release Components: EJB API Reporter: Shelly McGowan Assignee: Shelly McGowan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBEE-50) ScheduleExpression.getTimezone() should return null for default @Schedule

by jaikiran pai (JIRA)

ScheduleExpression.getTimezone() should return null for default @Schedule ------------------------------------------------------------------------- Key: JBEE-50 URL: https://jira.jboss.org/browse/JBEE-50 Project: JBoss JavaEE APIs Issue Type: Bug Components: EJB API Affects Versions: 1.0.0.Beta2-ejb-3.1-api Reporter: jaikiran pai Assignee: jaikiran pai For a default @Schedule when timezone is *not* explicitly specified, the EJB3.1 spec says: [97] Note that annotation java.lang.String attributes use the empty string "" as a default, so the expression @Schedule(timezone="", ...) will result in a null value from the corresponding ScheduleExpression.getTimezone() method. Right now, ScheduleExpression.getTimezone() returns an empty string for a default @Schedule -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBJCA-371) Tattletale 1.1.0

by Jesper Pedersen (JIRA)

Tattletale 1.1.0 ---------------- Key: JBJCA-371 URL: https://jira.jboss.org/browse/JBJCA-371 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha14 Latest Tattletale release to the QA environment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6991) Still issue in 5.1.0.GA <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered

by Jeff Wexler (JIRA)

Still issue in 5.1.0.GA <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered -------------------------------------------------------------------------------------------------------------- Key: JBAS-6991 URL: https://jira.jboss.org/jira/browse/JBAS-6991 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (JBoss Messaging) Affects Versions: JBossAS-5.0.0.GA Reporter: Jeff Wexler Assignee: Howard Gao Priority: Minor Fix For: JBossAS-5.1.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2010