I have fixed the NPE in CXF, although the cause of the problem is that your
STSClient is missing some configuration. What does your STSClient
configuration look like? For the PublicKey KeyType, it should look
something like:
<bean id="stsClient" class="org.apache.cxf.ws.security.trust.STSClient">
<constructor-arg ref="cxf"/>
<property name="wsdlLocation" value="
https://localhost:8443/SecurityTokenService/Transport?wsdl"/>
<property name="serviceName" value="{
http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService"/>
<property name="endpointName" value="{
http://docs.oasis-open.org/ws-sx/ws-trust/200512/}Transport_Port"/>
<property name="properties">
<map>
<entry key="ws-security.username" value="alice"/>
<entry key="ws-security.callback-handler"
value="org.apache.cxf.systest.sts.common.CommonCallbackHandler"/>
<entry key="ws-security.sts.token.username"
value="myclientkey"/>
<entry key="ws-security.sts.token.properties"
value="clientKeystore.properties"/>
<entry key="ws-security.sts.token.usecert" value="true"/>
</map>
</property>
</bean>
Is your configuration missing the "ws-security.sts.token.properties" value?
Colm.
On Tue, Sep 23, 2014 at 2:27 PM, niranjana.murthy <
[email protected]> wrote:
> I am using <cxf.version>3.0.0</cxf.version>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/IssuedToken-nullpointer-exception-tp5749119p5749120.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
