Using SSL for web publishing

  • Thread starter Thread starter chippyp
  • Start date Start date
C

chippyp

So I'd like to have it set up where I could use SSL to connect to the server rather than using the direct gateway. When I start my web publishing I set it up for SSL on port 441, not 443. On the IIS side, i set the TCP to use 441. From the client side I browse to http://[servername]:441 and it brings up my list of available applications. When I try to use an application, it tries to connect to the server and fails, but as soon as I change the settings to direct gateway on port 80, it connects just fine. So what would the best route for this be?
 
Hi Chippyp

From the web console, you can set the client's default connect mode per server in the advanced setting to:
1) Auto (If user connects using https, SSL is used else Regular is used)
2) Regular
3) Direct
4) SSL

By default, the 2X client will use the same settings the web service is using to connect. Now if the clients need to use different settings to connect to the server, one can override the default settings from the Advanced Setting.

Nixu
 
You must log in or register to reply here.
Back
Top