You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using @envelop/generic-auth in my GraphQL Yoga server, following this example. I’ve set mode to protect-granular, expecting the resolveUserFn to only be called for fields marked with the @authenticated directive. However, I noticed that resolveUserFn is being called for all fields, including public fields that don’t require authentication.
This behavior adds unnecessary overhead for fields that don’t need user resolution or validation.
What I was expecting:
In protect-granular mode:
resolveUserFn should only be invoked for fields marked with the @authenticated directive.
Public fields should bypass user resolution and validation.
Actual Behavior
resolveUserFn is executed for all fields, including public fields, leading to unnecessary overhead.
useGenericAuth({mode: 'protect-granular',asyncresolveUserFn(context){consttoken=context.request.headers.get('x-authorization');// further validations: decoding, getting user deails from db e.t.c.returntoken??null;},});
Query:
query {
public
}
Observe that resolveUserFn is called for the public field.
any thoughts on this?
The text was updated successfully, but these errors were encountered:
This is the expected behavior. The user is always fetched at context building time. The plugin then extends the context with the resolved user to make it available for all resolvers or other plugins by storing the user in the context.
The protect-granular implies that the validateUser function will be called only for marked fields. Which means you can return null from resolveUserFn if their is no authenticated user for a request, public fields will still be resolvable.
Don't hesitate to ask more question if my explanation is not clear enough!
Discussed in #2363
Originally posted by ethdev279 January 11, 2025
I’m using
@envelop/generic-auth
in my GraphQL Yoga server, following this example. I’ve setmode
toprotect-granular
, expecting theresolveUserFn
to only be called for fields marked with the@authenticated
directive. However, I noticed thatresolveUserFn
is being called for all fields, including public fields that don’t require authentication.This behavior adds unnecessary overhead for fields that don’t need user resolution or validation.
What I was expecting:
In
protect-granular
mode:resolveUserFn
should only be invoked for fields marked with the@authenticated
directive.Actual Behavior
resolveUserFn
is executed for all fields, including public fields, leading to unnecessary overhead.Reproduction
Schema:
Plugin setup in GraphQL Yoga:
Query:
Observe that
resolveUserFn
is called for thepublic
field.any thoughts on this?
The text was updated successfully, but these errors were encountered: