Here’s the deal.
We were running Orchestrator 2019.10 successfully in our current configuration. We have a machine, let’s call it OrchMachine as the web server serving up the orchestrator application. This machine is redirected to via a VIP from a different URL, let’s call it https://orchURL.mydomain.com.
After upgrading to 2020.4.3 and with a signing certificate in place, if we navigate to https://orchURL.mydomain.com we get a couple of different behaviors.
- Some users get a connection timeout at https://OrchMachine/identity/connect/authorize
- Other users (different network connection) actually get the login screen at https://orchmachine/identity/. If they click to login with Windows, they get the same screen again and have to click to log in a second time at which point they get to the main page at https://orchmachine
Anyone run into this trouble with this kind of configuration and upgrading to 2020.4.3?
I do have a ticket open with support as this is an enterprise license but I thought I’d try and mine the crowd and see if someone has any other ideas.