- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qlik Sense : Hiding dev hub
Dear all,
is it possible to hide the Qlik Dev Hub link based on the user ?
In the security rule of the stream, the only action available is "Read". Nevertheless, the user can access to the qlik dev hub.
Best regards,
Johann
- Tags:
- qlikview_deployment
- « Previous Replies
-
- 1
- 2
- Next Replies »
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks to mitaliajgaonkar for helping find the solution. It involves editing the source code in the following way:
Navigate to where your Qlik Sense program files are, and find the file:
~\Qlik\Sense\Client\assets\hub\hub.js
Copy this file and save it somewhere else as a backup in case anything goes wrong. Then open the file and find the string tid="MenuBtn".
This string is in a <button> tag which you will need to delete as well as the <div> around the button. Once this has been removed you will no longer see the dropdown for Dev Hub, Help, and About on any account. Now, to get to the dev hub you just append "/dev-hub/" to the end of your url. Keep in mind that if you upgrade, you will have to redo this change.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i'm also looking to hide it but couldn't find any option in qmc. Can anyone help please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Waqqas / Johann Choucq
Were you able to find a solution for hiding the dev hub dropdown?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear QlikexploreA8,
no sorry ! Never found a solution !
Best regards.
Johann
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there a way to go to source code of the html, javascript and css of it and erase it from there?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks to mitaliajgaonkar for helping find the solution. It involves editing the source code in the following way:
Navigate to where your Qlik Sense program files are, and find the file:
~\Qlik\Sense\Client\assets\hub\hub.js
Copy this file and save it somewhere else as a backup in case anything goes wrong. Then open the file and find the string tid="MenuBtn".
This string is in a <button> tag which you will need to delete as well as the <div> around the button. Once this has been removed you will no longer see the dropdown for Dev Hub, Help, and About on any account. Now, to get to the dev hub you just append "/dev-hub/" to the end of your url. Keep in mind that if you upgrade, you will have to redo this change.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot Tim !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I realize that even with hiding this button, the user can still type "/dev-hub/" at the end of the hub URL and have access to the dev hub anyway. Eventually I will need to figure out how to block access to this based on security rules or something.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
At version 3.1.* you need to add the following code to the stylesheet at C:\Program Files\Qlik\Sense\Client\hub\hub.css
li[tid="globalmenu-devhub"] {
display: none;
}
But be aware that this only hides the buton. It's still available when using ~/dev-hub/ in your URL.
So therefore you need to block the URL by firewall for instance.
Or deface / redirect it by putting this in the meta part of the file at location C:\Program Files\Qlik\Sense\Client\dev-hub.html
<meta http-equiv="refresh" content="0; URL='xxxxxxxxxxxxx'" />
Also make sure you set the security rules properly with read only on Extensions for instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is no solution obtained yet to get the permanent fix for the Dev Hub.
If we perform the code changes, it will be applied for all users.
There should be a way to control the access to certain users.
Please let know if the Dev-Hub can be controlled through the Security Rules or through QMC
- « Previous Replies
-
- 1
- 2
- Next Replies »