Knowledge Base

Configure bindings

The URL of the proxy server must be added as a second binding to the deployed website. With PcVue 12 you must configure the bindings directly in the IIS Manager:

With PcVue 15 the second binding can be added via the WDC:

The second binding is mandatory since WebVue does not support the Forwarded HTTP Extension and «SSL Offloading».

Add redirect URL for the clients

Since OAuth is checking the redirect URL of WebVue and WebScheduler it would return an “invalid redirect URL” error in case of accessing via a reverse proxy.

To avoid that it is mandatory to add the proxy URL also to the list of known URLs. You can do this directly via the WDC. URLs must be separated via “;” (semicolon). E.g.: https://webvue.pcvue.de/WebClient/Authentication/AuthorizationCodeCallback;https://proxy.pcvue.de/WebClient/Authentication/AuthorizationCodeCallback

This only applies to PcVue 12. With PcVue 15 redirect URLs for all added bindings are generated automatically by the WDC.

Configure WebClient

There are two settings of WebClient which must be enabled:

The option “UseClientHostForRedirects” tells WebVue to use the value from the HOST header to generate redirect URLs. If it is disabled, the URLs will be generated with the entries from the Registry.

The second option, “RelativeAcessToGraphicalData” forces WebVue to load GraphicalData via a relative URL, i.e.: /GraphicalData instead of https://webvue.pcvue.de/GraphicalData.

For PcVue 12 both settings must be changed directly in the web.config file.

In PcVue 15 “UseClientHostForRedirects” option can be changed in the WDC: