October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-700) CLONE - AdvancedLdapLoginModule behavior should be aligned with LdapExtLoginModule

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-700?page=com.atlassian.jira.plug... ] Josef Cacek closed SECURITY-700. -------------------------------- I'm closing it as a documentation issue. (c.f. comments in JBPAPP-10173) > CLONE - AdvancedLdapLoginModule behavior should be aligned with LdapExtLoginModule > ---------------------------------------------------------------------------------- > > Key: SECURITY-700 > URL: https://issues.jboss.org/browse/SECURITY-700 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Josef Cacek > Assignee: Darran Lofthouse > > AdvancedLdapLoginModule is based on LdapExtLoginModule, but behavior differs for some configurations. > Testcase > https://github.com/kwart/jboss-as/blob/JBQA-5129-jboss-negotiation-master... > Failing test methods: > 1) test2 - role mapping object (roleAttributeIsDN==true) is not used as a role object itself. I.e. jduke role is not assigned to jduke user by AdvancedLdapLoginModule. The LdapExtLoginModule includes the jduke role - the change was based on JBAS-3312 > 2) test4 - recursion in AdvancedLdapLoginModule is enabled only if the roleAttributeIsDN module option is true. This is not required in LdapExtLogiModule. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-4929) JBoss7 Fails ASV Scan Report Attestation of Scan Compliance

by Carlos Oliva (JIRA)

Carlos Oliva created AS7-4929: --------------------------------- Summary: JBoss7 Fails ASV Scan Report Attestation of Scan Compliance Key: AS7-4929 URL: https://issues.jboss.org/browse/AS7-4929 Project: Application Server 7 Issue Type: Quality Risk Affects Versions: 7.0.2.Final Environment: Centos Reporter: Carlos Oliva Fix For: 7.0.2.SP1 ASV Scan Report Attestation of Scan Compliance. Vulnerabilities Noted for each IP Address https (tcp/443) GET /LETtoaCuluFoy4DePCwPLiT0HI1s36zHz9s712uSci 4zxnjnmPAmXpdcnGMYmVwDfBGtXI6zXgIJ1YC8lqJ0T YlUP8hajSNTWZJH7RUk1K6JHLGgGnDaMfSojaxweHvj cnRe3KKTJ8miLU3U3XnS4KZ4bihRqT2rIkowzQJHSk9 VbbQ26pdrzLoImGB4v9lqUFyewXsahnz55dwjEDBNRE ZEbS7b67a<font%20size=50>DEFACED<!--//-- : MyWebServer 1.0.2 is vulnerable to HTML injection. Upgrade to a later version. CVE-2002-1453 Medium 4.3 Fail http (tcp/80) GET /LNSAZoL2iuV3PmcrZl0W5YhMwILOBPbZwzEHVi5QAM dlOJcFL6Y0Ihv21bU7R3461Q80T3CFq9WqFvx3lfcgs MIZ4MDac8YVcxkBralskmulwlrf5JnvLuewKZ402AkB LBIK0CZY7ajOn7U9xzZ0LAgwAzrUaw9UViczNtTyvEK hm7WnyF5dfR084QH966s324XgjXktxVXXaqe7xtf3d5 bTukJXDoo<font%20size=50>DEFACED<!--//-- : MyWebServer 1.0.2 is vulnerable to HTML injection. Upgrade to a later version. CVE-2002-1453 -- 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, 9 months

4
15
0 / 0

[JBoss JIRA] (AS7-5736) Console: unable to change default-cache

by Heiko Braun (JIRA)

Heiko Braun created AS7-5736: -------------------------------- Summary: Console: unable to change default-cache Key: AS7-5736 URL: https://issues.jboss.org/browse/AS7-5736 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5275) Vault shared key is displaying the byte[] address

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5275: -------------------------------- Summary: Vault shared key is displaying the byte[] address Key: AS7-5275 URL: https://issues.jboss.org/browse/AS7-5275 Project: Application Server 7 Issue Type: Bug Components: Security Environment: AS7 trunk branch Reporter: Jeff Mesnil Assignee: Anil Saldhana Priority: Critical I added a secured attribute with vault.sh but the shared key looked suspicious: {noformat} ******************************************** Vault Block:HQ Attribute Name:thePass Shared Key:[B@52621f0c Configuration should be done as follows: VAULT::HQ::thePass::[B@52621f0c ******************************************** {noformat} Looking at VaultSession#attributeCreatedDisplay(), the byte[] handshakeKey is displayed by calling toString() => this displays its address, not a textual representation of the bytes. When the shared key is read in RuntimeVaultReader, we call String.getBytes() to get back the byte[]. A simple fix is to display the handshakeKey with new String(handshakeKey). However this will work only if the default charset is the same on machines that store the secured attribute and read from it. It'd be safe to use always the same Charset (e.g. US-ASCII or UTF-8). I've raised the priority to critical since it is not possible to use any secured attribute if the handshake is not properly displayed -- 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, 9 months

