February 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Signatures and CRs

by alessio.soldano＠jboss.com

"richard.opalka(a)jboss.com" wrote : "alessio.soldano(a)jboss.com" wrote : | | Fortunately this issue only happens when the message is not encrypted. Signature+encryption prevents this since the xml parser works with the encrypted element data. | If we're not able to fix the problem we could suggest our users to use base64 encoding of such strings before putting them to the message payload (the workaround) Yep, this is a workaround too, you're right. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131937#4131937 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131937

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Signatures and CRs

by alessio.soldano＠jboss.com

"richard.opalka(a)jboss.com" wrote : "alessio.soldano(a)jboss.com" wrote : As you can read here http://www.w3.org/TR/REC-xml/#sec-line-ends CRs must be converted in line feeds when parsing. Xerces does this of course, thus the message bytes change and signature (which is obtained using the message containing the CR) is not valid anymore when processing the request message at server side. | | | | From my understanding this have nothing to do with our problem. The above specification says what to do with new-lines only. Our use-case is different. We have element containing | sequence of characters enclosing 0xD character: | Sorry, may be I'm missing something, why this should have nothing to do with our issue? The spec says: "To simplify the tasks of applications, the XML processor MUST behave as if it normalized all line breaks in external parsed entities (including the document entity) on input, before parsing, by translating both the two-character sequence #xD #xA and any #xD that is not followed by #xA to a single #xA character." We have a #xD not followed by #xA that is converted to #xA... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131935#4131935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131935

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Signatures and CRs

by alessio.soldano＠jboss.com

"richard.opalka(a)jboss.com" wrote : I'm not 100 % sure but IMHO such enclosed 0xD character won't be converted to new line by the parser. Try this: | public void testParser() throws Exception | { | String s = "<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Body><a>He\rllo</a></env:Body></env:Envelope>"; | Logger.getLogger(this.getClass()).info("before: "+s); | ByteArrayInputStream bis = new ByteArrayInputStream(s.getBytes()); | Element el = DOMUtils.parse(bis); | Element body = DOMUtils.getChildElements(el).next(); | Element a = DOMUtils.getChildElements(body).next(); | Logger.getLogger(this.getClass()).info(a.getTextContent()); | Logger.getLogger(this.getClass()).info(a.getChildNodes().item(0)); | String res = DOMWriter.printNode(el, false); | Logger.getLogger(this.getClass()).info("after: "+res); | assertEquals(s, res); | } | The \r is converted into in a new line (and the logs show the text node already contains the new line, thus it's created while parsing). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131934#4131934 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131934

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Signatures and CRs

by richard.opalka＠jboss.com

"alessio.soldano(a)jboss.com" wrote : | Fortunately this issue only happens when the message is not encrypted. Signature+encryption prevents this since the xml parser works with the encrypted element data. If we're not able to fix the problem we could suggest our users to use base64 encoding of such strings before putting them to the message payload (the workaround) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131910#4131910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131910

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Signatures and CRs

by richard.opalka＠jboss.com

"alessio.soldano(a)jboss.com" wrote : | We might strip out CR from messages before signing but that would be a poor fix since thirdparty implementations could still produce signatures over messages containing CRs. | Stripping out the CR character from such elements violates the message integrity. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131907#4131907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131907

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Signatures and CRs

by richard.opalka＠jboss.com

I'm not 100 % sure but IMHO such enclosed 0xD character won't be converted to new line by the parser. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131906#4131906 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131906

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Signatures and CRs

by richard.opalka＠jboss.com

"alessio.soldano(a)jboss.com" wrote : As you can read here http://www.w3.org/TR/REC-xml/#sec-line-ends CRs must be converted in line feeds when parsing. Xerces does this of course, thus the message bytes change and signature (which is obtained using the message containing the CR) is not valid anymore when processing the request message at server side. | >From my understanding this have nothing to do with our problem. The above specification says what to do with new-lines only. Our use-case is different. We have element containing sequence of characters enclosing 0xD character: | <some_element>asdf\rjklo</some_element> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131905#4131905 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131905

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Signatures and CRs

by alessio.soldano＠jboss.com

Hi Folks, I spent some time on http://jira.jboss.org/jira/browse/JBWS-2011, I think there aren't straightforward solutions for this, may be somebody else have interesting idea ;-) Here is my analysis: the reason why the signature verification fails when signing messages containing CR (\r i.e. #x0d) is that the WS-Security implementation works with the soap message element that is created parsing the incoming xml message. As you can read here http://www.w3.org/TR/REC-xml/#sec-line-ends CRs must be converted in line feeds when parsing. Xerces does this of course, thus the message bytes change and signature (which is obtained using the message containing the CR) is not valid anymore when processing the request message at server side. We might strip out CR from messages before signing but that would be a poor fix since thirdparty implementations could still produce signatures over messages containing CRs. Btw, if you're wondering whether this should be done by the canonicalization happening before the actual signature is computed, here http://www.w3.org/TR/2001/REC-xml-c14n-20010315#Example-Chars is an example showing the CR is processed and not discarder (we actually use the Exclusive XML canonicalization, but afaik this shouldn't change). Fortunately this issue only happens when the message is not encrypted. Signature+encryption prevents this since the xml parser works with the encrypted element data. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131875#4131875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131875

16 years, 3 months

1
0
0 / 0

Re: [Fwd: [jbossws-dev] User project generator]

by Alessio Soldano

Hi, I'm still using RHDS Beta1, thus I'd say it works with JBDS (considering it uses basic eclipse features), however I'll give it a try soon with JBDS and other Eclipse versions. Honestly I don't know if/how many customer are actually asking for this, but considering my previous user experience this might be really useful; anyway there's been a brainstorm on the dev forum some months ago about ws productivity in general and the idea of doing this generator is part of the efforts we agreed upon to make the ws use easier. Cheers Alessio Burr Sutter ha scritto: > That is great. It has been hard to "get started". > > Do you know if it works with JBDS and EAP 4.2/4.3? > > We have customers asking for this sort of thing right now? > > > > -------- Original Message -------- > Subject: [jbossws-dev] User project generator > Date: Wed, 13 Feb 2008 16:11:45 +0100 > From: Alessio Soldano <asoldano(a)redhat.com> > To: jbossws-dev <jbossws-dev(a)lists.jboss.org> > > > > Hi Folks, > this morning I've written this page on the wiki: > http://jbws.dyndns.org/mediawiki/index.php?title=Setup_your_IDE It's > about the ws-enabled user project generator I committed a couple of > weeks ago (something like the SeamGen tool). > As you can read there, it's meant to provide an easy way to start a web > service user project, without spending a lot of time dealing with > libraries selection, writing an Ant build file and performing basic > Eclipse configuration. > > Richard (or anybody else using Windows), could you please give the > above-mentioned stuff a try (since I tested it with Linux only)? > Apart from the test, this is for native stack only right now. If you > like the idea, once the changes for jbossws 3 are done, I could modify > this stuff to make it available for all the stacks binary releases. > Please let me know what you think about this. > > Thanks > Cheers > Alessio > _______________________________________________ > jbossws-dev mailing list > jbossws-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossws-dev >

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Simplify deploy/undeploy cycles for different stacks

by thomas.diesler＠jboss.com

Merci, we'll look into it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130732#4130732 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130732

16 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev February 2008