"Pablo Cibraro [MVP]" wrote:

> Hi Sid,
>
> Microsoft provides another tool to grant permissions on certificates, the
> name of this tool is winhttpcertcfg.
> The following sample, grant permission on the certificate created above to
> the ASPNET account:
> winhttpcertcfg -g -c LOCAL_MACHINE\My -s MyServerCert -a ASPNET
>
> You can find this tool in the same folder as the WSE quickstarts.
> (C:\Program Files\Microsoft WSE\v3.0\Samples)
>
> Regards,
> Pablo Cibraro
> http://weblogs.asp.net/cibrax
>
> "Sid DeLuca" <SidDeLuca@discussions.microsoft.com> wrote in message
> news:A9A7A762-C832-43D4-98D4-AE0B8F715868@microsoft.com...
> >I have my web service application running well using the
> > UsernameForCertificate assertion. As part of getting the service and test
> > client application set up on a development Win2003 Server box I have
> > access
> > to, I had to use the WSE3 certificates tool to grant permissions to the
> > server certificate for the Network Service account.
> >
> > Now I have to move the web server to our outward facing staging server,
> > which I don't have access to. I would like to instruct the server admins
> > on
> > how to set the appropriate permissions on the server certificate
> > installed,
> > but I'm guessing they *don't* want to have to install WSE3 and use the
> > certificate tool to do so. Can anyone tell me how I might go about
> > associating a particular certifiate with a physical path on the server so
> > one
> > can set permissions? Again, I don't want to have to require them to
> > install
> > the WSE3 tools.
> >
> > Sid
>
>