Skip to main content
Close announcements banner

Administration

Syncing users from Qlik Sense

To make the setup of users as simple as possible Qlik Alerting syncs users from the linked Qlik Sense installation during the initial registration process. It also periodically scans Qlik Sense for updates to keep the user list, user licenses, and license details current. This is currently set to check every 30 minutes.

The sync process works in two phases to permit management of very large user lists. You will not notice if you have a limited user list as it will process very quickly:

  1. It will return all user details without user attributes.
  2. It will then batch process the users to retrieve all of the attributes such as email and groups from the identify provider server (e.g. Active Directory).

An admin user in Qlik Alerting can also manually activate the sync process.

Do the following:

  1. Navigate to Admin > User Management > Users. (You will need to be logged in as an administrator or the super admin to view this menu.)

  2. Click Sync Qlik Sense Users at the bottom left of the table.
Note: This process may take a number of minutes as it schedules within the next minute and then processes the two phases as per the initial and periodic sync process.

Qlik Alerting licensing

Qlik Alerting has a site-based license that will read the license details from Qlik Sense which should have the Qlik Alerting attributes as part of the license details. If you have purchased Qlik Alerting recently and this is your first install please ensure your Qlik Sense site has been updated with the revised license details as this is a prerequisite for installing.

Access privileges in Qlik Alerting are governed by the user's licensed access to Qlik Sense. The table below outlines how licenses in Qlik Sense translate to Qlik Alerting access.

Qlik license type Qlik Alerting access and defaults
Professional
  • User can create their own alerts and distribute to groups or individuals (through Broadcast and Managed Shared alerts).
  • Can receive any distributed alert from other users.
  • Default setup will allow advanced features such as distribution to others and share alerts but these privileges can be removed by an Admin.
  • Default setup will not allow system alerts or broadcast notifications but these permissions can be switched on by the admin for specific users through the privileges area.
Analyzer
  • Standard user who can create their own alerts but is not able to distribute to groups or individuals.
  • Can receive any distributed alert from other users.
  • Will not be allowed access to any additional privileges.

Capacity Analyzer

Recipient by email only, no access to web portal nor mobile app.

No license access

Recipient by email only, no access to web portal nor mobile app.

Equivalent privileges for alternative Qlik Sense license models

  • Token-based license sites will treat anyone with User Access pass or Login Access Pass as an equivalent to a Professional license.
  • Core-based license sites will treat all users as an equivalent to a Professional license.

Assigning administrator rights to a user

You will need to always have at least one administrator user at any one time. There is no limit on how many administrator users you can assign.

Do the following:

  1. Navigate to Admin > User Management > Users.
  2. Use the search object to find the user you wish to make an administrator and highlight that row.
  3. Click on the edit button on the bottom toolbar.
  4. Change the user role dropdown and select administrator.
  5. Click Save.

Assigning user roles

There are two different types of user roles in Qlik Alerting: user and administrator. An administrator will have access to all functionality to be able to manage all aspects of the Qlik Alerting site.

Assigning user privileges

Professional level users can be given additional functionality through the assignment of user privileges. Only professional level users will be shown in the assigner user lists for privileges as other users cannot be assigned additional privileges. Administrator role users are also excluded from this list as they have access to all privileges as part of their user role.

The following user privileges are available:

User privilege Description
System Alerts Allows a professional Qlik Sense licensed user access to system alerts functionality to create and receive system alert notifications.
Distribution Setting Allows a professional Qlik Sense licensed user access to create broadcast and managed shared alerts which are sent to users with either a standard or a broadcast license.
Broadcast Notification Allows a professional Qlik Sense licensed user access to create and manage broadcast notifications. These are manually created notification messages that can be sent to a user group.
Share Alerts Allows a professional Qlik Sense licensed user to be able to share alert records they have created with other named professional or analyzer licensed users who are enabled in Qlik Alerting. This functionality makes a copy of the alert record that the recipient will take ownership of when they accept.

Steps to assign a user privilege

Do the following:

  1. Navigate to Admin > User Management > User Privileges. (You will need to be logged in as an administrator or the super admin to view this menu.)

    You will see a table that identifies the user privilege types available with a count to help you see what has been assigned.

  2. Click the edit (pencil) icon of the user privilege type to which you wish to assign users.

    The next page will show you two lists of users, on the left those who have not been assigned this privilege and on the right those who are already assigned.

  3. Select those users you wish to move, use the search to find users easily.
  4. Click the direction arrows to move them from one list to the other.
  5. Click Update.
Note: A user does not need to be assigned to both a broadcast and a standard licenses. A standard license user can receive broadcast alerts as part of their license.

Disabling access for a user

Disable the user in the Admin > User Management > Users area. Click the enabled switch against the user to turn off the users access.

Note: If the user has an Administrator role assigned, they will still be able to log in if they do not have a Qlik Sense named license but they will not receive triggered alerts. Other users will not be able to log on if they do not have a license in Qlik Sense.

Using trusted SSL certificates with Qlik Alerting

The Qlik Alerting install ships with a default self-signed certificate to secure the connection between the desktop of the user and the hosted application. This is a secure approach that enables HTTPS connections but will result in error messages in browsers, such as “The site’s security certificate is not trusted” (Chrome) or “This Connection is Untrusted” (Firefox).

