<?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 SAML configuration with OKTA using Alias name in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/SAML-configuration-with-OKTA-using-Alias-name/m-p/1941300#M30455</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;Thank you for taking time and reading this. I am new to Qlik sense and we are trying to do SAML configuration with OKTA and we are getting the "400 Bad request" error using the following doc.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/SAML-configuration-okta.htmSAML" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/SAML-configuration-okta.htmSAML&lt;/A&gt; configuration with Okta ‒ Qlik Sense for administrators&lt;/P&gt;
&lt;P&gt;Previously when we used the server name it was working for us. But now we want to use the alias name which we added in the Central Proxy - Host allow list and repeated all the configuration steps using the new alias name. Please let me know if there are anymore steps I need to take for using the Alias name.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;Sikander&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jan 2025 16:38:32 GMT</pubDate>
    <dc:creator>sikander02</dc:creator>
    <dc:date>2025-01-29T16:38:32Z</dc:date>
    <item>
      <title>SAML configuration with OKTA using Alias name</title>
      <link>https://community.qlik.com/t5/Management-Governance/SAML-configuration-with-OKTA-using-Alias-name/m-p/1941300#M30455</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;Thank you for taking time and reading this. I am new to Qlik sense and we are trying to do SAML configuration with OKTA and we are getting the "400 Bad request" error using the following doc.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/SAML-configuration-okta.htmSAML" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/SAML-configuration-okta.htmSAML&lt;/A&gt; configuration with Okta ‒ Qlik Sense for administrators&lt;/P&gt;
&lt;P&gt;Previously when we used the server name it was working for us. But now we want to use the alias name which we added in the Central Proxy - Host allow list and repeated all the configuration steps using the new alias name. Please let me know if there are anymore steps I need to take for using the Alias name.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;Sikander&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 16:38:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/SAML-configuration-with-OKTA-using-Alias-name/m-p/1941300#M30455</guid>
      <dc:creator>sikander02</dc:creator>
      <dc:date>2025-01-29T16:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: SAML configuration with OKTA using Alias name</title>
      <link>https://community.qlik.com/t5/Management-Governance/SAML-configuration-with-OKTA-using-Alias-name/m-p/1942782#M30456</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/18094"&gt;@sikander02&lt;/a&gt;&amp;nbsp; do you see any errors in the log "&lt;SPAN&gt;Servername_Audit_Proxy.txt" default location&amp;nbsp; (&lt;/SPAN&gt;&lt;SPAN&gt;C:\Programdata\Qlik\Sense\log\Proxy\Trace&lt;/SPAN&gt;&lt;SPAN&gt;)?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jun 2022 11:03:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/SAML-configuration-with-OKTA-using-Alias-name/m-p/1942782#M30456</guid>
      <dc:creator>Eugene_Sleator</dc:creator>
      <dc:date>2022-06-13T11:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: SAML configuration with OKTA using Alias name</title>
      <link>https://community.qlik.com/t5/Management-Governance/SAML-configuration-with-OKTA-using-Alias-name/m-p/1944742#M30457</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/134172"&gt;@Eugene_Sleator&lt;/a&gt;&amp;nbsp; thank you for you response. No I didn't see the&amp;nbsp; error. We were able to resolve by reverting back to server name and worked with OKTA team use the allow host name.&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;Sikander&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2022 17:59:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/SAML-configuration-with-OKTA-using-Alias-name/m-p/1944742#M30457</guid>
      <dc:creator>sikander02</dc:creator>
      <dc:date>2022-06-16T17:59:40Z</dc:date>
    </item>
  </channel>
</rss>

