-
Re: Reverse Proxy Setup - IIS Windows Server 2012
wlipford Apr 27, 2016 2:40 PM (in response to wlipford)Bumping this hoping someone can point me in the right direction.
-
Re: Reverse Proxy Setup - IIS Windows Server 2012
jayd Apr 28, 2016 12:17 PM (in response to wlipford)I don't know what you're using (or want to use) as a reverse proxy, but I was just able to successfully access NPM through Nginx configured as a reverse proxy on a CentOS box.
Our NPM 11.0.1 is installed on Windows 2012 and I don't remember doing anything special or out of the ordinary to set the web console up. I did import our commercial wildcard SSL cert into IIS and then bound the Orion website to it for HTTPS access. I do know that if I simply try to access NPM by using https://orion.ourdomain.com, it will attempt to authenticate via NTLM (i.e. pop up a login prompt) which is not supported in Nginx. If I use https://orion.ourdomain.com/Orion/Login.aspx, it will use forms authentication by bringing up the Orion login screen and that is working just fine.
Jay
-
Re: Reverse Proxy Setup - IIS Windows Server 2012
wlipford May 18, 2016 3:01 PM (in response to jayd)1 of 1 people found this helpfulJay,
Did you have more then one Orion server you were reverse proxy too?
We have multiple Orion instances we point to. Now my issue I am facing is this.
Proxy 1: /OrionNA -> serverA.com
Proxy 2: /Orion -> serverB.com
I see all javascript/css & other assets are a relative path of /orion - well since both instances both have the same relative paths and I can not change the name of that directory the web server could send the request down path A or B and then the asp pages fail if it differs from the source server.
Hard to explain its just the fact that both instances have the exact same relative paths for assets.
-Will
-
-