Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
bupham
Contributor
Contributor

Can't keep app's OAuth consent method "Trusted" -- keeps going back to "required"

I am creating a OAuth client in the management console per these instructions: https://qlik.dev/authenticate/oauth/create/create-oauth-client/

However when I change the consent method and publish the client, the consent method flips back to "required" from "trusted". Any idea why? 

Labels (1)
  • SaaS

1 Solution

Accepted Solutions
bupham
Contributor
Contributor
Author

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). 

View solution in original post

1 Reply
bupham
Contributor
Contributor
Author

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).