May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3224) SSL The Last Round

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3224?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3224: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > SSL The Last Round > ------------------ > > Key: WFLY-3224 > URL: https://issues.jboss.org/browse/WFLY-3224 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.Alpha3 > > > I could probably list most components in the components box, anyway this is a top level task to contain all of the SSL enhancements required so that they can be addressed once and for all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3291) Pass Jandex CompositeIndex into Hibernate 5.x

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3291?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3291: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Pass Jandex CompositeIndex into Hibernate 5.x > ---------------------------------------------- > > Key: WFLY-3291 > URL: https://issues.jboss.org/browse/WFLY-3291 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.Alpha3 > > > 1. When creating the persistence unit for Hibernate 5.x, pass a Jandex composite index via: > integrationMap.put( "hibernate.jandex_index", CompositeIndex.create( pu.getAnnotationIndex().values() ). > 2. Also change from: > integerationMap.put( "hibernate.ejb.resource_scanner", HibernateArchiveScanner.class ) > To: > integrationMap.put( "hibernate.jpa.scanner_archive_delegate", VirtualFileSystemArchiveDescriptorFactory.INSTANCE ) > This may turn out to be a Jipajapa only change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3463) org.apache.cxf.wsdl11.WSDLManagerImpl needs read access to the jre wsdl.properties

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3463?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3463: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > org.apache.cxf.wsdl11.WSDLManagerImpl needs read access to the jre wsdl.properties > ---------------------------------------------------------------------------------- > > Key: WFLY-3463 > URL: https://issues.jboss.org/browse/WFLY-3463 > Project: WildFly > Issue Type: Feature Request > Components: Security Manager > Affects Versions: 9.0.0.CR1 > Reporter: Scott Marlow > Assignee: Alessio Soldano > Fix For: 10.0.0.Alpha3 > > > During TCK testing (with security-manager enabled), I am seeing a java.security.AccessControlException: WFSM000001: Permission check failed for ("java.io.FilePermission" "/qa/tools/opt/x86_64/jdk1.7.0_60/jre/lib/wsdl.properties" "read") > from org.apache.cxf.wsdl11.WSDLManagerImpl. > Some related comments from irc: > {quote} > http://sourceforge.net/p/wsdl4j/patches/1/ > <asoldano> smarlow, I'm currently working around the problem (when running with security manager on) by setting "-Djavax.wsdl.factory.WSDLFactory=com.ibm.wsdl.factory.WSDLFactoryImpl" when starting the jvm > {quote} > Seems related to [https://issues.apache.org/jira/browse/TUSCANY-3925] which also has a patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3491) All key and trust stores should be reloadable.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3491?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3491: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > All key and trust stores should be reloadable. > ---------------------------------------------- > > Key: WFLY-3491 > URL: https://issues.jboss.org/browse/WFLY-3491 > Project: WildFly > Issue Type: Sub-task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.Alpha3 > > > Some stores may need to be self re-loading e.g. detect filesystem changes - others could be on demand via a management op. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3590) Option to disable processing of authentication tokens on unsecured resources.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3590?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3590: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Option to disable processing of authentication tokens on unsecured resources. > ----------------------------------------------------------------------------- > > Key: WFLY-3590 > URL: https://issues.jboss.org/browse/WFLY-3590 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: Oracle Java 1.8.0_05, Ubuntu 14.04 > Reporter: Harald Wellmann > Assignee: Stuart Douglas > Fix For: 10.0.0.Alpha3 > > > WildFly sends a basic authentication challenge and denies access when it shouldn't in the following simple setup: > {code:xml} > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>test</realm-name> > </login-config> > > <security-constraint> > <web-resource-collection> > <web-resource-name>all</web-resource-name> > <url-pattern>/hello</url-pattern> > </web-resource-collection> > <auth-constraint> > <role-name>USER</role-name> > </auth-constraint> > </security-constraint> > > <security-role> > <role-name>USER</role-name> > </security-role> > {code} > {{/hello}} is the only protected URL (mapped to a servlet), other URLs like {{/index.html}} are public. > When GETting /index.html with an (unneeded) basic authentication header, access is denied: > {noformat} > $ curl -v -u foo:bar http://localhost:8080/auth-basic/index.html > * Hostname was NOT found in DNS cache > * Trying 127.0.0.1... > * Connected to localhost (127.0.0.1) port 8080 (#0) > * Server auth using Basic with user 'foo' > > GET /auth-basic/index.html HTTP/1.1 > > Authorization: Basic Zm9vOmJhcg== > > User-Agent: curl/7.35.0 > > Host: localhost:8080 > > Accept: */* > > > < HTTP/1.1 401 Unauthorized > < Connection: keep-alive > * Authentication problem. Ignoring this. > < WWW-Authenticate: Basic realm="test" > < X-Powered-By: Undertow/1 > * Server WildFly/8 is not blacklisted > < Server: WildFly/8 > < Content-Type: text/html;charset=ISO-8859-1 > < Content-Length: 71 > < Date: Mon, 07 Jul 2014 17:28:25 GMT > < > * Connection #0 to host localhost left intact > <html><head><title>Error</title></head><body>Unauthorized</body></html> > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3583) Convert mod_cluster excluded context into an xs:list of host:context

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3583?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3583: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Convert mod_cluster excluded context into an xs:list of host:context > -------------------------------------------------------------------- > > Key: WFLY-3583 > URL: https://issues.jboss.org/browse/WFLY-3583 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.Alpha3 > > > {noformat} > // TODO: Convert into an xs:list of host:context > static final SimpleAttributeDefinition EXCLUDED_CONTEXTS = SimpleAttributeDefinitionBuilder.create(CommonAttributes.EXCLUDED_CONTEXTS, ModelType.STRING, true) > .setAllowExpression(true) > .setDefaultValue(new ModelNode("ROOT,invoker,jbossws,juddi,console")) > .setRestartAllServices() > .build(); > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3573) Adding incorrect JGroups protocol should provide better error description than CNFE

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3573?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3573: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Adding incorrect JGroups protocol should provide better error description than CNFE > ----------------------------------------------------------------------------------- > > Key: WFLY-3573 > URL: https://issues.jboss.org/browse/WFLY-3573 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 10.0.0.Alpha3 > > > As reported by the community user: > {noformat} > [standalone@localhost:9990 / #] list-batch > #1 /subsystem=jgroups/stack=test:add() > #2 /subsystem=jgroups/stack=test/transport=TRANSPORT:add(type="udp",socket-binding=jgroups-udp) > #3 /subsystem=jgroups/stack=test:add-protocol(type=FD_SOCK,socket-binding=jgroups-udp-fd) > [standalone@localhost:9990 / #] run-batch > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.ClassNotFoundException: org.jgroups.protocols.udp from [Module \"org.jboss.as.clustering.jgroups:main\" from local module loader @4d9f6ce5 (finder: local module finder @1da65633 (roots: /home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules,/home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]"}} > [standalone@localhost:9990 / #] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3582) Redesign mod_cluster xml subsystem parsers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3582?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3582: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Redesign mod_cluster xml subsystem parsers > ------------------------------------------ > > Key: WFLY-3582 > URL: https://issues.jboss.org/browse/WFLY-3582 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.Alpha3 > > > As per https://github.com/wildfly/wildfly/pull/6449 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3532) RemoteFailoverTestCase still fails intermittently

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3532?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3532: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > RemoteFailoverTestCase still fails intermittently > -------------------------------------------------- > > Key: WFLY-3532 > URL: https://issues.jboss.org/browse/WFLY-3532 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Richard Achmatowicz > Fix For: 10.0.0.Alpha3 > > > Fail rate is at 1.5% atm. > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF&testNameI... > (making affected version alpha, but indeed its master) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4120) JAX-WS: HandlerChain-Annotation referencing file outside Java Archive causes JBAS015507

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4120?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4120: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > JAX-WS: HandlerChain-Annotation referencing file outside Java Archive causes JBAS015507 > --------------------------------------------------------------------------------------- > > Key: WFLY-4120 > URL: https://issues.jboss.org/browse/WFLY-4120 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.2.0.Final > Environment: Windows 8.1 > Reporter: Manfred Otte > Assignee: Alessio Soldano > Priority: Minor > Fix For: 10.0.0.Alpha3 > > Attachments: testjsr109.war > > > Regarding JSR 109, chapter 6.3 the "handler chain file can also be packaged and specified in the annotation such that, it is accessible as a resource from the ClassPath. At runtime, container providers must first try to access the handler chain file as per the locations specified in JSR-181 specification. Failing that, they must try to access it as a resource from the ClassPath." > The JBoss AS Documentation states that "The war is considered to be a single module, so classes defined in WEB-INF/lib are treated the same as classes in WEB-INF/classes. All classes packaged in the war will be loaded with the same class loader" (https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7). > Following this statements I think it should be fine to have a HandlerChain-annnotated Webservice within a JAR inside a WAR (WEB-INF/lib) referencing a handler chain file that ist not part of the JAR but resides in WEB-INF/classes. However this situation results in > {code} > Internal Server Error > { > "outcome" => "failed", > "failure-description" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"testjsr109.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"testjsr109.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"testjsr109.war\" > Caused by: javax.xml.ws.WebServiceException: JBAS015507: Handler chain config file handlerchain.xml not found in ResourceRoot [root=\"/D:/tools/wildfly-8.2.0.Final/bin/content/testjsr109.war/WEB-INF/lib/testjsr109.jar\"]"}}, > "rolled-back" => true > } > {code} > The implementation of org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor seems to expect, that the handler chain file is always part of the ResourceRoot the annotated WebService lives in. With respect to JSR 109 I think that this expectation is wrong and that a handler chain file outside the JAR is a valid scenario. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2015