WCF asymmetric binding and establishsecuritycontext

Question

0.00/5 (No votes)

See more:

In one of my service I am using wsHttpBinding.

I am using certificate(on both side, server as well as client) as clientCredentialType.so, this is a type of asymmetric binding.

I have also kept establishsecuritycontext = "True"

Now as per what I have read about establishsecuritycontext, when we keep this as "True" then a security context token (SCT) is generated through an initial exchange between caller and service and this token is used to authorize and secure subsequent message exchanges.

My question is if SCT will be used to secure message then what is the role of private and public key of certificate.

As per what i understand both keys will be used to encrypt and sign the message then do we really require establishsecuritycontext = "True"

Posted 3-Aug-15 19:10pm

mukul trivedi

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

dnxit · Answer 1 · 2019-07-30T23:04:00

If the token is set to false then, key exchange and validation will be done per call as opposed to being done once and cached for the session and only a SCT passed around in the messages instead.

SCTs are based on a symmetric key which makes them much more efficient for signing/encrypting the message. The use of a SCT is very good when the client is expected to make many calls in succession because it alleviates the need to do the exchange and validation of a one off key every time.

But it should be kept in mind it gives the benefit only if Channel is not being closed and created on each call also it has some issues with SSL and load balancer in place