我有以下从http://web-gmazza.rhcloud.com/blog/entry/cxf-sts-tutorial的例子中CXF-STS应用程序的工作没有证书。我能够生成SAML断言,但它在遇到服务提供者时失败。CXF服务抛出WSSecurityException:没有发现用于解密(KEYID)
我在服务的PasswordCallback如,
@Override
public void handle(Callback[] callbacks) throws IOException,
UnsupportedCallbackException {
for (int index = 0; index < callbacks.length; index++) {
WSPasswordCallback pc = (WSPasswordCallback)callbacks[index];
int usage = pc.getUsage();
if (usage == WSPasswordCallback.DECRYPT || usage == WSPasswordCallback.SIGNATURE) {
String pass = (String) passwords.get(pc.getIdentifier());
if (pass != null) {
pc.setPassword(pass);
return;
}
}
}
的WSPasswordCallback型被发现,作为秘密密钥或东西,但not WSPasswordCallback.DECRYPT or WSPasswordCallback.SIGNATURE
标识符在上面的代码调试时显示为_0bfaf221-9588-4033-b3fa-db9ecbd478fe
或某些随机文本。在服务提供商我有对称的KeyType结合 - 为
<sp:SymmetricBinding>
<wsp:Policy>
<sp:ProtectionToken>
<wsp:Policy>
<sp:IssuedToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<sp:RequestSecurityTokenTemplate>
<t:TokenType>http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1</t:TokenType>
<t:KeyType>http://docs.oasis-open.org/ws-sx/ws-trust/200512/SymmetricKey</t:KeyType>
<t:KeySize>256</t:KeySize>
</sp:RequestSecurityTokenTemplate>
<wsp:Policy>
<sp:RequireInternalReference/>
</wsp:Policy>
<sp:Issuer>
<wsaw:Address>http://localhost:8080/StsService/services/STS</wsaw:Address>
<wsaw:Metadata>
<wsx:Metadata>
<wsx:MetadataSection>
<wsx:MetadataReference>
<wsaw:Address>http://localhost:8080/StsService/services/STS/mex</wsaw:Address>
</wsx:MetadataReference>
</wsx:MetadataSection>
在STS SymmetricKey结束我提供加密服务提供者的公钥
<bean id="utSTSProperties"
class="org.apache.cxf.sts.StaticSTSProperties">
<property name="signaturePropertiesFile" value="springconfig/keystore.properties"/>
<property name="signatureUsername" value="${stskeyalias}"/>
<property name="callbackHandlerClass" value="com.security.sts.security.StsPasswordCallbackHandler"/>
<property name="encryptionUsername" value="${serverkeyalias}" />
<property name="encryptionPropertiesFile" value="springconfig/keystore.properties" />
<property name="issuer" value="cieron"/>
</bean>
继http://mail-archives.apache.org/mod_mbox/cxf-users/201112.mbox/%[email protected].com%3E和建议http://coheigea.blogspot.in/2011/05/ws-trust-sample-in-talend-service.html
我不确定服务提供程序是如何使用对称密钥的,因为它已被加密。
我已经检查了所有相关文件,一切似乎完好无损。我有我的例子https://github.com/sampleref/CXFSecurity作为参考。运行客户端时出现错误,服务提供商日志显示
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.apache.wss4j.common.ext.WSSecurityException: No certificates were found for decryption (KeyId)
at org.apache.wss4j.dom.processor.EncryptedKeyProcessor.getCertificatesFromEncryptedKey(EncryptedKeyProcessor.java:372)
at org.apache.wss4j.dom.processor.EncryptedKeyProcessor.handleToken(EncryptedKeyProcessor.java:137)
at org.apache.wss4j.dom.saml.WSSSAMLKeyInfoProcessor.processSAMLKeyInfo(WSSSAMLKeyInfoProcessor.java:80)
at org.apache.wss4j.common.saml.SAMLUtil.getCredentialFromKeyInfo(SAMLUtil.java:225)
at org.apache.wss4j.common.saml.SAMLUtil.getCredentialFromSubject(SAMLUtil.java:152)
at org.apache.wss4j.common.saml.SamlAssertionWrapper.parseSubject(SamlAssertionWrapper.java:672)
at org.apache.wss4j.dom.processor.SAMLTokenProcessor.handleSAMLToken(SAMLTokenProcessor.java:193)
at org.apache.wss4j.dom.processor.SAMLTokenProcessor.handleToken(SAMLTokenProcessor.java:79)
at org.apache.wss4j.dom.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:427)
at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:257)
未找到任何证书。请提供一些建议
感谢
谢谢科尔姆,用于识别错误和建议。最后,我可以设置完整的WSC-> STS-> WSC-> WSP流程 – Chakri