The error is that your (STS) client is not configured with the Encryption
Crypto information it needs to communicate with the STS. If you look at
section 6 in Glen's tutorial that you referenced, the client is configured
with:
<property name="properties">
<map>
<entry key="ws-security.username" value="alice" />
<entry key="ws-security.callback-handler"
value="client.ClientCallbackHandler" />
<entry key="ws-security.encryption.properties"
value="clientKeystore.properties" />
<entry key="ws-security.encryption.username" value="mystskey" />
</map>
</property>
The last two properties are the location of the Crypto properties file,
which contains the information about which keystore to use, and the
username (alias of the keystore to use).
Colm.
On Mon, Jul 1, 2013 at 12:08 PM, tulika <[email protected]> wrote:
> I am new to CXF. I am trying to bring up sts server and use it for a web
> service client and server interaction as explained in following
> example.However , on running the web service client , I am getting
> following
> error. Can someone please help me understand (why this kind of error comes
> )
> and resolve this problem:
>
> http://www.jroller.com/gmazza/entry/cxf_sts_tutorial
>
>
> Error:::::
> org.apache.cxf.phase.PhaseInterceptorChain doDefaultLogging
> WARNING: Interceptor for
> {
> http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService#{http://docs.oasis-open.org/ws-sx/ws-trust/200512/}Issue
> has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: No encryption crypto object found.
> at
>
> org.apache.cxf.ws.security.wss4j.policyhandlers.SymmetricBindingHandler.doSignBeforeEncrypt(SymmetricBindingHandler.java:395)
> at
>
> org.apache.cxf.ws.security.wss4j.policyhandlers.SymmetricBindingHandler.handleBinding(SymmetricBindingHandler.java:124)
> at
>
> org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:162)
> at
>
> org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:89)
> at
>
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:463)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:366)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:319)
> at
>
> org.apache.cxf.ws.security.trust.AbstractSTSClient.issue(AbstractSTSClient.java:751)
> at
>
> org.apache.cxf.ws.security.trust.STSClient.requestSecurityToken(STSClient.java:62)
> at
>
> org.apache.cxf.ws.security.trust.STSClient.requestSecurityToken(STSClient.java:56)
> at
>
> org.apache.cxf.ws.security.trust.STSClient.requestSecurityToken(STSClient.java:52)
> at
>
> org.apache.cxf.ws.security.policy.interceptors.IssuedTokenInterceptorProvider$IssuedTokenOutInterceptor.getTokenFromSTS(IssuedTokenInterceptorProvider.java:356)
> at
>
> org.apache.cxf.ws.security.policy.interceptors.IssuedTokenInterceptorProvider$IssuedTokenOutInterceptor.issueToken(IssuedTokenInterceptorProvider.java:465)
> at
>
> org.apache.cxf.ws.security.policy.interceptors.IssuedTokenInterceptorProvider$IssuedTokenOutInterceptor.handleMessage(IssuedTokenInterceptorProvider.java:149)
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Error-org-apache-cxf-interceptor-Fault-No-encryption-crypto-object-found-tp5730117.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
