@theydo/graphql-directive-requires-authentication
Advanced tools
Weekly downloads
Readme
The point of this directive is not to validate JWT tokens, since this is frequently a project-specific implementation. Instead it is expected that resolving token status is done in the Apollo getContext hook, where the validated token is used to extend the context object (user information).
This directive will only assert the "isAuthenticated" status coming from the context object.
To use the directive, you should start by adding the directive to your GraphQL schema:
@directive requiresAuthentication on FIELD_DEFINITION
After this, you can create the directive by passing an isAuthenticated
resolver
(and optionally a custom error) and the directive will do the rest:
const requiresAuthentication = requiresAuthenticationDirective<Context>({
isAuthenticated: (context) => !!context.auth?.token,
throwError: new MyCustomError('WITH_CUSTOM_ERROR_CODE'),
})
new ApolloServer({
schemaDirectives: {
requiresAuthentication,
},
})
FAQs
GraphQL directive for checking authentication through context
The npm package @theydo/graphql-directive-requires-authentication receives a total of 196 weekly downloads. As such, @theydo/graphql-directive-requires-authentication popularity was classified as not popular.
We found that @theydo/graphql-directive-requires-authentication demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket installs a Github app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.