WSE 2.0 with X509 Certs



Can someone explain or point me in the direction of some documentation for
manually configuring X509 Token elements in the policy file of a WSE2.0 app?
I am having to down convert from WSE3 using mutualcertsecurity11 to WSE2 for
business reasons. Particularly I am looking at the <wssp:SecurityToken>
element and it's child elements. In WSE3 I had all kinds of options of how
I wanted to retrieve an X509 Cert and from which Store to retrieve it. In
WSE2, I can't seem to find any documentation on using something like a
Certificate Serial Number to go after a Cert in the My CertStore. It looks
like the <wssp:SubjectName> element matches on Certificate Attributes, but
is there another element possibly to go after other attributes in a
Certificate?

If this is not possible, how do I get the value in the <wssp:X509Extension>
element in code once I have the Certificate? As I recall, this was some
sort of hash of the Cert. My requirements force me to set the client policy
in code at runtime so I'm guessing I will need to be able to generate this
value..... Actually after more thought I propably won't need to generate is
as I am finding the Cert in the CertStore and adding it to the policy I am
creating. From what I have read on WSE2, this should solve my problem, but
if anyone could confirm it would be appriciated.

TIA


.



Relevant Pages

  • Re: The message must contain a wsa:To header
    ... My client app is not generating a trace file. ... the client is not applying the WSE policy at all because of an ... at ApplicationMessagingWS.Dispatch(String messageType, String ... look for a certificate with this subject name in the certificate store ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: security header is not present in the incoming message
    ... Similar problem appears when I run my client directly under IIS instead of under ASP.NET Development Server. ... There are no certificates in the certificate store that match the find value of 'CN=WSE2QuickStartServer'. ... 'Hello World with certificate policy. ...
    (microsoft.public.dotnet.security)
  • The message must contain a wsa:To header
    ... When I setup the policy, ... at ApplicationMessagingWS.Dispatch(String messageType, String ... be used along with the Integrity assertion when the presence of the signed ... look for a certificate with this subject name in the certificate store ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • RE: Encryption and signing using Security context tokens using WS
    ... In a webfarm scenario wen i try to run the sample using policy the error is ... Tokens in a Web Farm.The built-in SecurityContextService keeps track of the ... //This is the point where to get the SCT service. ... system can look for a certificate with this subject name in the certificate ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: The message must contain a wsa:To header
    ... When I setup the policy, ... at ApplicationMessagingWS.Dispatch(String messageType, String ... be used along with the Integrity assertion when the presence of the signed ... look for a certificate with this subject name in the certificate store ...
    (microsoft.public.dotnet.framework.webservices.enhancements)

Loading