One way is to have your web service provider/SIB implement the JAX-WS Provider interface--that would give you access to the entire SOAP message in XML format, from which you can use SAAJ or DOM or whatever to get to the username--that should work.
Another option might be a JAX-WS handler that does the ugly username-extracting work as above and passes the name as a property in the web service's MessageContext to your service implementation bean. There may be more elegant solutions, however. Glen Markus.Ruettimann wrote: > > Hi all, > I have a question regarding (soap) client identification. I have a CXF > soap server running (tomcat in an equinox osgi container, using Spring-DM) > > and I am able to communicate with it. I understand the user / password > authentification using WS-Security. > > My SOAP service must work on client specific data model and I like to use > the ws-security autentification of the soap client to select the correct > model. > Unfortenately I'm not able to find the way to do that, even it seems a > common use case... > Is there someone who can tell me, or point to some location, what I need > to do that my soap server implementation knows the client identity? > > That would be just great. > Thanks, and happy new year to all of you. > > Regards Markus > -- View this message in context: http://www.nabble.com/Client-identity-on-SOAP-services-tp21287791p21291409.html Sent from the cxf-user mailing list archive at Nabble.com.
