2010-05-03 19 views
2

全部, 我(仍)正在從Java/Metro 2.0調用WSE 3.0 .NET Web服務。我們已經設置了安全性要求,以便我們正在對正文&的標頭&進行加密。我可以向他們的服務發送請求&獲得響應,但Metro無法驗證簽名&從WSIT代碼中引發錯誤。我從CVS &最新WSIT代碼以下是方法的代碼片段多數民衆贊成炸掉:Metro&StreamBuffer命名空間錯誤 - 我是否正確理解這一點?

從com.sun.xml.ws.security.opt.impl.incoming.GenericSecuredHeader:

private XMLStreamBuffer completeHeader; 
public void writeTo(XMLStreamWriter w) throws XMLStreamException { 
     try { 
      // TODO what about in-scope namespaces 
      completeHeader.writeToXMLStreamWriter(w); 
     } catch (Exception e) { 
      throw new XMLStreamException(e); 
     } 
    } 

正如你所看到的,那裏有一個TODO,我認爲這個方法不能處理我所遇到的情況,但我不確定我是否知道他們的'範圍內'命名空間是什麼意思。

下面是來自web服務的響應XML的片段,它打破上:

<wsa:Action wsu:Id="Id-46282a5d-c7fa-403c-8ac9-f7df0dfdb0cf"> 
http://someAction</wsa:Action> 
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> 
<SignedInfo> 
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" /> 
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /> 

<Reference URI="#Id-46282a5d-c7fa-403c-8ac9-f7df0dfdb0cf"> 
<Transforms> 
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> 
</Transforms> 
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /> 
<DigestValue> 
/2ivNKDpYSLqPWHzrSxN/RuZ/e8=</DigestValue> 
</Reference> 

在堆棧跟蹤(包含下面),它抱怨不能夠驗證參考URI =「# ID-46282a5d-c7fa-403C-8ac9-f7df0dfdb0cf」。 我不清楚的是 - 它失敗,因爲Reference元素沒有名稱空間屬性或前綴?應該允許它們從父Signature元素繼承名稱空間,還是StreamBuffer類不能處理它?

爲了對比,這裏是從我的請求(由WSIT產生),其中雙鏈前綴是

XMLNS類似XML片段:DS =「http://www.w3.org/2000/09/ xmldsig#「

<ds:Signature xmlns:ns10="http://www.w3.org/2003/05/soap-envelope" 
xmlns:ns11="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" 
xmlns:ns12="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity" Id="_1"> 
<ds:SignedInfo> 
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"> 
<exc14n:InclusiveNamespaces PrefixList="wsse S"/> 
</ds:CanonicalizationMethod> 
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> 

<ds:Reference URI="#_5002"> 
<ds:Transforms> 
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"> 
<exc14n:InclusiveNamespaces PrefixList="S"/> 
</ds:Transform> 
</ds:Transforms> 
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> 
<ds:DigestValue> 
vtf9n+OcI1nT0exavD4/ZQy6jm8=</ds:DigestValue> 
</ds:Reference> 

當Metro生成這些塊時,每件事都有一個名稱空間前綴。

如果你還在讀這麼遠 - 謝謝!以下是堆棧跟蹤中的一些片段:

Error occurred while trying to cache START_ELEMENTcom.sun.xml.stream.buffer.stax 
.StreamReaderBufferProcessor$InternalNamespaceContext 
[16:12:54.026] WSS1759: Following error null occured while performing canonicali 
zation null 
[16:12:54.026] javax.xml.stream.XMLStreamException 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.GenericSecuredHeade 
r.writeTo(GenericSecuredHeader.java:303) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.StreamWriterData.wr 
ite(StreamWriterData.java:101) 
[16:12:54.026] at com.sun.xml.ws.security.opt.crypto.dsig.Exc14nCanonicalizer.t 
ransform(Exc14nCanonicalizer.java:153) 
[16:12:54.026] at com.sun.xml.ws.security.opt.crypto.dsig.Transform.transform(T 
ransform.java:182) 
[16:12:54.026] at com.sun.xml.ws.security.opt.crypto.dsig.Reference.transform(R 
eference.java:183) 
[16:12:54.026] at com.sun.xml.ws.security.opt.crypto.dsig.Reference.validate(Re 
ference.java:102) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.processor.SignedInf 
oProcessor.processReference(SignedInfoProcessor.java:422) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.processor.SignedInf 
oProcessor.processReferences(SignedInfoProcessor.java:385) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.processor.SignedInf 
oProcessor.process(SignedInfoProcessor.java:189) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.Signature.process(S 
ignature.java:206) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.h 
andleSecurityHeader(SecurityRecipient.java:466) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.c 
acheHeaders(SecurityRecipient.java:281) 
[16:12:54.026] at com.sun.xml.ws.security.opt.impl.incoming.SecurityRecipient.v 
alidateMessage(SecurityRecipient.java:223) 
[16:12:54.026] at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.verifyInboundMess 
age(SecurityTubeBase.java:462) 
[16:12:54.026] at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRe 
sponsePacket(SecurityClientTube.java:412) 
[16:12:54.026] at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processResponse 


javax.xml.ws.WebServiceException: com.sun.xml.wss.impl.WssSoapFaultException: WSS1722: Error occurred while validating Reference with URI: #Id-46282a5d-c7fa-403c-8ac9-f7df0dfdb0c 
f 

回答

0

在做了一些更多的研究之後,我相信我對此的最初理解是正確的。調用StreamBuffer代碼以從SOAP響應中流式傳輸XML的Metro/WSIT代碼無法處理那些沒有名稱空間前綴或屬性的元素。我已經提交的問題對WSIT,對於那些在後續有興趣:

https://wsit.dev.java.net/issues/show_bug.cgi?id=1423

+0

你能給我關於這個問題的解決? [請檢查此鏈接](http://stackoverflow.com/questions/28696160/error-while-serializing-timestamp-element-occured-while-performing-canonicalizat) – 2015-02-27 11:53:17