|
Posted by Joe Kaplan on March 2, 2008, 9:07 pm
Please log in for more thread options
If you add the certificate to your trusted roots certificate store on your
client machine, that should allow your client to trust the certificate
without a warning (assuming the subject name matches the DNS name you use).
That also assumes that your source control client uses the Windows crypto
stack for doing SSL and not something else. If it uses something else, you
may need to configure some sort of cert container that is specific to that
implementation.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
> Quick question. Can I do the following?
>
> I have a single client (my laptop) that will be connecting to a server
> over a web service for source control. I use this a few hours per week and
> I really don't want to pay the $60 to get a athoritative certificate. If I
> generated a self signed certificate, is there any way that I can install
> that same certificate on the client of register the authority so that I
> don't get any warnings or issues about the authority of the certificate?
>
> I know I can simply bypass these warnings with a browser based page but I
> am affraid that my source control client will not be so willing to bypass
> this message.
>
>
> Thanks,
>
>
> -Andy
| 
XML Sitemap