Can you double check the version of wss4j you are picking up?
There isn't any related code at lines: > (UsernameTokenProcessor.java:84) > (UsernameTokenProcessor.java:54) in the version that goes with 2.2.3. Thus, I'm thinking that some version is mismatched someplace. Dan On Fri October 9 2009 6:59:02 pm Gabriel Guardincerri wrote: > Hi, > > We've gotten this error after migrating to CXF 2.2.3 (server side): > > Caused by: org.apache.ws.security.WSSecurityException: General security > error (WSSecurityEngine: No password callback supplied) > at > org.apache.ws.security.processor.UsernameTokenProcessor.handleUsernameToken > (UsernameTokenProcessor.java:84) at > org.apache.ws.security.processor.UsernameTokenProcessor.handleToken(Usernam > eTokenProcessor.java:54) at > org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEng > ine.java:326) at > org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEng > ine.java:243) at > org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInIn > terceptor.java:198) > > On the server side we have: > > <bean id="wss4jInInterceptor" > class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor"> > <constructor-arg> > <map> > <entry key="passwordCallbackClass" > value="com.XXX.XXX.XXXX" /> > <entry key="action" value="UsernameToken Timestamp > NoSecurity" /> > </map> > </constructor-arg> > </bean> > > On the client side we are using Axis and we use this to configure it: > > Stub axisPort = (Stub) locator.getUserServicePort(); > axisPort._setProperty(WSHandlerConstants.ACTION, > WSHandlerConstants.USERNAME_TOKEN); > axisPort._setProperty(UsernameToken.PASSWORD_TYPE, > WSConstants.PW_TEXT); > axisPort._setProperty(WSHandlerConstants.USER, user); > axisPort._setProperty(WSHandlerConstants.PW_CALLBACK_REF, new > PasswordCallback(password)); > > Any idea of what could have changed? That worked with CXF 2.0.7 > > Thank you, > > Gabriel > -- Daniel Kulp [email protected] http://www.dankulp.com/blog
