[
https://issues.jboss.org/browse/JGRP-1954?page=com.atlassian.jira.plugin....
]
Nick Sawadsky commented on JGRP-1954:
-------------------------------------
Yes, I think you're right, that should avoid the security risks I was concerned about
(I thought the code would have to eval the JSON string that was returned). As long as
JSON.parse is available, that seems like a good way to go. There are some posts about
JSON.parse not being available when running on Java 6, but hopefully that is resolved in
Java 7 and later.
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)