2

I'm using the SharePoint web proxy in an SharePoint App to call an external service (which I control). I set the service up to use SSL and it seems SharePoint has a problem with my certificate (or something) since it fails with the above error when calling the service with https. If I use http instead of https the call works fine. The app.manifest is correct. If I call the same service from the browser using https it works fine.

Also if I put the service on free Azure web sites which provides SSL automatically and have the SP WebProxy call that it also works OK. So SP must be happy with the Azure SSL certificate

It seems that it is something specific to my SSL certificate that SharePoint doesn't like.

Since it is Office 365 I don't control the server so I can't install certificates.

Improve this question
1
  • I don't want to answer my own question so I will just comment and say that I just tried this again this morning and the call worked with https via the SP Web Proxy. I don't know why it is working now. Maybe the certificate hadn't propagated everywhere? This is really something I do not know much about I am still a little concerned with on-prem where the servers are behind firewalls. Do certificates needs to be installed there in order for the https calls to work?
    – Jim Barrett
    Aug 11, 2015 at 12:13

2 Answers 2

Reset to default
1

Who issued the certificate you are using on the external service?

It sounds like it was issued by someone trusted by your browser, but not by Microsoft. I don't know if they publish a list of what certificate authorities they trust (I searched and couldn't find one), but I guess a good starting point would be the IE default list.

Improve this answer
1
  • Thanks. I used the links from the Microsoft support and TechNet site below since I host the web site on Azure. GoDaddy supplied the certificate and they are on the list of CA's in Microsoft's certificate program. The "caller" of the web site is not the actual browser, it is an instance of SharePoint online (in Office 365) calling it from the server. MS Support, Technet
    – Jim Barrett
    Jul 26, 2015 at 16:17
0

What version of SharePoint is the tenant you are having trouble with? You can find this in the response headers on any request (e.g. MicrosoftSharePointTeamServices: 16.0.0.4121)

Improve this answer
1
  • For Office 365 SharePoint the header is 16.0.0.4121, as in your reply. When the App is used on-prem I guess it could be anything. BTW I just tried this again this morning and the call worked with https! I don't know why. Maybe the certificate hadn't propagated everywhere? I am still a little concerned with on-prem where the servers are behind firewalls. Thanks for the reply.
    – Jim Barrett
    Aug 11, 2015 at 11:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.