4
6
0 / 0

[JBoss JIRA] (AS7-5724) Fix logging rollback handlers

by James Perkins (JIRA)

James Perkins created AS7-5724: ---------------------------------- Summary: Fix logging rollback handlers Key: AS7-5724 URL: https://issues.jboss.org/browse/AS7-5724 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Logging rollback handlers don't seem to be working at all. Really a snapshot should be taken of the LogContext or at least it's configuration and then rolledback in the rollback handler. Re-executing the opposite OSH (e.g. remove rollback invokes add) could be invoked in the incorrect order causing errors rolling back. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5674) Restart fails when many bundles deployed

by David Bosschaert (JIRA)

David Bosschaert created AS7-5674: ------------------------------------- Summary: Restart fails when many bundles deployed Key: AS7-5674 URL: https://issues.jboss.org/browse/AS7-5674 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Affects Versions: 7.2.0.Alpha1 Environment: AS7 master (Oct 3 codebase) Reporter: David Bosschaert Assignee: Thomas Diesler I install a fairly large number of OSGi bundles into AS7 using a script (40+ bundles). The script installs the bundles as follows: {{jboss-cli.sh -c --command="deploy bundle_x.jar"}} The installation itself completes without error. Then I stop AS7 (git ctrl-c) and restart it again. At that point I get an exception: POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."cxf-bundle-minimal-2.5.4.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "cxf-bundle-minimal-2.5.4.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_35] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_35] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_35] Caused by: java.lang.NullPointerException at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.deploy(JaxrsScanningProcessor.java:106) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 5 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
9
0 / 0

[JBoss JIRA] (AS7-5561) incorrect command name in error message reported by jboss-cli

by Cheng Fang (JIRA)

Cheng Fang created AS7-5561: ------------------------------- Summary: incorrect command name in error message reported by jboss-cli Key: AS7-5561 URL: https://issues.jboss.org/browse/AS7-5561 Project: Application Server 7 Issue Type: Bug Components: Server Reporter: Cheng Fang Assignee: Jason Greene When reporting invalid options, jboss-cli uses the hard-coded name ./domain.sh, even if the actual command is standalone.sh, standalone.bat. Could be from this class: org.jboss.as.process.ProcessMessages @Message(id = Message.NONE, value = "Usage: ./domain.sh [args...]%nwhere args include:") String argUsage(); I also suggest removing the leading ./ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1820) Remove references to "UsingBatchUpdates" from the *-persistence-service.xml files and the documentation.

by Justin Bertram (JIRA)

Remove references to "UsingBatchUpdates" from the *-persistence-service.xml files and the documentation. -------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1820 URL: https://jira.jboss.org/browse/JBMESSAGING-1820 Project: JBoss Messaging Issue Type: Task Components: Configuration and Management, Documentation and Training Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP10 Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 1.4.0.SP3.CP11, 1.4.8.GA This feature was removed in JBoss Messaging 1.4.0.CR2, but the documentation and configuration files were never updated. -- 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, 9 months

3
14
0 / 0

[JBoss JIRA] (AS7-5725) How do i provide JVM arguments for heap size

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-5725?page=com.atlassian.jira.plugin.s... ] David Lloyd deleted AS7-5725: ----------------------------- > How do i provide JVM arguments for heap size > -------------------------------------------- > > Key: AS7-5725 > URL: https://issues.jboss.org/browse/AS7-5725 > Project: Application Server 7 > Issue Type: Clarification > Environment: RHEL 5 > Reporter: Peddi Praveen > Labels: jboss > > Im unable to set the JVM arguments in clustered environment, i have provided the JVM values in host.xml of the managed server as below > <jvms> > <jvm name="default"> > <heap size="768m" max-size="768m"/> > <permgen size="128m" max-size="384m"/> > <jvm-options> > <option value="-server"/> > </jvm-options> > </jvm> > </jvms> > And when i grep the process ID i see that min heap size is 64m instead of 768m. > Is there any other location that i need provide these JVM settings? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-9518) Jboss migration 4.3 to 5.1 : ORA-01017: invalid username/password; logon denied

by Nandakumar Subramanian (JIRA)

Nandakumar Subramanian created JBAS-9518: -------------------------------------------- Summary: Jboss migration 4.3 to 5.1 : ORA-01017: invalid username/password; logon denied Key: JBAS-9518 URL: https://issues.jboss.org/browse/JBAS-9518 Project: Application Server 3 4 5 and 6 Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB, JPA / Hibernate Affects Versions: JBossAS-5.1.0.GA Reporter: Nandakumar Subramanian Assignee: Carlo de Wolf Fix For: JBossAS-5.1.0.GA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
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 2012