<?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 Re: SSO for Customer Portal in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/SSO-for-Customer-Portal/m-p/1123082#M80906</link>
    <description>&lt;P&gt;Hey, &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/915500"&gt;@MD14&lt;/a&gt;&lt;/SPAN&gt; Setting up SSO using JWT was sunset this year according to this note "&lt;I&gt;Please note: on February 5th, 2025, the ability to use SSO for new JWT applications was sunset. JWT-based applications configured for SSO prior to that date are not affected. Moving forward, it's recommended to use an Open ID Connect (OIDC) application instead&lt;/I&gt;" — &lt;A href="https://knowledge.hubspot.com/website-pages/set-up-single-sign-on-sso-to-access-private-content#:~:text=Please%20note%3A%20on%20February%205th%2C%202025%2C%20the%20ability%20to%20use%20SSO%20for%20new%20JWT%20applications%20was%20sunset.%20JWT%2Dbased%20applications%20configured%20for%20SSO%20prior%20to%20that%20date%20are%20not%20affected.%20Moving%20forward%2C%20it%27s%20recommended%20to%20use%20an%20Open%20ID%20Connect%20(OIDC)%20application%20instead." target="_blank"&gt;&lt;STRONG&gt;source&lt;/STRONG&gt;&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Jaycee&lt;/P&gt;</description>
    <pubDate>Mon, 17 Mar 2025 05:49:09 GMT</pubDate>
    <dc:creator>Jaycee_Lewis</dc:creator>
    <dc:date>2025-03-17T05:49:09Z</dc:date>
    <item>
      <title>SSO for Customer Portal</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/SSO-for-Customer-Portal/m-p/1122882#M80894</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to implement OIDC workflows in our authorisation server so that users in our application can access their tickets in the Customer Portal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both the authorise and token endpoints are invoked and responses are sent as expected but Customer Portal shows up an error page that says there is no permission.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am not sure what exact details in JWT token are expected by Hubspot server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have followed the OIDC section in this guide -&amp;nbsp;&lt;A href="https://knowledge.hubspot.com/website-pages/set-up-single-sign-on-sso-to-access-private-content?hubs_content=knowledge.hubspot.com/inbox/set-up-a-customer-portal&amp;amp;hubs_content-cta=setting%20up%20SSO" target="_blank" rel="noopener"&gt;https://knowledge.hubspot.com/website-pages/set-up-single-sign-on-sso-to-access-private-content?hubs_content=knowledge.hubspot.com/inbox/set-up-a-customer-portal&amp;amp;hubs_content-cta=setting%20up%20SSO&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be of great help if anyone can guide me to debug the issue further. I can share the sample code that implements the OIDC endpoints.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS: I have been trying out the sample code in AWS Lambda with Function URLs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;- Manjunath&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MD14_0-1742120638756.png" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/141029iE979FCE25A05212B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MD14_0-1742120638756.png" alt="MD14_0-1742120638756.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 16 Mar 2025 10:38:29 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/SSO-for-Customer-Portal/m-p/1122882#M80894</guid>
      <dc:creator>MD14</dc:creator>
      <dc:date>2025-03-16T10:38:29Z</dc:date>
    </item>
    <item>
      <title>Re: SSO for Customer Portal</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/SSO-for-Customer-Portal/m-p/1123082#M80906</link>
      <description>&lt;P&gt;Hey, &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/915500"&gt;@MD14&lt;/a&gt;&lt;/SPAN&gt; Setting up SSO using JWT was sunset this year according to this note "&lt;I&gt;Please note: on February 5th, 2025, the ability to use SSO for new JWT applications was sunset. JWT-based applications configured for SSO prior to that date are not affected. Moving forward, it's recommended to use an Open ID Connect (OIDC) application instead&lt;/I&gt;" — &lt;A href="https://knowledge.hubspot.com/website-pages/set-up-single-sign-on-sso-to-access-private-content#:~:text=Please%20note%3A%20on%20February%205th%2C%202025%2C%20the%20ability%20to%20use%20SSO%20for%20new%20JWT%20applications%20was%20sunset.%20JWT%2Dbased%20applications%20configured%20for%20SSO%20prior%20to%20that%20date%20are%20not%20affected.%20Moving%20forward%2C%20it%27s%20recommended%20to%20use%20an%20Open%20ID%20Connect%20(OIDC)%20application%20instead." target="_blank"&gt;&lt;STRONG&gt;source&lt;/STRONG&gt;&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Jaycee&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 05:49:09 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/SSO-for-Customer-Portal/m-p/1123082#M80906</guid>
      <dc:creator>Jaycee_Lewis</dc:creator>
      <dc:date>2025-03-17T05:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: SSO for Customer Portal</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/SSO-for-Customer-Portal/m-p/1123091#M80910</link>
      <description>&lt;P&gt;Hi Jaycee,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have implemented OIDC in our server and as part of that change, we are required to return a token (in JWT format). The issue is that though there are no errors in the API response, the Customer Portal is not loading.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are there specific information that is required by Hubspot and also is the "Provider Authorisation endpoint and Provider Token endpoint" needs to be hosted in same domain ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;- Manjunath&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 06:06:56 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/SSO-for-Customer-Portal/m-p/1123091#M80910</guid>
      <dc:creator>MD14</dc:creator>
      <dc:date>2025-03-17T06:06:56Z</dc:date>
    </item>
  </channel>
</rss>

