<?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: Can't keep app's OAuth consent method &amp;quot;Trusted&amp;quot; -- keeps going back to &amp;quot;required&amp;quot; in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Can-t-keep-app-s-OAuth-consent-method-quot-Trusted-quot-keeps/m-p/2538534#M108956</link>
    <description>&lt;P&gt;Ok for anyone who ends up here: I figured it out. Published oauth clients can only have the "required" consent method. However a oauth client does not have to be published. I created a new one with consent method "trusted" but kept it unpublished and it still works (it is a M2M client).&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 08 Dec 2025 19:54:42 GMT</pubDate>
    <dc:creator>bupham</dc:creator>
    <dc:date>2025-12-08T19:54:42Z</dc:date>
    <item>
      <title>Can't keep app's OAuth consent method "Trusted" -- keeps going back to "required"</title>
      <link>https://community.qlik.com/t5/App-Development/Can-t-keep-app-s-OAuth-consent-method-quot-Trusted-quot-keeps/m-p/2538344#M108937</link>
      <description>&lt;P&gt;I am creating a OAuth client in the management console per these instructions:&amp;nbsp;&lt;A href="https://qlik.dev/authenticate/oauth/create/create-oauth-client/" target="_blank" rel="noopener"&gt;https://qlik.dev/authenticate/oauth/create/create-oauth-client/&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However when I change the consent method and publish the client, the consent method flips back to "required" from "trusted". Any idea why?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 22:01:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Can-t-keep-app-s-OAuth-consent-method-quot-Trusted-quot-keeps/m-p/2538344#M108937</guid>
      <dc:creator>bupham</dc:creator>
      <dc:date>2025-12-05T22:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: Can't keep app's OAuth consent method "Trusted" -- keeps going back to "required"</title>
      <link>https://community.qlik.com/t5/App-Development/Can-t-keep-app-s-OAuth-consent-method-quot-Trusted-quot-keeps/m-p/2538534#M108956</link>
      <description>&lt;P&gt;Ok for anyone who ends up here: I figured it out. Published oauth clients can only have the "required" consent method. However a oauth client does not have to be published. I created a new one with consent method "trusted" but kept it unpublished and it still works (it is a M2M client).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2025 19:54:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Can-t-keep-app-s-OAuth-consent-method-quot-Trusted-quot-keeps/m-p/2538534#M108956</guid>
      <dc:creator>bupham</dc:creator>
      <dc:date>2025-12-08T19:54:42Z</dc:date>
    </item>
  </channel>
</rss>

