Comments (7)
To write custom authentication logic, you need to do two things:
- Make sure that you have access to the request data in the GraphQL context object. For example, if you're using express-graphql, the express request will be passed as
context
, so you're all set. - Implement a custom custom
GraphQLClient
client, e.g. by extendingHttpGraphQLClient
. For example, you could overridegetHeaders
, look into the request (passed ascontext
), do the token decoding and set appropiate headers for the proxied request.
Then, you can use a config like this:
const schema = weaveSchemas({
endpoints: [, {
namespace: 'M1',
url: 'http://m1/...'
}, {
namespace: 'M2',
client: new CustomHttpGraphQLClient('http://m2/...')
}, /* ... */
]
});
I hope this helps
from graphql-weaver.
@Yogu Few doubts:
- What is the `CustomHttpGraphQLClient?
- Where would I write the code for decoding the JWT token?
- Do I have to pass the client property for microservices M3 and M4 also?
from graphql-weaver.
CustomGraphQLClient
would be your subclass of HttpGraphQLClient
, something like this:
class CustomGraphQLClient extends HttpGraphQLClient {
protected async getHeaders(document: DocumentNode, variables?: { [name: string]: any }, context?: any, introspect?: boolean): Promise<{ [index: string]: string }> {
const request = context as Request;
// implement your logic here for decoding the token based on the express request
const regularHeaders = super.getHeaders(document, variables, context, introspect);
return {
...regularHeaders,
// add your headers here
};
}
}
Do I have to pass the client property for microservices M3 and M4 also?
I understood that M2, M3 and M4 are basically the same, so yes you would need to add endpoints with the custom client for all three of them.
from graphql-weaver.
@Yogu I understand that above mentioned solution will add a header (in which token data will be available for other to use) to the original request but I still don't understand how it will stop the request at the API Gateway if no JWT Token is found int the request header?
from graphql-weaver.
from graphql-weaver.
@Yogu Hey what if I am not using Typescript?
class CustomGraphQLClient extends HttpGraphQLClient { protected async getHeaders(document: DocumentNode, variables?: { [name: string]: any }, context?: any, introspect?: boolean): Promise<{ [index: string]: string }> { const request = context as Request; // implement your logic here for decoding the token based on the express request const regularHeaders = super.getHeaders(document, variables, context, introspect); return { ...regularHeaders, // add your headers here }; } }
Then how can I implement this custom class?
from graphql-weaver.
Ah, just remove some parts:
class CustomGraphQLClient extends HttpGraphQLClient {
async getHeaders(document, variables) {
const request = context;
// implement your logic here for decoding the token based on the express request
const regularHeaders = super.getHeaders(document, variables, context, introspect);
return {
...regularHeaders,
// add your headers here
};
}
}
If you need to target an older version of JavaScript, just use a transpiler of your choice.
from graphql-weaver.
Related Issues (20)
- Misbehavior for scalar type , maybe an edge case ? HOT 5
- Woven Schemas lose their astNodes HOT 2
- Directives, especially and primarily, default ones, get duplicated for each schema HOT 1
- Linked field returns null when using linkFieldName HOT 6
- Create a schema from already weaved schemas
- Documentation on links, pipelines, fieldMetadata and more insufficient
- Apollo's schema stiching
- LaunchPad graphql endpoints no longer available HOT 1
- Support `skip` argument with @join
- woking with uploads via apollo-upload-server HOT 1
- Launchpad example broken
- Links return an error when recommendation service sets typePrefix HOT 7
- [FEATURE REQUEST]: Ability to include HTTP headers HOT 1
- How to rename fields properly?
- Some implementations lost after weaveSchemas HOT 3
- GraphQL 15 compatibility HOT 1
- Cannot read property 'map' of undefined (link issue with undefined variableDefinitions)
- Upgrade graphql-tools dependency to 6.x.x
- Change introspectionQuery to getIntrospectionQuery
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graphql-weaver.