Re: XEnroll and local machine's cert store

From: Sébastien PICAMELOT (PICAMELOT_at_discussions.microsoft.com)
Date: 11/18/04 

Date: Thu, 18 Nov 2004 03:28:02 -0800

I am trying to enroll a certificate this way (at the difference code is
within a web service - never mind about security for the moment -). the
CAStoreFlags are set to CERT_SYSTEM_STORE_LOCAL_MACHINE and all is OK.

But...

after acceptResponse() execution, certificate is already in issued
certificate, and not in one of the stores.

this method returns only void, so I don't understand what is missing. Any
idea ?

Relevant Pages

  • RE: Recommendations for securing a local webservice.
    ... You seem to be trying to secure a web service interface to only those ... protocol that was intended to be caller agnostic to implement a caller ... Install a special certificate as part of the ... Combine #2 with token based security. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Public key certificate disappears automatically !!!
    ... My web service is a token issuer and issues Security ... server certificate and imported it into the Local Computer -> Personal store ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Security problem with orchestration exposed as web service
    ... Then I wrote a client example to access my web service and I received ... In my receive port in Biztalk Administration console, I set Security ... Transport mode and Certificate. ... I configured the web service to use the certificate. ...
    (microsoft.public.biztalk.general)
  • Re: Ping Roedy Green, advantages/limitations of real certificates
    ... They don't have to lower the price since other vendors can't compete, ... What other vendors could do is offer you a cheap 5-year certificate, ... Roedy Green Canadian Mind Products ...
    (comp.lang.java.programmer)
  • Re: How do I store secrets?
    ... Danny van Kasteel wrote: ... > mind that I need to verify that the CODE used to sign the message was ... That means the certificate would have to reside INSIDE the ...
    (microsoft.public.dotnet.security)