Product knowledge
Docs
Connect Qlik Cloud and Qlik Sense
Add the Qlik instances your Gateway will use, then verify user sign-in and access to the intended apps.
On this page
Prepare the Qlik connection
A Gateway connection establishes a route to Qlik. It does not assign a Raptor licence to every Qlik user or replace Qlik permissions. Keep connection setup, user assignment and the final access test as separate steps.
Open the Gateway's own administration page at /raptor/admin/ and select Config. The external Raptor Portal handles account, licence and download access; it is not the screen for managing these Qlik connections.
- Confirm the exact Qlik tenant or server and the administrator responsible for it.
- Check that the Gateway can reach Qlik and that users can reach the Gateway's advertised HTTPS address.
- For a new installation, use the verified installation administrator sign-in provided by Setup. Windows administrator access does not itself allocate an MCP seat.
Qlik Cloud
The connection dialog uses an approved Qlik Cloud API key to verify the tenant connection. Interactive users sign in through the configured Qlik Cloud OAuth flow. These credentials serve different purposes; do not distribute the setup API key to AI clients.
- In Config, open the Qlik connection dialog and choose Qlik Cloud.
- Enter the Qlik tenant address and the approved API key, then select Connect. Review the result before adding another instance.
- Confirm that Qlik Cloud user sign-in is configured for the Gateway, including its OAuth client and exact callback address. Ask the Gateway administrator to resolve a missing sign-in option.
- Assign the intended Qlik user in Seats. Have that user sign in to the Gateway and test one app they are allowed to open.
Qlik Sense Enterprise on Windows
Enter the Qlik server address used for the connection. If users sign in through a different browser address or virtual proxy, enter that separately, including the proxy prefix. Do not append /hub or an app URL.
The Gateway needs a matching client.pem, client_key.pem and root.pem certificate set. The dialog can discover suitable local certificates on the installation computer; otherwise select the three approved PEM files. Certificate validation and the Qlik connection check must succeed.
- Choose Qlik Sense on Windows in the connection dialog and review the server and browser addresses.
- Use the discovered certificates or select the matching certificate, private key and root certificate files. Select Connect.
- Complete or repair the Qlik sign-in bridge through the supported Setup process. Changing the Qlik browser address requires repairing or reinstalling that bridge and activating it again.
- Assign a Qlik-backed user in Seats, sign in as that user, and check access to an intended app and a harmless read operation.
Finish with an access test
Saving a connection may restart the Gateway to apply the new configuration. Wait for that change to finish, then refresh Config. A successful connection check proves a route to Qlik; it does not prove every user's app access or every tool operation.
The optional Writeback database connection settings are a separate route from the Gateway to Qlik. They require a database address reachable from the Qlik reload server or the selected Qlik Cloud Direct Access gateway, plus the appropriate PostgreSQL CA trust. Raptor does not open database firewall ports. Resolve a pending writeback setup before relying on reloads to read submitted changes.
For each connected estate, test sign-in, the user's Raptor assignment, app visibility and one permitted read. Record failures at the step where they occur rather than treating a green Gateway health indicator as complete acceptance.
Previous
Enterprise Gateway
Next