topic NPrinting API Error from POSTMAN - Forbidden REVEL_CSRF tokens mismatch in Qlik NPrinting

NPrinting API Error from POSTMAN - Forbidden REVEL_CSRF tokens mismatch

sudeepkm_analog — Thu, 14 Jan 2021 19:09:37 GMT

Hi All,
I'm testing NPrining APIs (OnDemandRequest) from POSTMAN.
I used NTLM Auth and tried GET and it works.

https://<np_serverhost>:4993/api/v1/reports
After getting the Report ID, I tried POST call using the Report ID found from GET response.

https://<np_serverhost>:4993/api/v1/ondemand/requests
{
"type": "Report",
"config": {
"reportId": "0a0f095d-5109-4212-89d4-156bc3079469",
"outputFormat": "XLS"
}

I also added localhost to admin/settings > ondemand > trusted origin in NP Console.

It gives me an error.

Forbidden
REVEL_CSRF: tokens mismatch.

Please help in this regard. Thanks in advance.

@Frank_S , @Lech_Miszkiewicz, @Ruggero_Piccoli

Re: NPrinting API Error from POSTMAN - Forbidden REVEL_CSRF tokens mismatch

Frank_S — Thu, 14 Jan 2021 20:01:11 GMT

@sudeepkm_analog

Check your REST POST connection.

Ensure you have your Qlik Sense server inserted in the query header address as shown in the image below. In my case, the QS hub/QMC address is:

qlikserver1.domain.local

This address is also required as a trusted origin in the NPrinting management console

Re: NPrinting API Error from POSTMAN - Forbidden REVEL_CSRF tokens mismatch

sudeepkm_analog — Thu, 14 Jan 2021 20:51:47 GMT

Hi @Frank_S

Thanks for your quick response. In my case POSTMAN is the client that is making the API Call.

I'm not using QlikSense or QlikView to make the call.

I also checked the NPWEBCONSOLE_XSRF-TOKEN as mentioned here.(https://community.qlik.com/t5/Support-Knowledge-Base/How-to-Authenticate-Connect-with-the-Qlik-NPrinting-API-in/ta-p/1716540?_ga=2.104118848.1976822626.1610549407-1849850257.1580830761)

Still it does not work.

Re: NPrinting API Error from POSTMAN - Forbidden REVEL_CSRF tokens mismatch

sudeepkm_analog — Thu, 14 Jan 2021 22:27:31 GMT

Sorry I forgot one step to add X-XSRF-TOKEN in my POST request header.

I'm now able to make "POST" method call successfully.