September 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5253) [Migration operation] [Web to Undertow] Protocol attribute in ssl configuration of https connector is not properly migrated

by Radim Hatlapatka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5253?page=com.atlassian.jira.plugin.... ] Radim Hatlapatka updated WFLY-5253: ----------------------------------- Affects Version/s: 10.0.0.Beta2 > [Migration operation] [Web to Undertow] Protocol attribute in ssl configuration of https connector is not properly migrated > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5253 > URL: https://issues.jboss.org/browse/WFLY-5253 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Critical > > In Web {{protocol}} attribute of https ssl configuration is used for defining ssl protocols such as TLSv1.2. This attribute isn't properly migrated. Migrate operation defines {{enabled-protocols}} in {{https-listener}} based on Web's {{ssl-protocol}} which is incorrect as {{ssl-protocol}} in Web stands for name of custom ssl protocol provider. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-941) The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-941?page=com.atlassian.jira.plugin... ] Tomaz Cerar closed WFCORE-941. ------------------------------ Fix Version/s: 2.0.0.Beta5 Resolution: Out of Date 2.0.0.Final also has fix which was wildfly core already uses. > The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-941 > URL: https://issues.jboss.org/browse/WFCORE-941 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 1.0.1.Final, 1.0.2.Final > Reporter: Marco Mondini > Fix For: 2.0.0.Beta5 > > > Changing version of the artifact "jboss-javax-sql-api_7.0_spec" to 1.1.1.Final will fix the issue. > (see: https://issues.jboss.org/browse/WFLY-4884) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4884) The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4884?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4884: ----------------------------------- version 2.0.0.Final already has the fix. which is already in master. > The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-4884 > URL: https://issues.jboss.org/browse/WFLY-4884 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final, 9.0.1.Final, 9.x.x TBD > Reporter: Marco Mondini > Assignee: David Lloyd > > jboss-javax-sql-api_7.0_spec module jar does not contains javax/sql/rowset/rowset.properties. > Fix should be trivial, moving the file in the project from src/main/java to src/main/resources will do the job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3971) Jar Services in META-INF/services are not loaded from static modules

by Tomas Repel (JIRA)

