topic Re: Corporate network - problem with port 4244 in Management & Governance

Corporate network - problem with port 4244

Mon, 04 Jul 2016 10:41:37 GMT

Hi,

We are starting to use QlikSense for our customers and did a successful install however we immediately hit a wall: port 4244 being used for windows authentication. On a corporate network they are hesitant (or unwilling) to open this port for outbound communications.

How can we work our way around this? When I look around on the web I can find info about non-windows authentication but this is not the way we want to go (using LDAP). I also find info on reverse proxy's but it is not clear to me whether this would solve the issue.

Thanks for any help!

Edwin

Re: Corporate network - problem with port 4244

kuczynska — Tue, 08 Aug 2017 09:44:11 GMT

Hi Edwin,

We are hitting a very similar issue - don't think we will get the port open too for corporate security reasons. Could you advise how did you progress on your end? We also have to follow non-Windows authentication here. Any advice would be appreciated.

Thanks in advance,

Michalina

Re: Corporate network - problem with port 4244

Vincenzo_Esposito — Wed, 09 Aug 2017 18:40:50 GMT

You can use the custom authentication and write your authentication module to authenticate against the AD or LDAP.

Re: Corporate network - problem with port 4244

kuczynska — Thu, 10 Aug 2017 08:06:13 GMT

Hi,

thanks for your reply but this is not the case here as all of our users are external. QMC doesn't allow setting both https ports to 443 (shows the message 'All ports in this property group must be unique on the same proxy'). We will probably end up setting up a reversed proxy on Apache etc.

Re: Corporate network - problem with port 4244

barry_stevens — Fri, 11 Aug 2017 02:57:36 GMT

Can't you define the port to use - ie not 4244? - on the proxies window

Re: Corporate network - problem with port 4244

kuczynska — Mon, 21 Aug 2017 08:27:09 GMT

Unfortunately not - this would mean we have to change the port for all of our customers and require their corporate networks to open new port, which not everyone wants to do.

We end up adding a custom authorization module to our scope to resolve this.

Thanks,

Re: Corporate network - problem with port 4244

Mon, 21 Aug 2017 10:09:08 GMT

Hi,

We've implemented a proxy in front of the QlikSense server based on a 'officially not supported' solution from the Qlik Community. Here's a link: Reverse Proxy using Apache but we use NGINX, this is also documented in the community: Re: Reverse Proxy and Authentication port redirect

Hope this helps...

Cheers,

Edwin