Skip to main content
Solved

Configure IFS Applications 10 to use port 443 instead of standard 48080

  • Mar 30, 2021 2:22 PM UTC
  • 5 replies
  • 1423 views

Srikanth
Superhero (Partner)
Forum|alt.badge.img+18

Has anyone successfully implemented IFS Applications 10 to use the default SSL port 443 instead of the standard port numbers?

One of my client wants to implement this configuration for couple of reasons:

  1. Suppress the port number inside the IFS URL
  2. Most firewalls are tolerant to 443 compared to other ports

Please advise, thanks!

Best answer by dsj

Hi @Srikanth,

 

Given below is example configuration.

Loadbalancer is of type TCP with listener port 443

 

Regards,

Damith

View original
This topic has been closed for replies.

5 replies

dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)
  • Mar 30, 2021 3:32 PM UTC

Hi @Srikanth,

 

It worked straight for us.

In our installations we use SSL passthrough where external load balancer setup to pass through traffic to IFS and the SSL certificate is managed in IFS. But I hope other options also work as they should.

 

Regards,

Damith


Srikanth
Superhero (Partner)
Forum|alt.badge.img+18
  • Author
  • Superhero (Partner)
  • Mar 30, 2021 4:23 PM UTC

Hi @dsj ,

Can you please provide more details or a screenshot of your configuration?

We are using SSL Passthrough right now and it works fine as long as the port number 48080 is part of the SSL proxy URL.

Example - https://ifs.mydomain.com:48080

However the goal is to utilize the standard SSL Port - 443.

Example - https://ifs.mydomain.com


dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)
  • Answer
  • Mar 31, 2021 9:59 AM UTC

Hi @Srikanth,

 

Given below is example configuration.

Loadbalancer is of type TCP with listener port 443

 

Regards,

Damith


Srikanth
Superhero (Partner)
Forum|alt.badge.img+18
  • Author
  • Superhero (Partner)
  • Mar 31, 2021 10:21 PM UTC

I did not specify the port number 443 in the Proxy URL assuming https would resolve to the default port number. Adding the port number at the end made the configuration to work and another colleague of mine confirmed this as well. 

Thank you!


Chandana Gunasekara
Hero (Employee)
Forum|alt.badge.img+10

Yes, I have used 443 default SSL port and reconfigured MWS.  that way you can use the url without 48080 as well.

e.g https://<mws_host_name>.com