<?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 February 2024 release: Change in OAuth CRUD authorization? in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/February-2024-release-Change-in-OAuth-CRUD-authorization/m-p/2420220#M19931</link>
    <description>&lt;P&gt;&lt;SPAN&gt;We have a unique OEM use-case where we need to create, configure, and delete OAuth M2M clients programmatically.&amp;nbsp; We are using undocumented API endpoints for this use-case (see below).&amp;nbsp; Everything was working until yesterday.&amp;nbsp; It seems like the February release of Qlik Cloud went out yesterday.&amp;nbsp; We noticed the following API behavior change is causing our OEM workflow to no longer work.&amp;nbsp; We are looking for advise on how to resolve the issue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We have a trusted M2M OAuth client with a Tenant Admin role, with the scopes,&amp;nbsp;user_default , admin_classic, and offline_access.&amp;nbsp; It was able to create an M2M OAuth client programmatically by making the following request.&lt;/SPAN&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;curl -X POST --location 'https://some-tenant.us.qlikcloud.com/api/v1/oauth-clients' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'qlik-web-integration-id: &amp;lt;webIntegrationId&amp;gt;' \
--header 'Origin: https://some.origin.com' \
--header 'Authorization: Bearer &amp;lt;token&amp;gt;' \
--data '{
  "app_type": "web",
  "client_name": "some client",
  "description": "a temporary client",
  "allowedGrantTypes": [
    "client_credentials"
  ],
  "allowedScopes":[
    "user_default",
    "admin_classic",
    "offline_access"
  ]
}'&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;However, this endpoint now returns a 403.&amp;nbsp; Allowing all scopes and roles to the M2M OAuth client that is making the request still returns a 403.&amp;nbsp; Deleting and recreating the M2M OAuth client making the request also is causing the same issue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;What could we potentially do to allow an M2M OAuth client to create and configure other M2M OAuth clients?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Feb 2024 19:35:03 GMT</pubDate>
    <dc:creator>yosuke-coupa</dc:creator>
    <dc:date>2024-02-16T19:35:03Z</dc:date>
    <item>
      <title>February 2024 release: Change in OAuth CRUD authorization?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/February-2024-release-Change-in-OAuth-CRUD-authorization/m-p/2420220#M19931</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We have a unique OEM use-case where we need to create, configure, and delete OAuth M2M clients programmatically.&amp;nbsp; We are using undocumented API endpoints for this use-case (see below).&amp;nbsp; Everything was working until yesterday.&amp;nbsp; It seems like the February release of Qlik Cloud went out yesterday.&amp;nbsp; We noticed the following API behavior change is causing our OEM workflow to no longer work.&amp;nbsp; We are looking for advise on how to resolve the issue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We have a trusted M2M OAuth client with a Tenant Admin role, with the scopes,&amp;nbsp;user_default , admin_classic, and offline_access.&amp;nbsp; It was able to create an M2M OAuth client programmatically by making the following request.&lt;/SPAN&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;curl -X POST --location 'https://some-tenant.us.qlikcloud.com/api/v1/oauth-clients' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'qlik-web-integration-id: &amp;lt;webIntegrationId&amp;gt;' \
--header 'Origin: https://some.origin.com' \
--header 'Authorization: Bearer &amp;lt;token&amp;gt;' \
--data '{
  "app_type": "web",
  "client_name": "some client",
  "description": "a temporary client",
  "allowedGrantTypes": [
    "client_credentials"
  ],
  "allowedScopes":[
    "user_default",
    "admin_classic",
    "offline_access"
  ]
}'&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;However, this endpoint now returns a 403.&amp;nbsp; Allowing all scopes and roles to the M2M OAuth client that is making the request still returns a 403.&amp;nbsp; Deleting and recreating the M2M OAuth client making the request also is causing the same issue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;What could we potentially do to allow an M2M OAuth client to create and configure other M2M OAuth clients?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 19:35:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/February-2024-release-Change-in-OAuth-CRUD-authorization/m-p/2420220#M19931</guid>
      <dc:creator>yosuke-coupa</dc:creator>
      <dc:date>2024-02-16T19:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: February 2024 release: Change in OAuth CRUD authorization?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/February-2024-release-Change-in-OAuth-CRUD-authorization/m-p/2420628#M19941</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/226619"&gt;@yosuke-coupa&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We don't support usage of unpublished (i.e. not published on &lt;A href="https://qlik.dev" target="_blank"&gt;https://qlik.dev&lt;/A&gt;) APIs, however we do have work ongoing to prepare this API for publishing, which potentially is what's caused the changes you've seen.&lt;/P&gt;
&lt;P&gt;Once an API is published, it is governed and we are required to publish notice of breaking changes on the changelog at qlik.dev.&lt;/P&gt;
&lt;P&gt;I'll reach out about this specific API over email.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Feb 2024 09:49:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/February-2024-release-Change-in-OAuth-CRUD-authorization/m-p/2420628#M19941</guid>
      <dc:creator>Dave_Channon</dc:creator>
      <dc:date>2024-02-19T09:49:24Z</dc:date>
    </item>
  </channel>
</rss>

