is there a way to get the details of certificate (cert subject) when service rejects authentication for expired certificate or not trusted.
both the OperationContext and ServiceSecurityContext both are null.
View Complete Post
We recently installed SQL Reporting Services SP2. When we run Report Manager (i.e
http://myserver/reports) and attempt to print a report using the Print control we get UAC prompts for both Vista and Windows 7. If we click "Show Information About this Publishers
Certificate" under UAC prompt it indicates the certificate expired on Feb 22, 2009. Were the correct CAB files for installing the print control included in SP2?
i am using self created certs for client authentication. for one of the cert it works fine but ith another cert it does work. i get an error, can't rer connect to server.
is there any way/tool to troubleshoot cert issue?
I'm trying to receive a Client Certificate in a Web Service and having some problems.
Dim cert As X509Certificate = X509Certificate.CreateFromCertFile("C:\cert.cer")
Dim hw As String = _ws.HelloWorld
The certificate seems to be correclty loading and added to the client.
The client connects to the server with HTTPS.
Public Function HelloWorld() As String
Dim cert As HttpClientCertificate = Me.Context.Request.ClientCertificate
Return "Hello World"
cert.IsPresent is false and all certificate fields are empty.
IIS is configured to Accept Client Certificates.
Reproduced in two environments:
- Windows 7 x64, IIS 7, VS 2008, .NET 3.5
- XP x86, IIS 5, VS 2008, .NET 3.5
Always in the Web Service the Client Certificate is not proesent. I haven't been able to find any other configuration I should do. Can anyone help?
How can i know at client side that my request to wcf service(with certificate authentication over nettcp) has failed because of authentication or authorization.
i think authentication can fail if the certificate is not a valid certificate(ie date has expired). For authorization i have implemented ServcieAuthorizationmanger and returning true/false. how wcf will transfer this to authrization error.
We are having issues with our certificates assigned to the WCF-client proxy. If we issue a call to a WCF-service via basicHttpBinding with transport security using certificates we get an error stating "Could not establish secure channel for SSL/TLS with
authority X". If we open internet explorer and navigate to the WCF-service and select the certificate, it works nicely and after that our WCF-client proxy works as well.
I'm creating a Web application to consume a third party Web service. The third party has provided me a Security Certificate and I can use it to see their WSDL in Browser successfully.
I've created a Unit Test to consume the web service with the client certificate and it works fine.
I've also create a Console application to consume the web service, and again it works fine.
The problem is, I created a Web application (ASP .NET in IIS) to consume the web service, and it fails. The party said I didn't send the Client Certificate in the Web Service call. But the code I use is the same as the one running in the Unit Test and Console application.
Background: The Web Application has impersonate="true" and we are using Integrated Windows Authentication. Also we have a Web Proxy in our company to go out to internet.
Below is the code I'm using. I believe the code is fine as it works in some cases except in ASP .NET (IIS).
this.BuySideService = new FXBuySideServiceV1();
// preserve cookies for auth info (SMSESSION)this.BuySideService.CookieContainer = new System.Net.CookieContainer();
// basic authenticationthis.BuySideService.Credentials = new System.
we have upgraded our WSS 3.2 installation to Sharepoint Foundation 2010 and have trouble with authentication over client certificates (works perfect with WSS 3.2).
You can reproduce this with a fresh install of SharePoint Foundation 2010 on Windows Server 2008 R2. Create an application and set in IIS authentication to Client Certificates. Then create a site with one document library and upload at least two documents.
Message: Object expected
I found following HTTP 500 error in IIS-Log:
2010-05-21 13:20:01 192.168.1.86 POST /_vti_bin/client.svc/ProcessQuery - 443 XXXX\XXX 192.168.XXX.XXX Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+InfoPath.2;+.NET4.0C;+.NET4.0E)
500 0 0 188
If i switch authentication in IIS to Windows Authentication i get no error (HTTP Status Code = 200).
Full error Message:
Accessing this site requires a client certificate. Specify a client certificate in the crawl rules.
I added the Crawl Rule and Content Source for the test site
https://sp.xxxx.com/TestSite and tried specifying each available client certificates
in the rules one by one, but the crawl still fails.
What kind of certificate does it needs and how to enable it? I know that the *.xxxx.com certificate is used for our SSL.