I think you're mixing up transport-layer with message-layer security--what's in the soap header or soap body wouldn't matter for https:// because it's all encrypted anyway. You'll probably just need simple basic authentication for https (Step #7 of http://www.jroller.com/gmazza/entry/setting_up_ssl_and_basic).
As for soapUI, I believe there's a Preferences menu where you place in the basic auth username and password for https:// for it to work, but am less certain here. HTH, Glen De Bakker, Bjorn wrote: > > I'm currently developing a client, which has to communicate with a > webservice. This webservice is accessible through https, so we have to > provide authentication. > -- View this message in context: http://old.nabble.com/Authorization-for-web-service-tp28241860p28242794.html Sent from the cxf-user mailing list archive at Nabble.com.
