October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-758) AdvancedLdapLoginModule doesn't isn't mapping nested roles

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-758?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-758: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017974|https://bugzilla.redhat.com/show_bug.cgi?id=1017974] from MODIFIED to ON_QA > AdvancedLdapLoginModule doesn't isn't mapping nested roles > ---------------------------------------------------------- > > Key: SECURITY-758 > URL: https://issues.jboss.org/browse/SECURITY-758 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_6 > > > The recursive role searching is currently broken, believed to be caused by the introduction of quotes for a previous role searching fix. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1094) Use own JSSE Provider for http Connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1094?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1094: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 956391|https://bugzilla.redhat.com/show_bug.cgi?id=956391] from MODIFIED to ON_QA > Use own JSSE Provider for http Connector > ---------------------------------------- > > Key: WFLY-1094 > URL: https://issues.jboss.org/browse/WFLY-1094 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (JBoss Web) > Affects Versions: 8.0.0.Alpha1 > Reporter: Hauke Mehrtens > Assignee: Tomaz Cerar > Labels: https, jsse, ssl > Fix For: 8.0.0.Alpha1 > > Attachments: ssl-protocol.patch > > > We are using our own JSSE Provider implementation for TLS to add support for HTTPS with preshared key to one http connector, while the others still use the default JSSE provider. > In JBoss 5 we added sslProtocol="RFC4279", while RFC4279 is the name of our provider, to one Connector entry in the file server/default/deploy/jbossweb.sar/server.xml. This option is not available in JBoss 7.1 any more and we could not find a way to make one connector use our provider while the others are using the default one. > To fix this issue for use we used the attached patch. We would like to get this patch into the next version of JBoss, so we do not have to modify the source code by our self any more. This patch was tested with JBoss 7.1.2, but it still applies against the master branch. If we should do any changed to the patch or if you want to get it in an other form please inform us. > With this patch we are able to specify our JSSE provider like this: > {code:xml} > <connector name="httpspsk" protocol="HTTP/1.1" scheme="https" socket-binding="httpspsk" secure="true"> > <ssl name="ssl" key-alias="intended purpose ssl test from bremen online services" password="123456" certificate-key-file="${jboss.server.config.dir}/governikus_ssl.jks" protocol="ALL" keystore-type="JKS" ssl_protocol="RFC4279"/> > </connector> > {code} > This is related to Red Hat Customer Portal support case 00721624 "Additional JSSE Provider on socket bindings and connectors" -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-74) REMJMX-65 Overzealous disabling local authentication

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-74?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-74: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1021630|https://bugzilla.redhat.com/show_bug.cgi?id=1021630] from MODIFIED to ON_QA > REMJMX-65 Overzealous disabling local authentication > ---------------------------------------------------- > > Key: REMJMX-74 > URL: https://issues.jboss.org/browse/REMJMX-74 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.2.Final, 2.0.0.CR4 > > > REMJMX-65 is overzealous at disabling local authentication, if a username and credential is supplied in the environment then it does make sense to disable local authentication - however the availability of a callback handler is not a sufficient flag to also disable it. > In the case of the callback handler the user may still only want to be prompted if the other mechanisms fail. > This issue will remove the disabling of local authentication based on the presence of a callback handler and will instead add a configuration option that can be set on the environment. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-88) Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-88?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-88: --------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 952746|https://bugzilla.redhat.com/show_bug.cgi?id=952746] from MODIFIED to ON_QA > Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC > -------------------------------------------------------------------------------------------- > > Key: WFLY-88 > URL: https://issues.jboss.org/browse/WFLY-88 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, Remoting > Reporter: Ivo Studensky > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > Attachments: logs_prepareHaltClient.tgz > > > It looks like recovery process is not fully triggered on a distributed transaction when the transaction falls down at prepare phase of 2PC. In the new crash recovery tests over propagated transactions only one of two servers recovers from the crash, but the other keeps an unfinished tx in its tx log. > It corresponds to prepareHaltClient and prepareHaltServer test methods of org.jboss.as.test.jbossts.crashrec.txpropagation.TxPropagationCrashRecoveryTestCase, see JBQA-2604 for general description of the new tests. The prepareHaltClient test crashes the server which initiated the transaction, while as the prepareHaltServer test crashes the second server. > The tests are written against EAP6.x branch, so for reproducing this it is needed a built server from the 7.1 branch of AS7. > Steps to reproduce. > 1. git clone -b as7 git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-transactions.git > 2. cd eap-tests-transactions > 3. git checkout tx_propag_crashrec_tests > 4a. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltClient -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > or > 4b. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltServer -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > The logs of prepareHaltClient run attached to this jira. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-761) Release JBoss Negotiation 2.2.6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-761?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-761: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017974|https://bugzilla.redhat.com/show_bug.cgi?id=1017974] from MODIFIED to ON_QA > Release JBoss Negotiation 2.2.6 > ------------------------------- > > Key: SECURITY-761 > URL: https://issues.jboss.org/browse/SECURITY-761 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_6 > > -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-760) Make the JBoss Negotiation dependency on JBoss Web - Provided

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-760?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-760: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1022679|https://bugzilla.redhat.com/show_bug.cgi?id=1022679] from MODIFIED to ON_QA > Make the JBoss Negotiation dependency on JBoss Web - Provided > ------------------------------------------------------------- > > Key: SECURITY-760 > URL: https://issues.jboss.org/browse/SECURITY-760 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_6 > > -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2357) OperationStepHandlers do not properly check if runtime steps should be added

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2357?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2357: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1021633|https://bugzilla.redhat.com/show_bug.cgi?id=1021633] from MODIFIED to ON_QA > OperationStepHandlers do not properly check if runtime steps should be added > ---------------------------------------------------------------------------- > > Key: WFLY-2357 > URL: https://issues.jboss.org/browse/WFLY-2357 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.CR1 > > > Currently only checks if the process type is a server which would add runtime steps if booted in admin only mode. This should use the {{OperationContext.isNormalServer()}} instead. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-369) Domain mode: kill an unresponsive JVM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-369?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-369: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 901232|https://bugzilla.redhat.com/show_bug.cgi?id=901232] from MODIFIED to ON_QA > Domain mode: kill an unresponsive JVM > ------------------------------------- > > Key: WFLY-369 > URL: https://issues.jboss.org/browse/WFLY-369 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Dennis Reed > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > If an AS instance gets into a state where it cannot be controlled normally by the host controller, local OS commands must be used to kill it. > It would be helpful to be able to kill an unresponsive JVM through the management interface. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-158) Constant fields that are not final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-158?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-158: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 926050|https://bugzilla.redhat.com/show_bug.cgi?id=926050] from MODIFIED to ON_QA > Constant fields that are not final > ---------------------------------- > > Key: WFLY-158 > URL: https://issues.jboss.org/browse/WFLY-158 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > Attachments: non-final-fields.txt > > > Analysis by Stephan Mueller shows that the AS codebase includes a significant number of public constant fields that are missing the "final" keyword, which could allow incorrect or nefarious code to change them. This task is to fix these. > As part of the work for a few cases I'll reduce the field visibility. > I'll attach file listing the cases. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2371) SizeRotatingHandlerTestCase.rotationTest fails with "the file is bigger than allowed size"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2371?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2371: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1020339|https://bugzilla.redhat.com/show_bug.cgi?id=1020339] from MODIFIED to ON_QA > SizeRotatingHandlerTestCase.rotationTest fails with "the file is bigger than allowed size" > ------------------------------------------------------------------------------------------ > > Key: WFLY-2371 > URL: https://issues.jboss.org/browse/WFLY-2371 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Petr Kremensky > Assignee: Petr Kremensky > > The test org.jboss.as.test.integration.logging.operations.SizeRotatingHandlerTestCase.rotationTest consistently fails with: > java.lang.AssertionError: This file is bigger than allowed rotate-size: size-rotating-reload-rotationTest.log.1 > Link to job: > https://jenkins.mw.lab.eng.bos.redhat.com/job/eap-6x-manu-acceptance-as-t... -- 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

12 years, 6 months

1
0
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 2013