Post reply

Does SSL activation in Reporting Services 2005 exclude the use of http in favor of https

  • October 7, 2010 at 6:58 am

    #224825

    Hello SSRS Community,

    I have been asked by a web developer in my company to check if in SQL Server 2005 reporting services the activation SSL makes it possible to access the Report Server with both HTTP and HTTPS.

    For example:

    1. Without SSL activation you can use http://ServerName/ReportServer to access your report server

    2. Once SSL is activated, we are wondering if it will be possible to access the Report Server with the following two links:

    a. https//ServerName:443/ReportServer

    Thank you,

    Lu

  • October 29, 2010 at 6:29 am

    #1244099

    From what I found here, I would say all links will be https after activation of ssl.

    In a wrox book I found however that after ssl-activation all http requests will automatically be redirected to https.

    So, all traffic will be using ssl, but you should still be able to use http links for pointing to a report.

    Peter Rijs
    BI Consultant, The Netherlands

  • October 29, 2010 at 7:09 am

    #1244145

    Thank you Peter for your input,

    In fact i have run a test which consists of calling a report with "http://..." to verify that there will be a redirection to "https://..." but it seems not to work, instead of redirecting it returns the following message: "The operation you are attempting requires a secure connection (HTTPS). (rsSecureConnectionRequired)".

    Your posts are welcomed.

    😀

  • October 29, 2010 at 8:48 am

    #1244246

    Can it be that the redirection only works when you make calls to reportmanager (http://server/reports), not when calling directly to the reportserver (http://server/reportserver?

    Have you tested that?

    From what I saw in BOL you should change all links in the reportmanager configs that refer the reportserver to https, so I think there is no auto-redirecting for reportserver.

    If thats the case, maybe a webdeveloper knows a way to go around that. But unless you can find some way of redirecting the call, the workaround may compromise security if there will be no ssl "tunnel" between client and server.

    Peter Rijs
    BI Consultant, The Netherlands

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply