October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3667) UrlResource getLastModified() method does not use authentication

by Matthew Fleming (JIRA)

Matthew Fleming created JBRULES-3667: ---------------------------------------- Summary: UrlResource getLastModified() method does not use authentication Key: JBRULES-3667 URL: https://issues.jboss.org/browse/JBRULES-3667 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.5.0.Beta1, 5.4.0.Final Environment: All environments Reporter: Matthew Fleming Assignee: Mark Proctor Drools supports BASIC authentication when fetching packages via a UrlResource. The implementation is complete for the grabStream() method but is not present for the getLastModified() method. The latter method is used by clients to determine if packages have changed over time. For example, this is use by Guvnor when the KnowledgeAgent (via the ResourceChangeScannerImpl) needs to determine if a remote URL based package has been changed. The defect that happens is swallowed, in that the result of the getLastModified() call returns a zero because of the redirect to whatever authentication is required. So no exception or anything is produced. The client just gets a zero back. The core should be consistent on when it uses authentication and should use it everywhere that URL connections are used. -- 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-5811) [EAP6] tomcatAuthentication attribute on the AJP connector

by Derek Horton (JIRA)

Derek Horton created AS7-5811: --------------------------------- Summary: [EAP6] tomcatAuthentication attribute on the AJP connector Key: AS7-5811 URL: https://issues.jboss.org/browse/AS7-5811 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.0.0.Final Environment: Windows Server 2003 32 bit, IIS 6, tomcat connector 1.2.28 used as an extension Reporter: Derek Horton Assignee: Jean-Frederic Clere Priority: Minor Fix For: 7.2.0.CR1 In JBoss 5.1.0 I could set the tomcatAuthentication attribute of the AJP connector to false to allow IIS to handle the authentication and pass that along to JBoss. I'm wanting to upgrade to JBoss 7 but unable to set this attribute in version 7.0.0 final to make this work. This attribute is descibed in the tomcat documentation at http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html -- 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
1
0 / 0

[JBoss JIRA] (AS7-5803) Remove dependency on org.osgi.enterprise

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5803: ----------------------------------- Summary: Remove dependency on org.osgi.enterprise Key: AS7-5803 URL: https://issues.jboss.org/browse/AS7-5803 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 It is generally considered bad practise to the deploy the compendium/enterprise bundle in the runtime. This is especially problematic when an API exposed by this bundle provides a newer version as an implementation of it. The implementation bundle would use/export the older version of the API, but a consumer of the API would always bind to the newer version and hence not see the services. APIs should be exported by the bundles that implement the API. -- 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
1
0 / 0

[JBoss JIRA] (AS7-5810) Naming context read-only during SAR deployment - EAP 6.0.0

by Brad Maxwell (JIRA)

Brad Maxwell created AS7-5810: --------------------------------- Summary: Naming context read-only during SAR deployment - EAP 6.0.0 Key: AS7-5810 URL: https://issues.jboss.org/browse/AS7-5810 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.1.1.Final Reporter: Brad Maxwell Assignee: Philippe Marschall Fix For: 7.2.0.Alpha1 During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}} http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi... -- 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
1
0 / 0

[JBoss JIRA] (AS7-5809) [EAP6] WSIntegrationProcessorJAXWS_EJB does not process @PermitAll, @DeclareRoles and @RolesAllowed properly

by Derek Horton (JIRA)

Derek Horton created AS7-5809: --------------------------------- Summary: [EAP6] WSIntegrationProcessorJAXWS_EJB does not process @PermitAll, @DeclareRoles and @RolesAllowed properly Key: AS7-5809 URL: https://issues.jboss.org/browse/AS7-5809 Project: Application Server 7 Issue Type: Bug Components: Web Services Reporter: Derek Horton Assignee: Alessio Soldano Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) WSIntegrationProcessorJAXWS_EJB does not process @PermitAll annotation on EJB3 endpoint classes at all, resulting in denied access if no @RolesAllowed/@DeclareRoles provided. Moreover, it erroneously mixes method and class @RolesAllowed annotations. -- 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
1
0 / 0

[JBoss JIRA] (SECURITY-665) Incorrect warning about invalid option passwordIsA1Hash in login modules

by Martin Gencur (JIRA)

Martin Gencur created SECURITY-665: -------------------------------------- Summary: Incorrect warning about invalid option passwordIsA1Hash in login modules Key: SECURITY-665 URL: https://issues.jboss.org/browse/SECURITY-665 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: PicketBox_v4_0_9.Final Reporter: Martin Gencur Assignee: Anil Saldhana As I described in in my last post in https://community.jboss.org/message/744521#744521, I had a problem with DIGEST authentication and passwordIsA1Hash option JBossAS 7. IMO one of the following classes should enlist passwordIsA1Hash option among their valid options: AbstractServerLoginModule, UsernamePasswordLoginModule, UsersRolesLoginModule. Now it's missing and login modules scream that the option is invalid (in my case UsersRolesLoginModule). -- 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

2
2
0 / 0

[JBoss JIRA] (AS7-3739) Add local-only web cache container to enable session persistence in non-HA environments

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3739: --------------------------------- Summary: Add local-only web cache container to enable session persistence in non-HA environments Key: AS7-3739 URL: https://issues.jboss.org/browse/AS7-3739 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.1.Final -- 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

3
4
0 / 0

[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating exception

by Barnabas Bodnar (JIRA)

Barnabas Bodnar created AS7-5432: ------------------------------------ Summary: TransactionRolledbackLocalException doesn't reference the originating exception Key: AS7-5432 URL: https://issues.jboss.org/browse/AS7-5432 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Barnabas Bodnar Assignee: jaikiran pai Priority: Minor If a runtime-exception thrown by an EJB v.2x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()). The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here. This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException(). -- 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

2
6
0 / 0

[JBoss JIRA] (AS7-5806) Upgrade JGroups to 3.2.0.Final

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-5806: --------------------------------- Summary: Upgrade JGroups to 3.2.0.Final Key: AS7-5806 URL: https://issues.jboss.org/browse/AS7-5806 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: No Release Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1 -- 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-5535) Cannot register a host with a - in the name with the domain controller.

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-5535?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber commented on AS7-5535: ------------------------------------------ Sure, I can do that. > Cannot register a host with a - in the name with the domain controller. > ----------------------------------------------------------------------- > > Key: AS7-5535 > URL: https://issues.jboss.org/browse/AS7-5535 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Environment: Cloud Forms deployment of EAP. > Reporter: John Doyle > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 7.2.0.CR1 > > > If hosts are configured with "-" in their name they cannot join the domain. -- 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

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