You do need a server certificate. This is different than Certificate
Server ...
Dan
--------------------
>Thread-Topic: ASP.NET SSL problem
>thread-index: AcTW5m1y0C2kHOF3TNyWjUZfN2+oLQ==
>X-WBNR-Posting-Host: 62.101.92.181
>From: "=?Utf-8?B?amFjaw==?=" <>
>References: <#>
<>
>Subject: RE: ASP.NET SSL problem
>Date: Tue, 30 Nov 2004 06:11:04 -0800
>Lines: 61
>Message-ID: <E3E4270A-F029-42EE-A86D->
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.dotnet.framework.aspnet.webservic es
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGXA0
3.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservic es:26890
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservic es
>
>hi Dan,
>
>so i have to install Server Certificate also on my server?
>
>thx
>
>"Dan Rogers" wrote:
>
>> Hi Mario,
>>
>> When embedding web service calls in server side applications, you will
have
>> to manually allocate a certificate to the connection. When you use a
>> client side application (win32 code running in an interactive window)
you
>> get automatic certificate negotiation. You will need to obtain a valid
>> level 3 cert for your server to allow it to make calls to secured
services,
>> and make sure that the called application recognizes the certificate
(party
>> and root authority) for this to work.
>>
>> There are good examples of this type of coding in the WSE 2.0 SP1
toolkit
>> that you can download from MSDN.
>>
>> I hope this helps
>>
>> Dan Rogers
>> Microsoft Corporation
>> --------------------
>> >From: "jack" <>
>> >Subject: ASP.NET SSL problem
>> >Date: Mon, 29 Nov 2004 21:25:11 +0100
>> >Lines: 14
>> >X-Priority: 3
>> >X-MSMail-Priority: Normal
>> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
>> >Message-ID: <#>
>> >Newsgroups: microsoft.public.dotnet.framework.aspnet.webservic es
>> >NNTP-Posting-Host: 170.252.72.1
>> >Path:
>>
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftn gxa06.phx.gbl!TK2MSFTNGP08
>> .phx.gbl!TK2MSFTNGP15.phx.gbl
>> >Xref: cpmsftngxa10.phx.gbl
>> microsoft.public.dotnet.framework.aspnet.webservic es:26860
>> >X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservic es
>> >
>> >hi,
>> >
>> >i've got an ASP.NET application which call a web service over ssl
channel
>> >sending client cetificate and i got the following error:
>> >"The underlying connection was closed: Could not establish secure
channel
>> >for SSL/TLS"
>> >
>> >If i use the same code in a windows application it works fine.
>> >
>> >Do you have any idea?
>> >
>> >thx
>> >
>> >
>> >
>>
>>
>
|
Similar Threads
