On Tue, 21 Dec 2004 08:31:01 -0800, "K. Mallory"
[quoted text, click to view] <KMallory@discussions.microsoft.com> wrote:
Actually, I did not so much need a lesson on using command line
parameters as I needed to know what parameters to use specifically to
generate a certificate that would work with a WSE 2.0 enabled Web
Service. Not sure what you were trying to say with the '-ss loser'
comment below, but I don't really think it was called for, and I found
it quite immature.
After doing some more research I used the following command to
generate a certificate that works for a Encrypted/signed Web Service
conversation:
makecert -r -pe -n "CN=ARRegSvc" -b 01/01/2000 -e 01/01/2036 -eku
1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp "Microsoft
RSA SChannel Cryptographic Provider" -sy 12
Thanks,
Kyle
[quoted text, click to view] >Sure, go to the command prompt and set the directory to whatever directory
>the makecert.exe excecutable is in. The type "makecert.exe" with the
>appropriate switches. make sure that you leave a space after each switch like
>"-ss loser" and type the resulting cert file at the end with a space between
>it and the value of the last switch. If you want the cert to be installed
>automatically to the "current user" / "other people" tree, omit the "-sr"
>switch. Since you want to use it to encrypt messages I recommend installing
>it to the LocalMachine root. S to do that, enter in the makecert.exe with "ss
>root" and "-sr LocalMachine" when the cert is finished, close the command
>window, double click on the cert file and press the install certificate
>button. it should install it to the LocalMachine/Root catagory, if not,
>manually select which store to use and put it in the LocalMachine/ "Root
>trusted certificates" catagory. There you go! That should do it.
>
>
>-Kristen
>
>
>"Kyle Swanton" wrote:
>
>> Hello all,
>>
>> I've been having quite a number of issues trying to generate my own
>> certificates. I'm using Makecert v5.131.3617.0 to generate the
>> certificate.
>>
