Sorry about the late reply here and thanks for that context @JLarue! There's currently a known issue where scopes aren't properly being sent as part of the OAuth 2.0 flow when using client credentials. We can let you know here as soon as that has been fixed.
In the meantime, you might try using a custom auth flow to manually execute your authentication. This would require you to define the request to your Access Token URL with its required parameters as part of an "API Request" step, and afterwards, save the token in a "Define a variable" step.
Let me know if that helps or raises any additional questions! Can try setting up a more detailed example if need be
We are authenticating without issue using the client-credential flow. What is not working is the auto-complete within your GraphQL editor. That's okay for now as we can use our local Graphql editor, and then paste the queries & mutations in manually. This would be a much nicer experience if we could edit directly in the editor.
Yea it seems as though Retool is having some trouble with the request to retrieve the schema from your endpoint. Typically, you should be able to get the schema and auto-complete and I'm not sure exactly why it's failing.
With the setup for the one you're using the guesses that I have at the moment are either:
The ngrok endpoint you're hitting isn't delivering the schema
The scope issue I mentioned above is blocking the schema from being retrieved
I imagine it could totally be some third thing as well but after taking a look with a teammate these are the best ideas I have so far.