Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
priyasawant
Creator II
Creator II

Errors while generating ticket with Postman

Hi Team,

We have Qlik Sense Single node server and we are trying to grant hub access to non AD users for which we have followed the following steps.

1. Added non AD users through excel (UDC connection)
2. Created a Dynamic header virtual proxy
3. Followed a complete process through PEM certificates (without Open SSL) as well as PFX certificates (With open SSL) both leads to XSRF prevention check failed. Possible XSRF discovered. error even after following the exact steps mentioned in the document - https://community.qlik.com/t5/Official-Support-Articles/How-to-configure-Postman-desktop-app-to-conn...
4. Followed https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Generate-a-ticket-with-Qlik-proxy... article to generate a ticket through powershell but this gives certificate parameter error where the path of the certificate is provided.

Has anyone tried implementing this? please support.

 

 

Regards,

Saniya

Labels (1)
1 Solution

Accepted Solutions
Damien_Villaret
Support
Support

Hello @priyasawant 

You cannot generate a ticket against a virtual proxy that uses header authentication.

The virtual proxy needs to be set to Ticket authentication.

Hope this helps.

If the issue is solved please mark the answer with Accept as Solution.

View solution in original post

3 Replies
Damien_Villaret
Support
Support

Hello @priyasawant 

You cannot generate a ticket against a virtual proxy that uses header authentication.

The virtual proxy needs to be set to Ticket authentication.

Hope this helps.

If the issue is solved please mark the answer with Accept as Solution.
priyasawant
Creator II
Creator II
Author

Hi Damien,

I have created a Dynamic Header authentication proxy for ticket authentication and it still is not working

priyasawant_0-1677419311019.png

 

Regards,

Saniya

Damien_Villaret
Support
Support

Hi @priyasawant 

As said previously, the authentication method needs to be set to "ticket"

Regards,

If the issue is solved please mark the answer with Accept as Solution.