topic Re: SSO Qlik SAML Attributemapping problem in Integration, Extension & APIs

SSO Qlik SAML Attributemapping problem

Anonymous — Thu, 01 Feb 2018 07:59:53 GMT

I have set up a single sign on intergration between keycloak and qliksense.

but i cannot map any of the Existing SAML attributes that i receive,

i got following attributes in log, [Name='name', FriendlyName='fullName', Value='firstName lastName'] [Name='email', FriendlyName='email', Value='email@address.com'] [Name='userid', FriendlyName='username', Value='adUsername'].

The only attribute that works is the one i use as "SAML attribute for user ID". It will show up as UserID and Name on the user in qlik after login.

I have tried to map email and fullName through the SAML attribute mapping in qlik but its not working. i have tried all kind of names in the "Qlik Sense attributes" area

I use [QLIKSAML] as name in "SAML attribute for user directory".

did i missed something here?

Regards

Daniel

Re: SSO Qlik SAML Attributemapping problem

maartenv — Thu, 20 Sep 2018 14:03:45 GMT

I have the same issue, somebody any ideas?

Re: SSO Qlik SAML Attributemapping problem

lucienorrin — Tue, 16 Oct 2018 13:55:23 GMT

I'm having similar issues.

Anyone?

Re: SSO Qlik SAML Attributemapping problem

PierreSeiitra — Thu, 31 Jan 2019 10:24:22 GMT

Hello,

For custom attribute mapping, the values will be "stored" (only as session variable) in user.environement.email or user.environement.name. I use this mechanism to "store" users roles and access them in security rules.

But i haven't found a way to store theses values as persistent attributes of the user. If you find a way, i could use it.

Pierre

Re: SSO Qlik SAML Attributemapping problem

Ken_T — Tue, 28 Jul 2020 18:55:17 GMT

we have the same issue. been working on this for several weeks. it seems this should be documented 🙂