[ https://issues.jboss.org/browse/WFLY-3971?page=com.atlassian.jira.plugin.... ] Tomas Repel commented on WFLY-3971: ----------------------------------- Hi [~lucas_k], I can confirm your workaround can be applied on my reproducer as well. Thanks. > Jar Services in META-INF/services are not loaded from static modules > -------------------------------------------------------------------- > > Key: WFLY-3971 > URL: https://issues.jboss.org/browse/WFLY-3971 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 9.0.0.Final, 10.0.0.Alpha6 > Reporter: Tomas Repel > Assignee: Stuart Douglas > > If the web application (war) uses jar file from static module, the content of META-INF/services has no effect. If the jar is located inside WEB-INF/lib, services are loaded successfully. > Neither adding `Dependencies: my.module.name.com services` into MANIFEST.MF nor adding `services="import"` to jboss-deployment-structure.xml works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1954) SWIFT_PING discovery protocol fatal error on OpenStack Kilo

by Thomas Segismont (JIRA)

[ https://issues.jboss.org/browse/JGRP-1954?page=com.atlassian.jira.plugin.... ] Thomas Segismont commented on JGRP-1954: ---------------------------------------- Hi, I'm the contributor of the SWIFT_PING discovery protocol. For the sake of transparency, I contributed it before joining Red Hat and it's a long time I haven't worked with Openstack+JGroups. That said, here's my opinion. A {{ScriptEngine}} based solution sounds more appealing, as it allows to keep the protocol implementation in JGroups. It is possible to write it in a way which is compatible with both Java 7 and Java 8 {code:javascript|title=script.js} var response = JSON.parse(json); var result = {}; result.id = response.access.token.id; var serviceCatalog = response.access.serviceCatalog; for (var i = 0; i < serviceCatalog.length; i++) { var service = serviceCatalog[i]; if (service.type == "object-store") { result.url = service.endpoints[0].publicURL; break; } } result; {code} {code:json|title=response.json} { "access": { "token": { "issued_at": "2014-01-30T15:30:58.819584", "expires": "2014-01-31T15:30:58Z", "id": "aaaaa-bbbbb-ccccc-dddd", "tenant": { "description": null, "enabled": true, "id": "fc394f2ab2df4114bde39905f800dc57", "name": "demo" } }, "serviceCatalog": [ { "endpoints": [ { "adminURL": "http://23.253.72.207:8080", "region": "RegionOne", "internalURL": "http://23.253.72.207:8080/v1/AUTH_fc394f2ab2df4114bde39905f800dc57", "id": "16b76b5e5b7d48039a6e4cc3129545f3", "publicURL": "http://23.253.72.207:8080/v1/AUTH_fc394f2ab2df4114bde39905f800dc57" } ], "endpoints_links": [], "type": "object-store", "name": "swift" } ], "user": { "username": "demo", "roles_links": [], "id": "9a6590b2ab024747bc2167c4e064d00d", "roles": [ { "name": "Member" }, { "name": "anotherrole" } ], "name": "demo" }, "metadata": { "is_admin": 0, "roles": [ "7598ac3c634d4c3da4b9126a5f67ca2b", "f95c0ab82d6045d9805033ee1fbc80d4" ] } } } {code} {code:java|title=Parsing.java} import java.util.Map; import javax.script.Bindings; import javax.script.ScriptEngine; import javax.script.ScriptEngineManager; import javax.script.SimpleBindings; public class Parsing { public static void main(String[] args) throws Exception { ScriptEngine engine = new ScriptEngineManager().getEngineByName("JavaScript"); System.out.println("engine.getFactory().getEngineName() = " + engine.getFactory().getEngineName()); String name = "script.js"; String script = // load script from file; String json = // load response sample from file; Bindings bindings = new SimpleBindings(); bindings.put("json", json); Map<String, String> result = (Map<String, String>) engine.eval(script, bindings); System.out.println("id = " + result.get("id")); System.out.println("url = " + result.get("url")); } } {code} In the actual implementation we'd have to synchronize on the script engine because it may not be thread-safe (depends on the registered implementation). [~nsawadsky] Can you elaborate on your security concern? In the example above, we ask the JS engine to parse a JSON string, we're not evaluating the JSON string. Doesn't that mitigate security risks? > SWIFT_PING discovery protocol fatal error on OpenStack Kilo > ----------------------------------------------------------- > > Key: JGRP-1954 > URL: https://issues.jboss.org/browse/JGRP-1954 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Environment: JGroups client running on Mac OS X - Yosemite > JDK 1.7.71 > OpenStack Kilo > Reporter: Nick Sawadsky > Assignee: Bela Ban > Fix For: 3.6.5 > > > I'm attempting to use the SWIFT_PING discovery protocol on the most recent version of OpenStack, "Kilo". An error occurs during initialization of the protocol stack, the stack trace is provided below. > The problem appears to be that support for XML-formatted responses has been removed in the OpenStack Identity API (http://developer.openstack.org/api-ref-identity-v2.html). Even though SWIFT_PING sends an Accept header of application/xml, the response still comes back as JSON (around line 286 of SWIFT_PING.java). > I've been able to repro the issue using Postman in Chrome. I tried providing the *request* in XML , with a Content-Type header of application/xml, but Swift returns an error: "Expecting to find application/json in Content-Type header". > It seems like the resolution would be for SWIFT_PING to be modified so it can parse the JSON response that it is receiving. If that sounds like a reasonable approach, I can try to create a patch that fixes the issue. > Stack Trace: > 2015-08-21 14:30:16,123 FATAL [com.pingidentity.common.util.ErrorHandler] Problem creating factory for multiplexed cluster communications > org.xml.sax.SAXParseException: Content is not allowed in prolog. > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) ~[?:1.8.0_25] > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:348) ~[?:1.8.0_25] > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) ~[?:1.8.0_25] > at org.jgroups.protocols.SWIFT_PING$Keystone_V_2_0_Auth.authenticate(SWIFT_PING.java:307) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.protocols.SWIFT_PING$SwiftClient.authenticate(SWIFT_PING.java:443) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.protocols.SWIFT_PING.init(SWIFT_PING.java:68) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:860) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.init(JChannel.java:854) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.<init>(JChannel.java:159) ~[jgroups.jar:3.6.4.Final] > at org.jgroups.JChannel.<init>(JChannel.java:120) ~[jgroups.jar:3.6.4.Final] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-941) The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar

by Marco Mondini (JIRA)

Marco Mondini created WFCORE-941: ------------------------------------ Summary: The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar Key: WFCORE-941 URL: https://issues.jboss.org/browse/WFCORE-941 Project: WildFly Core Issue Type: Component Upgrade Affects Versions: 1.0.1.Final, 1.0.2.Final Reporter: Marco Mondini Changing version of the artifact "jboss-javax-sql-api_7.0_spec" to 1.1.1.Final will fix the issue. (see: https://issues.jboss.org/browse/WFLY-4884) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4884) The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar

by Marco Mondini (JIRA)

[ https://issues.jboss.org/browse/WFLY-4884?page=com.atlassian.jira.plugin.... ] Marco Mondini updated WFLY-4884: -------------------------------- Affects Version/s: 9.x.x TBD > The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-4884 > URL: https://issues.jboss.org/browse/WFLY-4884 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final, 9.0.1.Final, 9.x.x TBD > Reporter: Marco Mondini > Assignee: David Lloyd > > jboss-javax-sql-api_7.0_spec module jar does not contains javax/sql/rowset/rowset.properties. > Fix should be trivial, moving the file in the project from src/main/java to src/main/resources will do the job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4884) The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar

by Marco Mondini (JIRA)

[ https://issues.jboss.org/browse/WFLY-4884?page=com.atlassian.jira.plugin.... ] Marco Mondini updated WFLY-4884: -------------------------------- Affects Version/s: 9.0.1.Final > The file javax/sql/rowset/rowset.properties is not present in jboss-javax-sql-api_7.0_spec-1.1.0.Final.jar > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-4884 > URL: https://issues.jboss.org/browse/WFLY-4884 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Final, 9.0.1.Final > Reporter: Marco Mondini > Assignee: David Lloyd > > jboss-javax-sql-api_7.0_spec module jar does not contains javax/sql/rowset/rowset.properties. > Fix should be trivial, moving the file in the project from src/main/java to src/main/resources will do the job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-499) System properties are broken in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-499?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-499: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1257301|https://bugzilla.redhat.com/show_bug.cgi?id=1257301] from POST to MODIFIED > System properties are broken in domain mode > ------------------------------------------- > > Key: WFCORE-499 > URL: https://issues.jboss.org/browse/WFCORE-499 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: Stuart Douglas > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.Alpha17 > > > There seems to be some weirdness in how system properties are being propagated to domain mode servers, and in many cases they are not being applied. > This appears to be an issue with the boot time handling of system properties. > The only way I could get the property to be applied was to start the server first, then add the property using boot-time=false, although even in this case the property will disappear if the domain is restarted or the server is reloaded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-811) Add module for org.wildfly.security.elytron-web:undertow-server

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-811?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFCORE-811: --------------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > Add module for org.wildfly.security.elytron-web:undertow-server > --------------------------------------------------------------- > > Key: WFCORE-811 > URL: https://issues.jboss.org/browse/WFCORE-811 > Project: WildFly Core > Issue Type: Sub-task > Components: Modules > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha1 > > > This is the module that provides the integration between Elytron and Undertow without each needing to be aware of the other. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2015