-
Notifications
You must be signed in to change notification settings - Fork 99
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
[FEAT]: Admin JWT/api-key for backend queries and graphql #398
Comments
Hello @c-nv-s The GraphQL API is for the Lago's front purpose, we do not support calls on it without a JWT token since a user has to be logged in this scope's logic. I hope it answers your problem, if not I'm happy to dig more on this! |
just wanted to say I'm still running into this issue as a bit of a blocker. |
Hello @c-nv-s I'm not sure to understand your use case. Happy to discuss more about it on our slack community https://lago-community.slack.com |
I suppose the issue is when you have two or more organizations registered (therefore multiple api keys) and a backend system/s (e.g. API Gateway) which needs to be able to easily query the information across organizations... |
@jdenquin we would be interested in including the GraphQL API within our "supergraph". It would be great if a JWT token could be used for both internal and external use. |
Hello Guys, Sorry for the (very) late reply, we still have this feature in mind and will try to prioritize it asap! |
Hey @jdenquin Happy to contribute on this, if you already have a solid plan we can discuss over slack |
Is your feature request related to a problem? Please describe.
whilst trying to programmatically retrieve a batch of test customers' details, I noticed that the
/api/v1/customers
endpoint accepts the user's api key, but the/graphql
endpoint doesn't accept it because it needs a JWT.It is not clear how a backend (or even a user-facing frontend app) would get that JWT in order to query the graphql endpoint for administrative purposes.
It would be useful to have the ability to set/create a privileged api key/jwt for use of the graphql endpoint from other backends/microservices
This is particularly useful if one has their microservices behind an api gateway performing various business logic
Describe the solution you'd like
A way to perform queries and administrative tasks across multiple users without having to use a user-specific api key to query each account.
The text was updated successfully, but these errors were encountered: