By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,022 Members | 856 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,022 IT Pros & Developers. It's quick & easy.

WS-Security Question

P: n/a
Hi.
My goal is to achive security similiar to the HTTPS.
The data visible for the port sniffer must be ciphered.
Is this possible with WS-Security or WS-Security only enables mi to secure
authorization and other stuff.
i will appreciate any answers.
regards

PK

Apr 20 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi.
My goal is to achive security similiar to the HTTPS.
The data visible for the port sniffer must be ciphered.
Is this possible with WS-Security or WS-Security only enables mi to
secure
authorization and other stuff.
i will appreciate any answers.
AFAIK, WS-Security only treats encryption and signing of message content
(soap body). Some parts of the soap header will be in plain text - this allows
messages to be routed, stored, resent etc by untrusted intermediaries such
as proxies, or to be converted between transport protocols (e.g. from http
to msmq).
To get full encryption, you must also use a transport level mechanism such
as https.

Of course, the challenge with https is that it requires a direct realtime
connection between provider and consumer.
regards
PK

Apr 20 '07 #2

P: n/a
Fortunately ( or not ) destination ans source addresses can be in plain text
in my case.
I only want data beeing transferred ( such as 32kb file buffer ) to be
encrypted. I want to guarantee that noone
will see content of the files iam exchanging.
What's your opinion?

AFAIK, WS-Security only treats encryption and signing of message content
(soap body). Some parts of the soap header will be in plain text - this
allows messages to be routed, stored, resent etc by untrusted
intermediaries such as proxies, or to be converted between transport
protocols (e.g. from http to msmq). To get full encryption, you must also
use a transport level mechanism such as https.
Of course, the challenge with https is that it requires a direct realtime
connection between provider and consumer.
>regards
PK

Apr 20 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.