This also has an affect on the way the Qlik Alerting Extension will work in Qlik Sense as this can cause cross-domain errors which require the user to click on a message that allows the browser to ‘run unsafe scripts’ (not an optimal user experience).

Steps to add a trusted SSL certificate for Qlik Alerting

Do the following:

  1. Access to the Qlik Alerting server via remote desktop.
  2. Navigate to the C:\Program Files\Qlik Alerting\config\certificates folder.
  3. Backup the server.pem and server_key.pem certificate files, so you can rollback the change if necessary.

    Note:
    • If you have been using a previous version of Qlik Alerting or Ping Alerting and have client.pem and client_key.pem certificates, you can simply rename them. Replace client with server.
    • Pass phrases for SSL certificates are not supported at this time.

  4. Replace the certificate files with your equivalent server.pem and server_key.pem certificate files.
  5. Restart the Qlik Alerting Gateway service.

Managing HSTS settings for an SSL connection

By default Qlik Alerting is set as securely as possible and we have HSTS headers enabled. This means that if you have connected to the site as HTTP or HTTPS you will be forced to connect (by the browser) as HTTPS the next time you connect. This has caused some issues with connections from the extension and mobile app where the environments are not fully secured with 3rd party trusted certificates. The HstsMaxAge setting can be managed to disable this behaviour, follow the steps below.

Do the following:

  1. Access to the Qlik Alerting server via remote desktop.
  2. Navigate to the C:\Program Files\Qlik Alerting\gateway\config folder.
  3. Open the default.json file with a text editor.
  4. Find the "hstsMaxAge" setting and change the default value 31536000 (1 year) to 0.
  5. Save the default.json file.
  6. Restart the Qlik Alerting Gateway service.

Additional security configuration options

Additional configuration options are available for organizations who wish to manage security tightly or wish to be specific about which security features to apply.

  • Allow or block HTTP access.
  • Allow or block TLS 1.2 (default), TLS 1.1, or TLS 1.0.
  • Add additional security headers to manage CORS access and other security restrictions.

To access these settings do the following:

  1. Access to the Qlik Alerting server via remote desktop.
  2. Navigate to the C:\Program Files\Qlik Alerting\gateway\config folder.
  3. Open the default.json file with a text editor.
  4. Find the "allowInsecure" and "customHeaders" settings where you can change the settings.
  5. Save the default.json file.
  6. Restart the Qlik Alerting Gateway Service.

Changing the ports for Qlik Alerting web access

If you wish to change the default ports from 4551 for HTTP and 4552 for HTTPS you must make this change in two places. For example, if you are running Qlik Alerting on a stand alone server with no other programs reserving these ports, you may wish to use ports 80 (HTTP) and 443 (HTTPS), which makes it easy for a user as they do not have to enter these default ports in the URL each time.

Do the following:

  1. Update the settings in the web UI.
    1. In the Qlik Alerting web portal, navigate to Admin > Config.
    2. Update the HTTP and ports to those you would like to change to, for example 80 (HTTP) and 443 (HTTPS).
    3. Click Save.
  2. Update the config file for the services.
    1. On the server, navigate to C:\Program Files\Qlik Alerting\config.
    2. Open the default.json file.
    3. On line 4, edit "httpPort": 4551; changing the 4551 value to your HTTP port entered in the Qlik Alerting settings step, for example port 80.
    4. On line 5, edit "httpsPort": 4552; changing the 4552 value to your HTTPS port entered in the Qlik Alerting settings step, for example port 443.
    5. Restart the Qlik Alerting Gateway service.
  3. You should now be able to access Qlik Alerting through these new ports.
  4. If you have used the Qlik Sense extension in any app, you will need to reset the port setting in each of these instances.

Backup and restore the MongoDB database

You will want to periodically backup the MongoDB database as this serves as the core of Qlik Alerting. It is recommended that you backup the database before each install.

Steps to backup

  1. RDP onto the server as an administrator user.
  2. Open a command window as an administrator.
  3. Enter the following to change directory:

    cd "C:\Program Files\MongoDB\Server\4.0\bin"

    Note: If you are using a newer version of MongoDB, or it is located in a different location such as a D:\ drive, then please adjust this appropriately.
  4. Enter the following command, where Backup Name is the identifier for your backup:

    mongodump --db=qlikalerting --out="Backup Name"

  5. This will create a new folder in the C:\Program Files\MongoDB\Server\4.0\bin folder called "Backup Name" and will export all of the data from the database into JSON format files.
  6. Zip this new folder and store where you require.

Steps to restore

  1. RDP onto the server as an administrator user.
  2. Open a command window as an administrator.
  3. Enter the following to change directory:

    cd "C:\Program Files\MongoDB\Server\4.0\bin"

    Note: If you are using a newer version of MongoDB, or it is located in a different location such as a D:\ drive, then please adjust this appropriately.
  4. Move the backup to a location that is easy to identify and unzip the file so the folder is located here, for example D:\backups\Backup Name.
  5. Enter the following command, where Backup Name is the identifier for your backup:

    mongorestore "D:\backups\Backup Name"

  6. You will now have restored the qlikalerting database in MongoDB.