Make a test request to a known good QRS API endpoint.If using a self-signed certificate: Go to Settings > General > Request > SSL certificate verification and disable certificate verification.Click Add to add this certificate to Postman.Note: Since you must enter the port used to connect, if you plan to connect via both the Proxy and directly to the QRS then you will need to specify both ports (4 respectively).Enter in the hostname of your Qlik Sense Server and port (e.g., with port 4242 in the example below).Go to Settings > Certificates > Add Certificate.Make a copy of the client.pem and client_key.pem files, and rename them to client.crt and client_key.key.Copy the client.pem and client_key.pem from C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\ (on the Central node if in a multi-node site) to a place where you can access it from Postman.Arbitrary machine name (best practice is to use the machine you are making the API calls from).Go into the QMC > Certificate section and export a copy of the certificates used in the site:.Process with PEM Certificates (Simplest, Doesn't Require OpenSSL): The ports being called are open between the machine with Postman installed and the server.In this guide we will use a Windows version of OpenSSL provided by Shining Light Productions. Other Windows versions may operate slightly differently, likewise for *Nix (UNIX, Linux, etc.) based versions of OpenSSL.Qlik Sense Enterprise on Windows , All Version. For insight into configuring the Chrome Extension, see article QRS API using Xrfkey header in Postman Chrome Extension. The desktop app is a standalone application whereas the Chrome Extension version is being deprecated. This article will outline how to connect to Qlik Sense's APIs using the desktop app version of Postman.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |