October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBEE-45) Release JACC 1.1 APIs built with JDK 1.4

by Shelly McGowan (JIRA)

Release JACC 1.1 APIs built with JDK 1.4 ---------------------------------------- Key: JBEE-45 URL: https://jira.jboss.org/jira/browse/JBEE-45 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.0.CR1 To replace this: http://repository.jboss.org/maven2/org/jboss/javaee/jboss-jacc-api_JDK4/1... which contains a servlet snapshot Needed by Hibernate -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBEE-76) Create JavaEE API aggregate for use with JBoss AS 7

by Shelly McGowan (JIRA)

Create JavaEE API aggregate for use with JBoss AS 7 --------------------------------------------------- Key: JBEE-76 URL: https://issues.jboss.org/browse/JBEE-76 Project: JBoss JavaEE APIs Issue Type: Feature Request Components: javaee6_specs_bom, javaee_6.0_spec Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 2.0.0-Beta1-javaee_6.0, 2.0.0-Beta1-javaee6-specs-bom Started Version 2.0.x series for use with JBoss AS 7. These APIs are compatible but the versions in the specs bom and aggregate align with the versions in the AS 7 distribution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] (AS7-2422) Failed to disable datasource

by Heiko Braun (Created) (JIRA)

Failed to disable datasource ---------------------------- Key: AS7-2422 URL: https://issues.jboss.org/browse/AS7-2422 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.Beta1 We've got regression on the datasource management. The datasource is enabled, but disabling fails: {noformat} [standalone@localhost:9999 /] /profile=default/subsystem=datasources/data-source=java\:jboss\/datasources\/ExampleDS:disable { "outcome" => "failed", "result" => {"server-groups" => [("main-server-group" => {"master" => { "host" => "master", "response" => { "outcome" => "failed", "failure-description" => "Data-source service [java:jboss/datasources/ExampleDS] is not enabled", "rolled-back" => true } }})]}, "failure-description" => "Operation failed or was rolled back on all servers.", "rolled-back" => true } {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1358) UserTransaction not available to non-EE threads

by Chris Lowe (JIRA)

UserTransaction not available to non-EE threads ----------------------------------------------- Key: AS7-1358 URL: https://issues.jboss.org/browse/AS7-1358 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Affects Versions: 7.0.0.Final Reporter: Chris Lowe Assignee: Jonathan Halliday JBoss Seam offers Asynchronous behaviour for non-EJB environments using a Quartz dispatcher. Asynchronous behaviour may also make use of Seam's @Transactional marker to demarcate tx boundaries. Since testing one of our applications in AS7 I noticed Seam "could not discover transaction status" error messages reported as our application ran async sections of code. Examining the Seam code, I could see that Seam would make two attempts to access a JNDI UserTransaction resource: 1 - context.lookup("java:comp/UserTransaction"); If an NameNotFoundException is thrown, then attempt: 2 - context.lookup("UserTransaction"); Under AS6 and below, the latter attempt would succeed. Under AS7 attempts are currently failing. While looking into this issue I came across the following developer discussion which suggests that it might be possible to add a "java:/jboss/UserTransaction" resource: http://lists.jboss.org/pipermail/jboss-as7-dev/2011-June/002298.html Further discussion on my AS7 user forum thread lead to the suggestion that I myself might add this behaviour. I have followed the implementation hints and light testing has been successful (with appropriate mods to Seam to use the new resource name). I aim to perform some more thorough testing on this shortly and submit a patch against this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
8
0 / 0

[JBoss JIRA] (AS7-2318) Web Console: The log4j/log editor should assist users with configurations/settings that do not make sense

by Jim Tyrrell (Created) (JIRA)

Web Console: The log4j/log editor should assist users with configurations/settings that do not make sense --------------------------------------------------------------------------------------------------------- Key: AS7-2318 URL: https://issues.jboss.org/browse/AS7-2318 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell If the root logger is set to info, it will grab all of the log messages and not allow for a debug logging later on in the hierarchy. This is a support issue as they often have users turn on more logging, but the user has not "turned off" the root logger so it is not able to grab any debug messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

8
10
0 / 0

[JBoss JIRA] Created: (JBAS-8151) Support CRL Validation in the services

by Anil Saldhana (JIRA)

Support CRL Validation in the services -------------------------------------- Key: JBAS-8151 URL: https://jira.jboss.org/browse/JBAS-8151 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 6.0.0.M4 Tomcat connector can do CRL validation (users can download CRL lists from commercial CAs). I would like to see us document our CRL support for the various services. This may force us to write a separate trust manager. Please research. The key here is to document. -- 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

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-8141) Validate the Principal Mapping Framework is configurable/usable for the various services

by Anil Saldhana (JIRA)

Validate the Principal Mapping Framework is configurable/usable for the various services ---------------------------------------------------------------------------------------- Key: JBAS-8141 URL: https://jira.jboss.org/browse/JBAS-8141 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 6.0.0.Final We need to validate that we can use the principal mapping framework with the following services: web, ejb2 and ejb3 -- 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

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8150) Research OCSP support for all services of the JBoss AS

by Anil Saldhana (JIRA)

Research OCSP support for all services of the JBoss AS ------------------------------------------------------ Key: JBAS-8150 URL: https://jira.jboss.org/browse/JBAS-8150 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: 6.0.0.Final I think the tomcat connectors have the capabilities to do ocsp. Not completely sure. But it will be good to have a trust manager that can do ocsp. Starting JDK5, there have been numerous x509 enhancements. We need to document (and beef up the services) to utilize ocsp. -- 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

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (SECURITY-216) Technical White Paper on SSL usage with JBoss

by Anil Saldhana (JIRA)

Technical White Paper on SSL usage with JBoss --------------------------------------------- Key: SECURITY-216 URL: http://jira.jboss.com/jira/browse/SECURITY-216 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: White Papers Reporter: Anil Saldhana Assigned To: Marcus Moyses Fix For: 2.0.2.GA This is one of the most critical white papers of a lot of value for JBoss users, JBoss customers as well as JBoss Support. Reference: http://wiki.jboss.org/wiki/SSLSetup Things to include: 1) Keytool examples 2) Generate CSR 3) Import Cert Chains 4) Tomcat configuration 5) RMISSL Server socket factories 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-345) Create test case for decryption of password with leading zero for SecureIdentityLoginModule

by Marcus Moyses (JIRA)

Create test case for decryption of password with leading zero for SecureIdentityLoginModule ------------------------------------------------------------------------------------------- Key: SECURITY-345 URL: https://jira.jboss.org/jira/browse/SECURITY-345 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.SP3 Reporter: Marcus Moyses Assignee: Marcus Moyses An example of password that would lead to an error in the decryption process is dynamcusr. Create a test case for this to guarantee the error is gone. -- 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

14 years, 9 months

3
2
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 October 2011