<?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>article Qlik Talend Product Q and A: Is it possible to authenticate Talend Studio to Github using SSO login？ in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Talend-Product-Q-and-A-Is-it-possible-to-authenticate/ta-p/2524087</link>
    <description>&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;After moved migrated GitHub from on-premises to cloud and so switched from credential login to SSO, is there a way to authenticate Talend Studio to GitHub using SSO login? If using personal access tokens (PATs), is it on the security risk?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;So far Talend Studio cannot SSO directly to GitHub, it can use a workaround with&amp;nbsp;&lt;STRONG&gt;PATs &lt;/STRONG&gt;or &lt;STRONG&gt;SSH keys&lt;/STRONG&gt;, and thereby also be more secure than without SSO.&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;How a personal access token can be authorized for SSO&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" target="_blank" rel="noopener"&gt;https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This link above explains how a personal access token can be authorized for SSO. So using a username and PAT from Studio to login to GitHub. GitHub allows granular permission controls for PATs and SSO authorization further mitigates security risks. Developers will need considerable rights.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;How an ssh key can be authorized for SSO&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on" target="_blank" rel="noopener"&gt;https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;You can do much the same with SSH keys&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Environment&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Talend Studio" id="qlik_TalendStudio"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 14 Jul 2025 02:57:51 GMT</pubDate>
    <dc:creator>Robert_Pence</dc:creator>
    <dc:date>2025-07-14T02:57:51Z</dc:date>
    <item>
      <title>Qlik Talend Product Q and A: Is it possible to authenticate Talend Studio to Github using SSO login？</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Talend-Product-Q-and-A-Is-it-possible-to-authenticate/ta-p/2524087</link>
      <description>&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;After moved migrated GitHub from on-premises to cloud and so switched from credential login to SSO, is there a way to authenticate Talend Studio to GitHub using SSO login? If using personal access tokens (PATs), is it on the security risk?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;So far Talend Studio cannot SSO directly to GitHub, it can use a workaround with&amp;nbsp;&lt;STRONG&gt;PATs &lt;/STRONG&gt;or &lt;STRONG&gt;SSH keys&lt;/STRONG&gt;, and thereby also be more secure than without SSO.&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;How a personal access token can be authorized for SSO&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" target="_blank" rel="noopener"&gt;https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This link above explains how a personal access token can be authorized for SSO. So using a username and PAT from Studio to login to GitHub. GitHub allows granular permission controls for PATs and SSO authorization further mitigates security risks. Developers will need considerable rights.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;How an ssh key can be authorized for SSO&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on" target="_blank" rel="noopener"&gt;https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;You can do much the same with SSH keys&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Environment&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Talend Studio" id="qlik_TalendStudio"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2025 02:57:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Talend-Product-Q-and-A-Is-it-possible-to-authenticate/ta-p/2524087</guid>
      <dc:creator>Robert_Pence</dc:creator>
      <dc:date>2025-07-14T02:57:51Z</dc:date>
    </item>
  </channel>
</rss>

