topic Re: Header Authentication with SSO in QlikView

Header Authentication with SSO

binujose1982 — Sat, 16 Nov 2024 21:02:09 GMT

Recently, we have integrated SSO with qlikview server 12. I am using qlikview header authentication.

HeaderName: QVUSER

header prefix: DOMAIN\

Authorization:

NTFS authorization.

User is able to login Access Point. The issue is, whenever I distribute the document to a local windows group, access point is not showing up any document. But If I distribute directly to the user id, user is able to see the document.

Can you help on this?

Regards,

Binu.

Re: Header Authentication with SSO

Daniele_Purrone — Wed, 17 Apr 2019 11:50:41 GMT

Hi!
First o fall, please make sure that the Windows Group is a not a Distribution group, as that is not supported.

The weird thing about what you are reporting is that we currently have investigating a similar situation, but there it looks like header authentication works.

So, this is an interesting one. It might be the same issue with just slightly different behaviours.

I have spoken with some colleagues from our integrations team, and they suggested that you open a Support case, either with your responsible partner (if you have one) or with Qlik Support (if you are entitled to direct support). This will guarantee you the proper service level.

Please, provide a clear description, a link to this post, and provide the logs from QVS, QVWS/Settings Service and DSC: https://support.qlik.com/articles/000003712

And make sure to include your license number in the case!

Thanks in advance!

Re: Header Authentication with SSO

binujose1982 — Thu, 18 Apr 2019 02:12:05 GMT

Thank you Daniele.

Re: Header Authentication with SSO

Brett_Bleess — Wed, 29 May 2019 18:40:25 GMT

I believe where you went wrong here is not having changed QlikView Server security mode to DMS, you cannot use Header Authentication in the Web Server resource along with NTFS in the QlikView Server unless the header you are passing in matches your domain information, but that then begs the question of why you are just not using NTLM Authentication in the Web Server settings...

Regards,
Brett