<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Qlik Sense - IAM WSO2 OIDC mapping attribute issue in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-IAM-WSO2-OIDC-mapping-attribute-issue/m-p/2520853#M22276</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;for a customer, we are trying to use Qlik Sense client managed as service provider and IAM WSO2 as authenticator (Identity Server). We are having problem in correctly mapping user attribute provided from IAM in Qlik user attribute,&lt;/P&gt;&lt;P&gt;Qlik virtual proxy redirects successfully to wso2 that proceeds to authenticate the user and call back to Sense.&lt;/P&gt;&lt;P&gt;While sub is correctly mapped to userID, such as emailaddress, we are having issue with Qlik attribute "name" that is accepting only wso2 "fullname" claim (this fullname claim inside the identity provider is mapped as "cn").&lt;/P&gt;&lt;P&gt;If I try to use claim "givenname" or "lastname" for example, we receive error 400 in the browser session and Qlik proxy log reports error&lt;/P&gt;&lt;P&gt;Missing claimType:OidcAttributeName↵↓ at Proxy.SessionEstablishment.Authentication.OIDC.OidcAttributeParser.ParseClaim(JwtPayload jwtPayload, String claimsAttrib, String claimTypeName, Boolean isMandatory)&lt;/P&gt;&lt;P&gt;I am attaching qlik virtual proxy configuration and wso2 claims configured into service provider&lt;/P&gt;&lt;P&gt;QLIK VIRTUAL PROXY&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="npapapicco_0-1749638654438.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181241iEAFA059E33342D5A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="npapapicco_0-1749638654438.png" alt="npapapicco_0-1749638654438.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;WSO2 SERVICE PROVIDER CLAIM CONFIGURATION&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="npapapicco_1-1749638740084.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181243i0C46820EE80745DD/image-size/medium?v=v2&amp;amp;px=400" role="button" title="npapapicco_1-1749638740084.png" alt="npapapicco_1-1749638740084.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Only this config produces successful authentication and correct redirection to Qlik Sense hub.&lt;/P&gt;&lt;P&gt;Why Qlik is accepting fullname claim only? Whatever you provide instead of fullname produce error 400&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any advice on that?&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Nick&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jun 2025 10:53:19 GMT</pubDate>
    <dc:creator>npapapicco</dc:creator>
    <dc:date>2025-06-11T10:53:19Z</dc:date>
    <item>
      <title>Qlik Sense - IAM WSO2 OIDC mapping attribute issue</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-IAM-WSO2-OIDC-mapping-attribute-issue/m-p/2520853#M22276</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;for a customer, we are trying to use Qlik Sense client managed as service provider and IAM WSO2 as authenticator (Identity Server). We are having problem in correctly mapping user attribute provided from IAM in Qlik user attribute,&lt;/P&gt;&lt;P&gt;Qlik virtual proxy redirects successfully to wso2 that proceeds to authenticate the user and call back to Sense.&lt;/P&gt;&lt;P&gt;While sub is correctly mapped to userID, such as emailaddress, we are having issue with Qlik attribute "name" that is accepting only wso2 "fullname" claim (this fullname claim inside the identity provider is mapped as "cn").&lt;/P&gt;&lt;P&gt;If I try to use claim "givenname" or "lastname" for example, we receive error 400 in the browser session and Qlik proxy log reports error&lt;/P&gt;&lt;P&gt;Missing claimType:OidcAttributeName↵↓ at Proxy.SessionEstablishment.Authentication.OIDC.OidcAttributeParser.ParseClaim(JwtPayload jwtPayload, String claimsAttrib, String claimTypeName, Boolean isMandatory)&lt;/P&gt;&lt;P&gt;I am attaching qlik virtual proxy configuration and wso2 claims configured into service provider&lt;/P&gt;&lt;P&gt;QLIK VIRTUAL PROXY&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="npapapicco_0-1749638654438.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181241iEAFA059E33342D5A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="npapapicco_0-1749638654438.png" alt="npapapicco_0-1749638654438.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;WSO2 SERVICE PROVIDER CLAIM CONFIGURATION&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="npapapicco_1-1749638740084.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181243i0C46820EE80745DD/image-size/medium?v=v2&amp;amp;px=400" role="button" title="npapapicco_1-1749638740084.png" alt="npapapicco_1-1749638740084.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Only this config produces successful authentication and correct redirection to Qlik Sense hub.&lt;/P&gt;&lt;P&gt;Why Qlik is accepting fullname claim only? Whatever you provide instead of fullname produce error 400&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any advice on that?&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Nick&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 10:53:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-IAM-WSO2-OIDC-mapping-attribute-issue/m-p/2520853#M22276</guid>
      <dc:creator>npapapicco</dc:creator>
      <dc:date>2025-06-11T10:53:19Z</dc:date>
    </item>
  </channel>
</rss>

