Groups | Blog | Home
all groups > dotnet web services enhancements > february 2006 >

dotnet web services enhancements : WSE 3.0, MutualCertificate11Assertion and EstablishSecurityContext



Jacques Marcialis
2/17/2006 5:17:02 AM
Hi,

I make a simple "Hello World" Web service that works fine :)

I implement to the project (Client and Server) WSE 3.0
MutualCertificate11 capabilities and it works fine too. I test
with/without policy file and in mixed mode (file and code), with client
side and server side x509 certificates ... no problem.

Now I'm trying to implement a SecureContextToken to sign and encrypt
messages after client and server are authenticated (with x509
certificates). To do that, I set the EstablishSecurityContext value to
true on client and server (in policy file or in my code). The two sides
have the same value : true.

When I lauch the client I have an error message :"Security requirements
are not satisfied because the security header is not present in the
incoming message."

On the server side WSE traces, I find : "SecurityContextToken is
expected but not present in the security header of the incoming
message."

Could someone help me ?

Jacques
Jacques Marcialis
2/21/2006 12:58:46 AM
Hi Pablo,

Thanks for your response.

No, I don't find any SecurityContextToken in the output trace file on
the client side.

I made 2 tries, the first with EstablishSecurityContext=True and the
second with the false value. In two cases. In all case, logs are
quitely the same. Is there any other parameters to set to establish a
security context ?

thx
Jacques
Jacques Marcialis
2/23/2006 12:39:11 AM
Hi Pablo,

Unfortunetly, the problem is not solved.

On the file policy, the value is written 'establishSecurityContext' and
in code, it's written 'EstablishSecurityContext'. I tried all of the
combination of code and file policy on the client and server side, no
way :(

Regards,
Jacques
AddThis Social Bookmark Button