Is it possible to disable the option of Uploading QVW via Qlik Sense Dev Hub for end-users

[eyalnir_qlik]

Hi Team,

Is it possible to disable the option of Uploading QVW via Qlik Sense Dev Hub for end-users (analyzer) ?

Regarding access rights to Dev Hub, its seems that analyzer user has the option for upload qlikview (QVW)Documents in Dev Hub, although he have only read rights . (based on Qlik Documents enclosed)

https://help.qlik.com/en-US/sense-developer/May2024/Subsystems/Dev-Hub/Content/Sense_Dev-Hub/dev-hub...

This is a secured valuation for high secured customers like a BANK,  

we're looking for a way to achieve this restrict,  due to the constraint of not possible to disable the Qlik Sense Dev Hub for end users.

https://community.qlik.com/t5/Official-Support-Articles/Not-possible-to-disable-Qlik-Dev-Hub-for-nor...

Many thanks for any feedback

#3143

[eyalnir_qlik]

Qlik Team, any response ?

@Albert_Candelario 

[Filippo_Nicolussi_P]

Hello @eyalnir_qlik 

Try to disable the convert service in the Qlik Sense Service Dispatcher if it fits your urgency to disable upload of .QVW on Qlik Sense perspective with: 

[converterservice]
Disabled=true
Identity=Qlik.converterservice
DisplayName=Converter Service
ExePath=Node\node.exe
Script=..\ConverterService\src\www.js

[converterservice.parameters]
--port=${ConverterPort}
--log-path=${LogPath}

as per usual:

 1) make a backup of C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf

 2) Search and change above [converterservice] (add the bolt Disabled=true )

 3) restart Qlik Sense Service Dispatcher. 

 4) Repeat on all front end/exposed Worker Proxy Nodes should be enough.

[eyalnir_qlik]

Dear @Filippo_Nicolussi_P 

Thanks for your feedback, 

I tried to disable the convert service in the Qlik Sense Service Dispatcher as you suggested, 

and it doesn't disable the option to upload QVW files, furthermore, now I'm getting "internal server error" and when canceling the popup, i still have the option to upload any QVW file

Do you have any other ideas?

Many thanks

Eyal 

[eyalnir_qlik · Accepted solution]

Hi Team

The workaround that works for us was disable the whole dev-hub, the way to achieve it, was to rename the C:\program files\qlik\sense\client\dev-hub folder

Than there will be no dev-hub on the proxy nodes we specify for that use case.

we also change it only for the Central node (end-users node), in this way, it would only expose the rim node for the end-users and rather to developers who uses Dev-hub.

Cheers,

Eyal

[zolbae]

That’s a good idea.

However, even after changing the folder name, 'dev-hub' still exists in the menu.

Clicking it just brings up a blank screen.

I doubt anyone knows how to remove the menu completely.

[hugo_andrade]

@eyalnir_qlik ,

Make sure to reapply these changes upon every upgrade.

The way we solved it in the past is to enforce the traffic to the server through a Load Balancer like F5. Then, routing rules would prevent the upload of the file.

Let me know if there's interest in pursuing the alternative I've presented.

[eyalnir_qlik]

Hi @zolbae ,The solution I suggested was after consulting with Qlik R&D, and currently there is no out of the box way to completely remove the Dev Hub menu.

As @hugo_andrade  mentioned, if you have a Load Balancer such as F5, it is definitely worth trying that approach by enforcing traffic routing rules to block the upload.

Also, keep in mind that these changes need to be reapplied after every upgrade to prevent the behavior from returning.