Windows Server 2003 and 2008 each enable SSL a bit differently. The following page from the SolarWinds Orion Common Components Administrator Guide provides links to procedures for each respective OS:
Yes, we use an additional web server (though this isn't a requirement to do this) and we force https.
Here is how I have it configured...
We are using Windows 2008 R2 and IIS 6. I created an additional site called SolarWinds Redirect and added binding on it for http/port80. I then put only an https/port 443 binding on my main NPM site. On the SolarWinds Redirect site it is set to redirect everything to the https site.
This was by far the easiest way I found to do this. I attempted other methods but I had problems with them.
Hope this helps!
If you want to require SSL, you can follow the below steps (after you enable SSL).
When the flags are enabled, only SSL access is possible (since Orion will only accept https cookies). By default, the web.config file is store in the root website folder of Orion (ie: c:\inetpub\SolarWinds\web.config).
To enable secure flag, edit web.config file:
find <system.web> and append after it:
<httpCookies requireSSL="true" />
find <forms loginUrl="~/Orion/Login.aspx"/> and change to:
<forms loginUrl="~/Orion/Login.aspx" requireSSL="true" />
Then save the file, no restart of anything needed.
To enable HTTPOnly flag, add attribute to <httpCookies> tag:
<httpCookies httpOnlyCookies="true" requireSSL="true" />
I did not see an end procedure after enabling 'Force HTTPS'. I assume we will need to restart the App Pool (or site) and then do we need to re-run config wizard? Or do we just run config wizard the first time, after we enable SSL certs on the site?
So is it:
(assuming Win2008R2 IIS 7):
1. Enable SSL (install cert first, of course) in IIS7.
2. Run Config wizard to point to HTTPS.
3. Edit web.config file to force https.
4. Re-start app pool (or site) in IIS?
Thanks in Advance,
This is something I want to accomplish as well. Are there detailed steps for doing this out there?