Makecert certificate generation headache
- From: tsa@xxxxxxxxxxxxxxx
- Date: Thu, 23 Aug 2007 00:49:24 -0700
Hi, all!
I'm currently working on a .NET development project in which I'm
trying to figure out how to utilize makecert.exe, in order to issue a
pair of X.509 certificates for testing out the authentication scheme
of the solution. So far, however, I've not succeeded in providing the
makecert utility with a proper set of parameters, as makecert seems
to
work in mysterious ways and responds with a "Too many parameters"
error message no matter how hard I try to come up with an acceptable
set of parameter values. In the following I've provided an example of
my latest command line struggle to get makecert generate the
certificates I need:
In order to generate self-signed root certificate:
makecert -sv c:\SignRoot.pvk -cy authority -r c:\signroot.cer -a sha1
-
n "CN=Another Test Certification Authority"
This command just fine. However, when I try to generate a server
certificate for my IIS, utilizing makecert and the "root" certicate
generated by the listed above works in the following way,
makecert -iv c:\SignRoot.pvk -ic c:\signroot.cer -cy end -pe -n
"CN=Another Test Server Cert" -eku 1.3.6.1.5.5.7.3.1 -a sha1 -ss My -
sr currentuser -sky exchange
I run into yet another extremely annoying "Too many parameters" error
message. Are some of the options I'm using mutually exclusive or
what?
Any help on this issue would be highly appreciated.
Regards, Trond
.
- Follow-Ups:
- Re: Makecert certificate generation headache
- From: Valery Pryamikov
- Re: Makecert certificate generation headache
- Prev by Date: Re: Manually computing sha1 digest of reference containing base64 encoded string and comparing it to digest value of same reference generated by SignedXML.ComputeSignature - Does not match
- Next by Date: Re: Makecert certificate generation headache
- Previous by thread: SAML 2.0
- Next by thread: Re: Makecert certificate generation headache
- Index(es):
Relevant Pages
|
|