STS Behavior Change In CXF 3+?

I've recently done some work migrating my STS implementation from using CXF 2.7.14 up to 3.1.4. In testing the upleveled STS, I noticed that a change crept in somewhere along the way when requesting a bearer token - in CXF 3, the returned token has an additional AttributeStatement:

Re: Using RSA with SHA256 algorithm for WS-Security policy

Thank you Colm. Thanks, Giriraj On Mar 8, 2016 7:13 AM, "Colm O hEigeartaigh" wrote: > Yes, there is a special JAX-WS configuration property to change the > asymmetric signature algorithm - > "ws-security.asymmetric.signature.algorithm". See here: > > http://cxf.apache.org/docs/ws-securitypolicy

Null Pointer Exception at WSDLServiceFactory init method

I am getting below exception while invoking the client service generated by CXF. Below is the piece of code where I am getting exception public Object createStub() { QueryCustomerOutService queryCustomerIdentification = new QueryCustomerOutService(); //Getting exception at this line