XML数字签名验证引发ResourceResolvexception-Java升级后
我正在将一个在Java6中稳定的应用程序更新为Java8。应用程序使用SAML身份验证,该身份验证现在在Java更新后的验证期间中断 我的验证代码:XML数字签名验证引发ResourceResolvexception-Java升级后,java,xml,xml-parsing,digital-signature,saml,Java,Xml,Xml Parsing,Digital Signature,Saml,我正在将一个在Java6中稳定的应用程序更新为Java8。应用程序使用SAML身份验证,该身份验证现在在Java更新后的验证期间中断 我的验证代码: public static boolean isValid(Element target, KeySelector keySelector) { NodeList nodeList = target.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature"); Node sigNo
public static boolean isValid(Element target, KeySelector keySelector) {
NodeList nodeList = target.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
Node sigNode = nodeList.item(0);
DOMValidateContext context = new DOMValidateContext(keySelector, sigNode);
XMLSignatureFactory factory = XMLSignatureFactory.getInstance();
try {
XMLSignature signature = factory.unmarshalXMLSignature(context);
if (!signature.validate(context)) { // Throws an XMLSignatureException
....
堆栈跟踪如下所示:
java.lang.RuntimeException: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID [5db62480-f1ce-4ea1-be81-b1ebdcb1d9ec]
....
Caused by: javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID [5db62480-f1ce-4ea1-be81-b1ebdcb1d9ec]
at org.jcp.xml.dsig.internal.dom.DOMReference.dereference(DOMReference.java:436) ~[na:1.8.0_20]
at org.jcp.xml.dsig.internal.dom.DOMReference.validate(DOMReference.java:398) ~[na:1.8.0_20]
at com.mycompany.commons.authentication.saml.common.SignatureUtil.isValid(SignatureUtil.java:154) ~[classes/:na]
... 24 common frames omitted
Caused by: javax.xml.crypto.URIReferenceException: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID [5db62480-f1ce-4ea1-be81-b1ebdcb1d9ec]
at org.jcp.xml.dsig.internal.dom.DOMURIDereferencer.dereference(DOMURIDereferencer.java:121) ~[na:1.8.0_20]
at org.jcp.xml.dsig.internal.dom.DOMReference.dereference(DOMReference.java:430) ~[na:1.8.0_20]
... 26 common frames omitted
Caused by: com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolverException: Cannot resolve element with ID [5db62480-f1ce-4ea1-be81-b1ebdcb1d9ec]
at com.sun.org.apache.xml.internal.security.utils.resolver.implementations.ResolverFragment.engineResolveURI(ResolverFragment.java:89) ~[na:1.8.0_20]
at com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolver.resolve(ResourceResolver.java:300) ~[na:1.8.0_20]
at com.sun.org.apache.xml.internal.security.utils.resolver.ResourceResolver.resolve(ResourceResolver.java:285) ~[na:1.8.0_20]
at org.jcp.xml.dsig.internal.dom.DOMURIDereferencer.dereference(DOMURIDereferencer.java:114) ~[na:1.8.0_20]
... 27 common frames omitted
我一直在努力调试它,因为我无法进入源代码,但我已经设法缩小了一点。根据这一点,验证分为两个阶段:签名和参考。我在参考阶段遇到了一个例外。下面的修订更好地隔离了这个问题
...
XMLSignatureFactory factory = XMLSignatureFactory.getInstance();
try {
XMLSignature signature = factory.unmarshalXMLSignature(context);
List<Reference> references = DOMSignedInfo.getSignedInfoReferences(signature.getSignedInfo());
// A DOMURIReference, its URI matches the value of the ID we are searching for
Reference reference = references.get(0);
// The Reference component was what was breaking in the XMLSignature.validate method
reference.validate(context); // Throws XMLSignatureException
。。。
XMLSignatureFactory=XMLSignatureFactory.getInstance();
试一试{
XMLSignature=factory.unmarshalXMLSignature(上下文);
列表引用=DOMSignedInfo.GetSignedInReferences(signature.getSignedInfo());
//一个域引用,其URI与我们正在搜索的ID的值匹配
Reference=references.get(0);
//引用组件是XMLSignature.validate方法中出现的问题
reference.validate(context);//抛出XMLSignatureException
还值得注意的是,我可以从上面的引用
组件中获得节点
,它是一个URI属性,其值与堆栈跟踪中报告的ID匹配,只是它的前缀是“#”。我感觉我越来越接近了,但即使我可以将此URI属性设置为ID类型,它仍然找不到,因为当ResolverFragment类尝试按ID获取元素时,ID搜索参数没有“#”前缀
根问题的详细信息如下:。在此链接中,注意到以下解决方案选项:
- 我不确定这是否是我的一个选项,它看起来不像我拥有SAML XML。至少,我还没有找到它…我尝试过按描述的方式以编程方式设置它,但它不起作用
- 不确定在方法参数中放入什么,或者这是否适用于我的情况。第一个方法参数调用一个元素,但我处理的是javax.xml.crypto.dsig.Reference
- 这里的主要问题是,我对UrideReference如何实现自定义的功能知之甚少。如果我可以访问正在使用的DomuridReference源代码,我会知道更多
参考
组件,这些组件似乎在我面临的问题中发挥了重要作用
我该如何解决这个问题?请帮助!我的问题是我在
参考上挂起了太多的电话,对我正在使用的XML文档没有足够的了解
虽然我还没有真正看到XML,但通过调试,我可以推断它看起来像这样
<Response>
<Issuer>
<Status>
<StatusCode>
</Status>
<Assertion ID="THE ID WE NEED!!!!!">
<Issuer>
</Issuer>
<Subject>
<NameID
</Subject>
<Conditions NotBefore=".." NotOnOrAfter="...">
</Conditions
<AttributeStatement>
<Attribute Name="...">
</Attribute>
<Attribute>
</Attribute>
...
</AttributeStatement>
<Signature dsig="...">
<SignedInfo>
<CanonicalizationMethod Algorithm="...">
<SignatureMethod Algorithm="...">
<Reference uri="#...">
</SignedInfo>
<SignatureValue>
...
</SignatureValue>
<KeyInfo>
</KeyInfo>
</Signature>
</Assertion>
</Response>
我希望验证SOAP信封的主体部分,我让这段代码正常工作(我必须使用“id”小写字母,否则就不行了):
XML看起来像:
<soapenv:Body wsu:id="id-540d03b42e954c4ab5e3624b305b42fb4" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
谢谢你的帮助
DOMValidateContext valContext = new DOMValidateContext(publicKey, nl.item(0));
NodeList nlb = doc.getElementsByTagNameNS("http://schemas.xmlsoap.org/soap/envelope/", "Body");
valContext.putNamespacePrefix("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd", "wsu");
Node body = nlb.item(0);
valContext.setIdAttributeNS((Element)body, "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd", "id");
<soapenv:Body wsu:id="id-540d03b42e954c4ab5e3624b305b42fb4" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">