I’ve marked some graphql queries as @requireAuth. As a result, when I try to run the query in the graphql playground I get an auth error. That makes sense because I am not logged in as a user.
My auth is set up with Netlify. The docs on authentication say:
Simulating a logged-in user through the GraphQL Playground is no picnic though, but we’re working on improving the experience!
but I can’t find any other info. Is this a ‘solved’ problem and, if so, are there docs or a guide available?
When invoking the Redwood GraphQL API, you need to send:
- Authorization header with
Bearer <token> with your access token
- a Header
auth-provider with the provider you use like
supabase etc. This will be the provider type setup in your app.
If you are using self-hosted dbAuth, then the
Bearer <token> then the token is your user id and you’ll also need to set the cookie (which is encypyted).
Typically, I run the app in dev and then inspect the request and copy the headers/cookie and then set those in the GraphQL Playground in the headers section.
To get a good sense of how things work, run your app and watch the requests made when cells do data fetching – that’s the info you’ll need to send.
There’s really no easy way not to set these up without poking a hole through security in development mode – which is a little risky since if you are not careful could leave your production app open.
Also, many of your services will rely of the context being set with a
currentUser and authenticating will set that.
Note: Often JWT’s/access tokens will expire, so you may have to re-set these in your playground after some time has expired.
Thanks! I am using Netlify and I just had to add the following
I had noticed that the GraphQL Playground had effectively become redundant.
This explains why (that is nice to know) but really doesn’t seem to offer a resolution. What was a nice to have feature now is just about useless I have no intention of using “Netlify”. While I do support the strict stance on security first by default I get the feeling there should be some way of sending these header requirements to the GraphQL playground after all it is started automatically as part of Redwood (or perhaps an option to turn that off)
I did rather like the playground a thought I would investigate further,
Same thing worked for me with auth0 as auth-provider.