469,291 Members | 1,719 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,291 developers. It's quick & easy.

Using Client Certificates

Can some body help me out?

I am trying to use client certificates in a Webservice. But some how i am not able to make it.
I went through the msdn resources but i think some one needs to help me out.
I am using IIS 5.1 on Windows XP professional.
I am able to setup the SSL on my webserver using the 14 day trial period certificate.
I setup the virtual directory using SSL connection required and Required Client certificates.
I want to know as my https webserver is now setup, then how do I get the client certificate. Is this certificate same as the certificate I received from verisign. I am not able to understand how do i generate the client certificate.

As per msdn site, using mmc console i imported the same certificate which i received from verisign to my trusted root certification auhtorities store. But when i tried to add this certificate to webservice's proxy, i received the error.

if i configure the virtual directory as "accept certificates" then the same setup work fine. But it does not work when i configure the virtual directory as "Required client certificates".When i am trying to use the webservice using internet explorer then i receive the certificate popup but fails to see the webservice even if i select yes to proceed.

Can some body tell me where am i going wrong? How do I proceed to achive this?

Thanks

dinoo
Nov 18 '05 #1
0 1380

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Matt Frame | last post: by
reply views Thread by Ankur Tyagi via .NET 247 | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by harlem98 | last post: by
reply views Thread by harlem98 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.