August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5309) Use JBoss rebuild of jaxb

by Paul Gier (JIRA)

Paul Gier created AS7-5309: ------------------------------ Summary: Use JBoss rebuild of jaxb Key: AS7-5309 URL: https://issues.jboss.org/browse/AS7-5309 Project: Application Server 7 Issue Type: Enhancement Components: Build System, XML Frameworks Reporter: Paul Gier Assignee: Paul Gier Fix For: 7.1.3.Final (EAP) The jaxb jars from java.net contain repackaged classes brought in from other projects. A rebuild of jaxb which does not include these classes should be used in AS7 for easier support. The external projects (for example, istack-commons and dtd-parser) should be included in the build via Maven dependencies and set up as modules in AS7. -- 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

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] (AS7-5156) Management doesn't work with vaulted passwords in security realm correctly

by Andy Goldstein (JIRA)

Andy Goldstein created AS7-5156: ----------------------------------- Summary: Management doesn't work with vaulted passwords in security realm correctly Key: AS7-5156 URL: https://issues.jboss.org/browse/AS7-5156 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.2.Final (EAP) Reporter: Andy Goldstein I've been trying to get a vaulted password working with the management interface (e.g. http://localhost:9990), but it isn't working for me. I've tried EAP 6 and I've also built the latest from the 7.1 git branch locally, and neither is successful. I think I've narrowed it down to the unmaskUsersPasswords method in org.jboss.as.domain.management.security.SecurityRealmAddHandler. It looks like when the for loop gets the list of properties to iterate through via users.get(USER).asPropertyList(), I think it's actually cloning each individual property. This means the property loop variable is essentially thrown away after looping, and the users variable remains unmodified. I have stepped through the debugger and can see the vault correctly decrypting my password, but when this method exits, it is no longer decrypted. I'd be happy to provide sample configuration files if necessary. Please let me know if you need more information. -- 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

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] (JBJCA-859) Byteman 2.0.4

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-859: ------------------------------------- Summary: Byteman 2.0.4 Key: JBJCA-859 URL: https://issues.jboss.org/browse/JBJCA-859 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta2 -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (SECURITY-682) Check if the vault certificate has expired

by Anil Saldhana (JIRA)

Anil Saldhana created SECURITY-682: -------------------------------------- Summary: Check if the vault certificate has expired Key: SECURITY-682 URL: https://issues.jboss.org/browse/SECURITY-682 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana Should go along with SECURITY-681. Check if the certificate has expired. If it has there should be a way to migrate the default vault implementation with a new keystore. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-681) Migrate the vault to use a new certificate

by Anil Saldhana (JIRA)

Anil Saldhana created SECURITY-681: -------------------------------------- Summary: Migrate the vault to use a new certificate Key: SECURITY-681 URL: https://issues.jboss.org/browse/SECURITY-681 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Stefan Guilhen If the certificate defining the keypair in the keystore has expired, the user should be able to migrate the vault to use a new keypair. An investigation is needed. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5268) Domain server prematurely tells HostController it is started

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5268: ------------------------------------- Summary: Domain server prematurely tells HostController it is started Key: AS7-5268 URL: https://issues.jboss.org/browse/AS7-5268 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 HostControllerServerClient tells the HC the server is started as soon as it's done registering the channel. This is premature and should be deferred until the ModelController boot is done. -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-3253) Test DS connection in pool, gone?

by Heiko Braun (Created) (JIRA)

Test DS connection in pool, gone? --------------------------------- Key: AS7-3253 URL: https://issues.jboss.org/browse/AS7-3253 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Braun Fix For: 7.1.0.Final There used to be an operation to verify a datasource connection. On recent master it's gone? [ERROR] "outcome" => "failed", [ERROR] "failure-description" => "JBAS015850: No handler for operation test-connection-in-pool at address [ [ERROR] (\"profile\" => \"default\"), [ERROR] (\"subsystem\" => \"datasources\"), [ERROR] (\"data-source\" => \"ExampleDS\") [ERROR] ]", -- 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

13 years, 11 months

4
3
0 / 0

[JBoss JIRA] (JBRULES-3603) Package_readonly rights

by abhijit passi (JIRA)

abhijit passi created JBRULES-3603: -------------------------------------- Summary: Package_readonly rights Key: JBRULES-3603 URL: https://issues.jboss.org/browse/JBRULES-3603 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.0.FINAL Environment: Windows, brms-standalone-5.1.0 Reporter: abhijit passi Assignee: Mark Proctor Priority: Blocker I created a user in BRMS and gave him Package_readonly rights. In the package where I had decision tables I could download, make changes to DT and upload it back in BRMS and it threw no exception. Something like this worked perfectly when I create business rules inside BRMS. I am using .xls for DT -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-5220) tmp/auth/ challenge files are not deleted when access is via a remote client

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-5220?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved AS7-5220. ----------------------------------- Resolution: Done > tmp/auth/ challenge files are not deleted when access is via a remote client > ---------------------------------------------------------------------------- > > Key: AS7-5220 > URL: https://issues.jboss.org/browse/AS7-5220 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > the authentication process that creates temporary files in tmp/auth is not deleting them when a JMX client connects. > At an extreme, this would be a DOS attack, as the disk could fill up. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2301) Get rid of System.out.println statement

by Juraj Tomasov (JIRA)

Get rid of System.out.println statement --------------------------------------- Key: JBRULES-2301 URL: https://jira.jboss.org/jira/browse/JBRULES-2301 Project: Drools Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.M1 Reporter: Juraj Tomasov Assignee: Mark Proctor Priority: Minor System.out.println statement is currently used in 280 project files. I propose to replace them with logger. -- 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, 11 months

9
18
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 August 2012