Design without SSL, publish with SSL

Riddle me this...
Can I design my reports onto a development server that does not have SSL in
the mix and then use the rs utility to publish them to a live server that has
SSL?
Well I did but I had to change \Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config
file with the attribute SecureConnectionLevel from 2 to 0 in order to do this.
Otherwise I received an error in the cmd window:
"The operation you are attempting requires a secure connection. (HTTPS)."
So, I can see the reports if I leave the SecureConnectionLevel setting at 0
but not when it is set to 2 (which I want to utilize SSL).Hmm.. setting SecureConnectionLevel to 0 stops rs from requireing SSL
connection at all. You don't want to do this :-).
Regariding rs.exe - you can simply specify in on your command https:// for
the path to report server. The tool should the estabilish an SSL
connection.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Greg Allan" <GregAllan@.discussions.microsoft.com> wrote in message
news:519624D0-C307-45EF-867A-D2F1DA8ADA78@.microsoft.com...
> Riddle me this...
> Can I design my reports onto a development server that does not have SSL
> in
> the mix and then use the rs utility to publish them to a live server that
> has
> SSL?
> Well I did but I had to change \Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config
> file with the attribute SecureConnectionLevel from 2 to 0 in order to do
> this.
> Otherwise I received an error in the cmd window:
> "The operation you are attempting requires a secure connection. (HTTPS)."
> So, I can see the reports if I leave the SecureConnectionLevel setting at
> 0
> but not when it is set to 2 (which I want to utilize SSL).