-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GraphQLLocalExecutionClient: Add user credentials/token #582
Comments
GraphQLLocalExecutionClient directly passes the request to a You need to find out in which way your GraphQL "instance" expects to receive the user details (remember, the To test GraphQL authorization in an HTTP context I would recommend to actually use a http connection (see integration tests in this repo for some examples). Otherwise you need to build your own validation system, there are some pointers in the GraphQL.NET documentation regarding this topic. |
hmm so basically i don't need authentication, passing an additional object would be totally fine for me (-> as I'm already within the application context, I have the authenticated user already - just need the user somehow accessible within the query itself). Thanks a lot for your answer! |
thanks a lot, did it now using the variable section. Not very nice but working for now :-) Thanks a lot again! |
hmm still a strange problem
Variables doesnt show up on server side - Extension is filled properly (problem exists indepent of serializer - tried newtonsoft and system.text). Do you have an idea? |
I'd recommend using the extensions map for that
What is showing up? I'd expect variables to be |
Nothing, the variables enumerator is empty |
Hi there,
for querying a local instance of my graphql instance I'm using the GraphQLLocalExecutionClient. But for specific reasons, I also need to provide user details (username, credentials, ..) for the execution/permissions checks.
Is that somehow possible, without falling back to the HTTP client?
Thanks in advance for your help :-)
The text was updated successfully, but these errors were encountered: