我想在我的肥皂消息中添加wsse:security。这是我的代码:
public Document signSoapMessage(SOAPMessage message) {
try {
Document doc = message.getSOAPBody().getOwnerDocument();
Crypto crypto = CryptoFactory.getInstance(properties); //File
WSSecHeader secHeader = new WSSecHeader(doc);
secHeader.insertSecurityHeader();
InputStream inStream = new FileInputStream(properties.getProperty("org.apache.ws.security.crypto.merlin.keystore.file"));
KeyStore ks = KeyStore.getInstance("PKCS12");
ks.load(inStream, properties.getProperty("privatekeypassword").toCharArray());
String alias = ks.aliases().nextElement();
X509Certificate cert = (X509Certificate) ks.getCertificate(alias);
WSSecSignature sign = new WSSecSignature(secHeader);
sign.setX509Certificate(cert);
sign.setUserInfo(properties.getProperty("org.apache.ws.security.crypto.merlin.keystore.alias"), properties.getProperty("privatekeypassword"));
sign.setKeyIdentifierType(WSConstants.BST_DIRECT_REFERENCE); // Binary Security Token - SecurityTokenReference
sign.setUseSingleCertificate(true);
sign.setDigestAlgo(DigestMethod.SHA1);
//sign.build(crypto);
Document signedDoc = sign.build(crypto);
return signedDoc;
} catch (SOAPException e) {
e.printStackTrace();
return null;
} catch (WSSecurityException e) {
e.printStackTrace();
throw new RuntimeException("Error: " + e.getMessage());
} catch (IOException e) {
e.printStackTrace();
return null;
} catch (CertificateException e) {
e.printStackTrace();
return null;
} catch (NoSuchAlgorithmException e) {
e.printStackTrace();
return null;
} catch (KeyStoreException e) {
e.printStackTrace();
return null;
}
}
它适用于soapenv:Body(它确实添加了wsu:Id和xmlns:wsu参数)
但是soapenv:Header中有一个额外的元素,它不对这个元素进行签名。没有wsu:Id和xmlns:wsu参数,也缺少一个 ds:Reference。
未签名的肥皂味精示例:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header>
<!-- this element should be signed but is not - NOT WORKING -->
<something>
</something>
</soapenv:Header>
<!-- this element should be signed and It does. -->
<soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
我将程序中的肥皂味精与 SoapUI 项目中的工作肥皂味精进行比较。
当我向 Web 服务发布消息时,出现错误:wsse:InvalidSecurity - Soap Header must be signed
。而在SoupUI中,它确实有效。
所以我的问题是我如何强制WSS4j在soapenv:Header中签署额外的元素?
好的,我已经解决了问题。
通常,此代码应该适用于我的情况。
//strange static method from apache o.O
org.apache.xml.security.Init.init();
List<WSEncryptionPart> wsEncryptionParts = new ArrayList<>();
WSEncryptionPart somethingPart = new WSEncryptionPart("something","somethingNamespace","");
wsEncryptionParts.add(somethingPart);
sign.addReferencesToSign(wsEncryptionParts);
然而,它不起作用。它总是抛出异常:
org.apache.wss4j.common.ext.WSSecurityException: No message with ID 在资源包中找到"noXMLSig" "org/apache/xml/security/resource/xmlsecurity"。最初的例外是 a org.apache.wss4j.common.ext.WSSecurityException and message No 在资源包中找到 ID 为"noEncElement"的消息 "org/apache/xml/security/resource/XMLsecurity">
我找不到我的肥皂消息或代码问题的答案。
但是,在调试了一段时间的org.apache.wss4j.dom.message.WSSecSignature之后。我觉得这门课有些不对劲。我决定修改一个方法构建(加密cr)。
public Document build(Crypto cr) throws WSSecurityException {
LOG.debug("Beginning signing...");
this.prepare(cr);
if (this.getParts().isEmpty()) {
this.getParts().add(WSSecurityUtil.getDefaultEncryptionPart(this.getDocument()));
// --- Here is my edit - And it works!
WSEncryptionPart aaa = new WSEncryptionPart("something","somethingNamespace","");
this.getParts().add(aaa);
// ----------------------------------
} else {
Iterator var2 = this.getParts().iterator();
label33:
while(true) {
while(true) {
if (!var2.hasNext()) {
break label33;
}
WSEncryptionPart part = (WSEncryptionPart)var2.next();
if (part.getId() == null && "STRTransform".equals(part.getName())) {
part.setId(this.strUri);
} else if ("KeyInfo".equals(part.getName()) && "http://www.w3.org/2000/09/xmldsig#".equals(part.getNamespace()) && part.getElement() == null) {
Element keyInfoElement = this.getKeyInfoElement();
part.setElement(keyInfoElement);
}
}
}
}
List<javax.xml.crypto.dsig.Reference> referenceList = this.addReferencesToSign(this.getParts());
this.computeSignature(referenceList);
if (this.bstToken != null) {
this.prependBSTElementToHeader();
}
return this.getDocument();
}
当然,解决方案很弱。然而,至少它现在有效。
最新版本中存在此问题:
wss4j-ws-security-dom 2.2.2
WSS4J-WS-security-common 2.2.2
我想它应该以这种方式工作:
WSSecSignature sign = new WSSecSignature(secHeader);
sign.getParts().addAll(getEncryptionParts());
getEncryptionParts() 是您要添加的 WSEncryptionPart List。 如果以这种方式添加,则 build 方法能够找到它们,而无需修补框架。